Look in the Event Viewer and see if chkdsk fixed the problem.
For a look at the chkdsk log.
Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Look in Application | Listed as Information |
Event ID: 1001
Source: Winlogon
[[Description: This includes file system type; drive letter or GUID, and
volume name or serial number to help determine what volume Chkdsk ran
against. Also included is whether Chkdsk ran because a user scheduled it or
because the dirty bit was set.]]
[[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.]]
[[This file states whether Chkdsk encountered any errors and, if so,
whether they were fixed.]]
You will see "0 KB in bad sectors" if there are no problems with the disk.
Can someone please explain the definition of "dirty volume"?
[[On NTFS volumes, the dirty bit is typically set only if the file system
has detected potential corruption. In this case, an event is logged in the
System event log.]]
http://support.microsoft.com/kb/322275
The dirty bit can also be set with fsutil dirty. But I doubt that has
happened. If the dirty bit is set, there is a problem of some sort with the
disk.
[[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.
Every time Windows XP starts, Autochk.exe is called by the Kernel to scan
all volumes to check if the volume dirty bit is set. If the dirty bit is
set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f
verifies file system integrity and attempts to fix any problems with the
volume.]]
Fsutil: dirty
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/fsutil_dirty.mspx
To query the dirty bit on drive C, type:
fsutil dirty query C:
Sample output:
Volume C: is dirty
or
Volume C: is not dirty
The only way to get rid of the dirty bit is to run chkdsk.
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
