CHKDSK

G

Guest

I run chkdsk at reboot as I'm using XP Pro which has a NTSF file system:
C:\WINDOWS\system32\cmd.exe /k chkdsk C:/f. After it runs, it displays
statistics related to the operation, but the display lasts less than 2
seconds. I'm unable to read the stats to determine what problems were
detected and if they were resolved. Suggestions?
 
D

Dave Patrick

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.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I run chkdsk at reboot as I'm using XP Pro which has a NTSF file system:
| C:\WINDOWS\system32\cmd.exe /k chkdsk C:/f. After it runs, it displays
| statistics related to the operation, but the display lasts less than 2
| seconds. I'm unable to read the stats to determine what problems were
| detected and if they were resolved. Suggestions?
| --
| Macmando
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top