Is there a chkdsk log?

[KG]

Is there a chkdsk log file that is created after chkdsk is ran and if so where might it be found?

Tanks much
*****************
Thank You (e-mail address removed)

Dr. Kavorkian for White house Physician

To reply to this email please remove the AT
after the kgs in the reply to address as shown above.

 

[Rick \Nutcase\ Rogers]

Hi,

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Rick \Nutcase\ Rogers]

Hi,

Yes, run eventvwr.msc from a start/run box or the administrative tools. Then
look under for winlogon under the system logs.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Richard Urban]

If you run chkdsk c: with a repair parameter, either /r or /f, a log (called
WinLogon) will be created in the application log. This is viewable by going
to Computer Management | Event Viewer | Application.

This log doesn't get created for a normal drive check, that I have ever
seen.

Then again, maybe I just haven't noticed it as there is no reason to go
there if the check shows no problems on the drive. (-:

--
Regards,

Richard Urban

If you knew as much as you thought you know,
You would realize that you don't know what you thought you knew!

 

[Wesley Vogel]

For a peek at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | 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.]]

Bootex.log is then deleted. The Application Event log is AppEvent.Evt and
is viewed in the Event Viewer, under Application.

Bootex.log can be acessed with recovery software such as Restoration.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[KG]

Thank you for the reply. My problem appears to be a false error from Norton Disk Dr.

For a peek at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | 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.]]

Bootex.log is then deleted. The Application Event log is AppEvent.Evt and
is viewed in the Event Viewer, under Application.

Bootex.log can be acessed with recovery software such as Restoration.

*****************
Thank You (e-mail address removed)

Dr. Kavorkian for White house Physician

To reply to this email please remove the AT
after the kgs in the reply to address as shown above.

 

[Wesley Vogel]

Norton strikes again. Keep having fun.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Thank you for the reply. My problem appears to be a false error from
Norton Disk Dr.

For a peek at the chkdsk log.

Open the Event Viewer...
Start | Run | Type: eventvwr | 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.]]

Bootex.log is then deleted. The Application Event log is AppEvent.Evt
and is viewed in the Event Viewer, under Application.

Bootex.log can be acessed with recovery software such as Restoration.

*****************
Thank You (e-mail address removed)

Dr. Kavorkian for White house Physician

To reply to this email please remove the AT
after the kgs in the reply to address as shown above.