Ran Error Checking and rebooted. where is the report?

[Joel]

I right clicked on my C drive and ran the Error Checking thing. I have to
reboot to get it to go through its process. I had it set to automatically
fix any errors. The process went through the motions and I watched it on my
screen at boot up as it worked.

When the checking reach 100%, the computer proceeded to boot up and told me
nothing. I guess that means everything is okay, but is there no report?

 

[Wesley Vogel]

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.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[S.Sengupta]

Control Panel > Administrative Tools > Event Viewer> Application >
Winlogon.

regards,
S.Sengupta[MS-MVP]

 

[Joel]

No need to paste the whole thing, but here is part of the Event Viewer that
interests me. What should I infer from this?
Free space verification is complete.

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

78148160 KB total disk space.

5835852 KB in 21204 files.

6000 KB in 2129 indexes.

0 KB in bad sectors.

73388 KB in use by the system.

44032 KB occupied by the log file.

72232920 KB available on disk.

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.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

I right clicked on my C drive and ran the Error Checking thing. I have to
reboot to get it to go through its process. I had it set to automatically
fix any errors. The process went through the motions and I watched it on
my screen at boot up as it worked.

When the checking reach 100%, the computer proceeded to boot up and told
me nothing. I guess that means everything is okay, but is there no
report?

 

[Wesley Vogel]

Doesn't look to me like you have any problems.

See if this helps...
The Chkdsk Process on NTFS Volumes
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/prkd_tro_utol.asp

This explains a little about Security Descriptors

Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/default.aspx?scid=kb;en-us;255008

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

No need to paste the whole thing, but here is part of the Event Viewer
that interests me. What should I infer from this?
Free space verification is complete.

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

78148160 KB total disk space.

5835852 KB in 21204 files.

6000 KB in 2129 indexes.

0 KB in bad sectors.

73388 KB in use by the system.

44032 KB occupied by the log file.

72232920 KB available on disk.

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.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

I right clicked on my C drive and ran the Error Checking thing. I have
to reboot to get it to go through its process. I had it set to
automatically fix any errors. The process went through the motions and
I watched it on my screen at boot up as it worked.

When the checking reach 100%, the computer proceeded to boot up and told
me nothing. I guess that means everything is okay, but is there no
report?

 

[Rock]

No need to paste the whole thing, but here is part of the Event Viewer that
interests me. What should I infer from this?
Free space verification is complete.

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

78148160 KB total disk space.

5835852 KB in 21204 files.

6000 KB in 2129 indexes.

0 KB in bad sectors.

73388 KB in use by the system.

44032 KB occupied by the log file.

72232920 KB available on disk.

It means chkdsk found discrepancies between it's results and the bitmap
kept by NTFS, and made some changes to correct it. It's not an uncommon
thing to see and not a big deal, AFAIK. What exactly chkdsk does and
the specifics of the NTFS file system are not well documented. Here is
one of the better and more in depth descriptions of it.

An explanation of the new /C and /I Switches that are available to use
with Chkdsk.exe
http://support.microsoft.com/kb/314835/en-us

 

[S.Sengupta]

It explains that the $BITMAP might become corrupted and resulted in lost
disk space.Chkdsk corrected the issue in the master file table's (MFT)
BITMAP attribute.CHKDSK discovered free space marked as allocated in the
volume bitmap.
As there is no bad sector so nothing serious.

regards,
S.Sengupta[MS-MVP]

No need to paste the whole thing, but here is part of the Event Viewer that
interests me. What should I infer from this?
Free space verification is complete.

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

78148160 KB total disk space.

5835852 KB in 21204 files.

6000 KB in 2129 indexes.

0 KB in bad sectors.

73388 KB in use by the system.

44032 KB occupied by the log file.

72232920 KB available on disk.

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.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

I right clicked on my C drive and ran the Error Checking thing. I have to
reboot to get it to go through its process. I had it set to automatically
fix any errors. The process went through the motions and I watched it on
my screen at boot up as it worked.

When the checking reach 100%, the computer proceeded to boot up and told
me nothing. I guess that means everything is okay, but is there no
report?