Re: Inconsistent CHKDSK results
- From: "CraigM" <cwigster@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 2 Jan 2008 17:15:05 +1100
Hi Tim and Dave,
thanks for your suggestions. Managed to fix it in the end, bit of a
convoluted solution, but in a nutshell
- noticed that all the files being reported as corrupt/unreadable by our
backup s/w were in one directory.
- discovered that although our backup s/w was reporting errors in the
filesystem and refused to backup the effected files, I could infact backup
the files with trusty old xcopy.
- backed up the directory with xcopy to a different disk on the same server
and onto a completely seperate server. Used /v to verify the xcopy was good.
- Deleted the suspect directory
- Did a full chkdsk
- Checked for bad sectors (none reported)
- Restored the directory from the xcopy backup
- Did another full chkdsk
- Performed a full system backup with out enterprise backup s/w which worked
without any errors. Yay!
So, after this, our backup s/w can now backup the directory and chkdsk is
now reporting a error free disk in both readonly and repair mode.
I've logged a support call with our backup vendor asking them why xcopy was
able to backup the files whereas their s/w couldn't. I'm assuming that
perhaps xcopy uses a different API to the filesystem or might ignore
specific errors or something along those lines.
In short, it's all ok now. Thanks for the additional tips though.
Regards
Craig
"Tim" <storagegeek007@xxxxxxxxx> wrote in message
news:927f6076-d2e2-427c-8cc5-d3dc0836a0e8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Dec 12, 4:21 am, "CraigM" <cwigs...@xxxxxxxxxxxxxxxxxxxx> wrote:
Hi eveyone,
I have a Win2003 server which is reporting that the filesystem on volume
D:
is corrupt. Upon doing a chkdsk d: /v (read only mode) from the command
line
chkdsk reports some index errors during stage 2 of the scan. There are 15
enrtries listed. Chkdsk also reports
"Detected minor inconsistencies on the drive. This is not a corruption"
This issue is causing our backups to fail when backing up certain
directories on that drive.
So, I scheduled a chskdsk on D: on the next reboot and rebooted the
server.
I watched the chkdsk run and it did not report any errors. Once it had
completed rebooting I re-ran a read only chkdsk from the command line and
it
reported the same index errors.
So next I tried running chkdsk in repair mode from the command line
allowing
it to dismount the volume. On the 1st run it reported fixing two index
errors at that was it, however when I do a read only chkdsk it is still
reporting index errors. Subsequent repair mode chkdsks runs reported no
errors.
So the situation is that
- A read only chkdsk reports index errors during stage 2
- A chkdsk in repair mode reports no errors
- Backups are still failing on specific directories on that drive
Luckily (I think) the directories failing to backup are just temporary
log
file area's so I think there not critical.
I'm not sure what to try next. I suppose the obvious is to try and delete
the effected directory structures? Suggestions welcome.
Craig
Hello Craig,
Try a quick fix. In Recovery Console, instead of just chdsk, try run
chkdsk /p (much less time consuming) to see if there are bad sectors
then if bad sectors are found run chkdsk /r.
chkdsk /r (don't forget the space between chkdsk and /r. This will
repair or replace damaged, missing or corrupt system files.
chkdsk /r locates and attempts to restore bad sectors and/or recover
readable information. chkdsk will need to be run before any other
recovery is attempted.
the best check is from dos from bootable disc with the utilities
available from the hard drive manufacturer.
if chkdsk and/or hard drive utilities can't fix the problem then a new
hard drive will be likely in the near future. This can be a scenario
of silent data corruption :) good luck..
:)
Tims
.
- Prev by Date: Re: Funny Vista/XP Boot change
- Next by Date: smb authentication question
- Previous by thread: Re: Can't able to read arabic file
- Next by thread: smb authentication question
- Index(es):
Relevant Pages
|
Loading
