Y
Yousuf Khan
I've been occasionally getting an error message on my Event Viewer,
Event ID 55, source Ntfs, message:
"The file system structure on the disk is corrupt and unusable. Please
run the chkdsk utility on the volume Hit 1000 winboot."
I'm absolutely certain that these are mostly fake messages, caused by
transient power losses. But still, I can't take a chance, If I were to
follow the advice given in the message and run chkdsk, since it's a boot
disk, it will require a reboot of the system and the chkdsk will run
just prior to system restart. I'd have no problems with that except
chkdsk is woefully slow, it takes over an hour to run it on my system.
I'd rather not run it, if all it's going to find is that there is
nothing wrong with the file system.
I found a technote from Microsoft, which is for a previous version of
Windows:
http://www.microsoft.com/technet/su...=5.2.3790.1830&EvtID=55&EvtSrc=ntfs&LCID=1033
It suggested running the "chkntfs" utility on the drive letter first and
it returns a simple "is dirty" or an "is not dirty" message. Runs in a
few seconds even while online. It usually sends back an "is not dirty"
message. Can this utility be trusted, compared to "chkdsk"? That is, are
there situations which Chkntfs is not aware of that Chkdsk is more
thorough about?
Yousuf Khan
Event ID 55, source Ntfs, message:
"The file system structure on the disk is corrupt and unusable. Please
run the chkdsk utility on the volume Hit 1000 winboot."
I'm absolutely certain that these are mostly fake messages, caused by
transient power losses. But still, I can't take a chance, If I were to
follow the advice given in the message and run chkdsk, since it's a boot
disk, it will require a reboot of the system and the chkdsk will run
just prior to system restart. I'd have no problems with that except
chkdsk is woefully slow, it takes over an hour to run it on my system.
I'd rather not run it, if all it's going to find is that there is
nothing wrong with the file system.
I found a technote from Microsoft, which is for a previous version of
Windows:
http://www.microsoft.com/technet/su...=5.2.3790.1830&EvtID=55&EvtSrc=ntfs&LCID=1033
It suggested running the "chkntfs" utility on the drive letter first and
it returns a simple "is dirty" or an "is not dirty" message. Runs in a
few seconds even while online. It usually sends back an "is not dirty"
message. Can this utility be trusted, compared to "chkdsk"? That is, are
there situations which Chkntfs is not aware of that Chkdsk is more
thorough about?
Yousuf Khan