If a volume's dirty bit is set, this indicates that the file system may be
in an inconsistent state. The dirty bit can be set because the volume is
online and has outstanding changes, because changes were made to the volume
and the computer shutdown before the changes were committed to disk, or
because corruption was detected on the volume. If the dirty bit is set when
the computer restarts, chkdsk runs to verify the consistency of the volume.
When Autochk runs against a volume at boot time it records its output to a
file called Bootex.log in the root of the volume being checked. The Winlogon
service then moves the contents of each Bootex.log file to the Application
Event log. One event log message for each volume checked is recorded. So
check the application event log.
This article may also help.
http://support.microsoft.com/default.aspx?scid=kb;[LN];160963
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Christos Kritikos" wrote:
|
| I am trying to figure out what exactly chkntfs does.
| According to the help chkntfs "displays or modifies the
| checking of disk at boot time" and with the /C flag
| it "schedules a drive to be checked at boot time; chkdsk
| will run if the drive is dirty".
|
| Does anyone know what "check a disk" stands for in this
| case? How does windows define a drive as "dirty"? Is
| there a way I can force a chkdsk at startup even if the
| drive is uh... "clean"?
|
| thanks
| christos
|