Hi all,
Sorry that this is such a long posting. However, it just might save someone
from the pain and frustration I have been through with chkdsk when run from
a command prompt and chkdsk /r after a restart. Jane is a Microsoft support
representative.
Hi Jane
I have done some extensive research over my experiences with my NTFS file
problems I contacted Microsoft about and I think I have resolved it.
A Google search revealed an interesting article
http://webspiffy.com/archives/2002/08/ntfs_file_system_glitch/ .
First, their appears to be a problem with chkdsk recording false positive
errors when run from a command prompt. I can find no reference to this
problem in the Microsoft Knowledge Base. To quote from the above article
reportedly sourced from Microsoft, "This problem occurs because when chkdsk
is run against a NTFS volume, chkdsk.exe may report that security
descriptors are in the database that are no longer referenced by any file or
folder, and that it is removing them. However, chkdsk.exe just reclaims the
unused security descriptors as housekeeping activity, and is not actually
fixing any kind of problem."
Thus the instruction given by chkdsk to run chkdsk with the /f fix option to
correct these errors can be safely ignored, but only in certain
circumstances.
There are many reports in web forums of poor souls doing high and low level
formats, ASR restores, changing hard disks, etc and generally pulling their
hair out, all to no avail because of this bug in chkdsk.
I sincerely hope that Microsoft fixes this problem ASAP. At least please
tell people to use chkntfs c: to see if a volume is dirty before they press
the panic button! Chkdsk is the only NTFS file utility that will correct
problems with files/disks and a bug like this can be an unneeded heart
stopper, if chkdsk is giving false positive errors!
Now to the lock ups I received when running chkdsk /r.
Your advice about InCD causing this is almost certainly correct. (THANKS!)
On uninstalling it I now find that chkdsk /r will run from a restart without
a lock up. I did not try this until yesterday because of the bogus errors I
was getting from chkdsk run from a command prompt. (I did not like my system
files being threatened!) In 2 trials, after the uninstall of InCD no
lockups! No silly STOP 0x7E messages. Problem (almost certainly) resolved.
What I don't understand is how InCD interferes with the running of autochk
on restart. At the stage of running autochk InCD would not be loaded. I
intend contacting AHEAD Nero and advising them of this.
Thanks again for your help.
Best wishes,
Bert Smith
