chkdsk issues

[brucewayne]

On both my desktop running XP Pro and laptop running w2k when I do a chkdsk on the main drive I get the following error:

CHKDSK is verifying files (stage 1 of 3)...

File verification completed.

CHKDSK is verifying indexes (stage 2 of 3)...

Index verification completed.

CHKDSK is recovering lost files.

CHKDSK is verifying security descriptors (stage 3 of 3)...

Security descriptor verification completed.

CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap.

Correcting errors in the Volume Bitmap.

Windows found problems with the file system.

Run CHKDSK with the /F (fix) option to correct these.

I tried running chkdsk with /f and also with /f /v /r. When l reboot chkdsk comes on (before the OS loads) and it runs fine. After the OS loads I run chkdsk and get the above error again.

It would appear that no matter how many chkdsk I run, the error keeps coming up. Is there something that I'm not doing or maybe another option that I need to run? Causes or fixes? I run the chkdsk monthly to make sure it runs ok. My Windows comes up ok and programs run but this chkdsk issue is driving me nuts. Any suggestions most appreciated.

[Needalittleinfo]

What type of check disk are you running? xp and 2ks?

[sechs]

If you are running chkdsk on a volume with locked files, chkdsk will never complete successfully. So, if this particular volume always passes a boot-time check, it's probably fine.

[dbook]

I have the same issue with CHKDSK /F on my C: drive. I've run CHKDSK /R and CHKDSK /F multiple times, but still wind up with volume bitmap errors. Has there been any resolution to this issue?

- David

[johnnyis42]

http://mike.steinbaugh.com/blog/2002...em_glitch.html

this guy actually sent microsoft a message about this and they replied. i'll save you the suspense... you can ignore the message. it's good information though if you're inclined to know why.

[dbook]

Thanks for the pointer. Fascinating (and frustrating) thread. One of the reasons I went to XP, finally, was to rid myself of annoying file system errors, and it seems NTFS is also error prone. Although Microsoft says it's not a problem, I'm not sure I buy it. I've had other weird file system glitches since this issue occurred, and none to speak of beforehand.

Perhaps the next version of the Windows file system will be an improvement, but I'm not holding my breath.
- David

[johnnyis42]

well, if you really are having errors, from what i was reading the bitmap errors shouldn't actually be the source of the errors. i'd check event viewer to see if there is anything wierd i there instead of relying on the simple chkdsk utility to tell you how the disk is doing.

i don't really know how the next file system, WINFS or whatever longhorn will have, will stack up to NTFS. from everything they say it will be a huge change, almost revolutionary, however it will not be implimented right away acording to the longhorn roadmap. rumor has it that the new file system is the thing causing the most delays.

[dbook]

Thanks for the reply. I do check the Event log and nothing weird shows up there. My backup utility, Retrospect, periodically crashes the system, however, and it may be implicated in some file system errors (though it's not clear how, since it's reading files on my hard drive, not writing them).

- David