Checkdisk Problem

When I run checkdisk on any drive/partition from within windows xp pro It
doesnt seem to log its findings anywhere. If I run checkdisk from outside
windows from commandline and boot back into windows I can see the info in
event viewer. Where does checkdisk log its info? This behaviour is on both
my computers even after reformating and reinstalling.

Glen

Running chkdisk without rebooting is a waste of time. Same as CHKDSK in
read-only mode, see below.

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

This will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

From: Doug Knox
-----

Don't bother even running CHKDSK in read-only mode.

1. In My Computer or Windows Explorer, right-click the volume you want to
check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

o To run Chkdsk by using the /f parameter, select the Automatically fix file
system errors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive is
currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your drive is
not available to run other tasks while the disk is being checked.]]

o To run Chkdsk by using the /r parameter, select the Scan for and attempt
recovery of bad sectors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All files
must be closed for this program to run. If the drive is currently in use, a
message asks if you want to reschedule the disk checking for the next time
you restart your computer. Your drive is not available to run other tasks
while the disk is being checked. If you select this option, you do not need
to select Automatically fix file system errors. Windows fixes any errors on
the disk.]]

You have to reboot for Error-checking to run.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Glen hunted and pecked:
When I run checkdisk on any drive/partition from within windows xp pro It
doesnt seem to log its findings anywhere. If I run checkdisk from outside
windows from commandline and boot back into windows I can see the info in
event viewer. Where does checkdisk log its info? This behaviour is on both
my computers even after reformating and reinstalling.

Glen

You are completely misunderstanding what I wrote. There is no log entry for
checkdisk if I run checkdisk from within windows. There are only log entries
if I run checkdisk from the commandline.

Glen


"Wesley Vogel" wrote in message
...
Running chkdisk without rebooting is a waste of time. Same as CHKDSK in
read-only mode, see below.

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

This will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

From: Doug Knox
-----

Don't bother even running CHKDSK in read-only mode.

1. In My Computer or Windows Explorer, right-click the volume you want to
check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

o To run Chkdsk by using the /f parameter, select the Automatically fix
file
system errors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive
is
currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your drive
is
not available to run other tasks while the disk is being checked.]]

o To run Chkdsk by using the /r parameter, select the Scan for and attempt
recovery of bad sectors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All
files
must be closed for this program to run. If the drive is currently in use,
a
message asks if you want to reschedule the disk checking for the next time
you restart your computer. Your drive is not available to run other tasks
while the disk is being checked. If you select this option, you do not
need
to select Automatically fix file system errors. Windows fixes any errors
on
the disk.]]

You have to reboot for Error-checking to run.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Glen hunted and pecked:
When I run checkdisk on any drive/partition from within windows xp pro It
doesnt seem to log its findings anywhere. If I run checkdisk from outside
windows from commandline and boot back into windows I can see the info in
event viewer. Where does checkdisk log its info? This behaviour is on
both
my computers even after reformating and reinstalling.

Glen

I just reread what I wrote and while I meant to say checkdisk doesnt log its
results in event viewer I didn't write it. So I'll attempt to rewrite it for
clarity. There are no entries for checkdisk in event viewer if i run
checkdisk from within windows. If I run checkdisk from the commandline its
logged in event viewer.
This behaviour is on two computers both with fresh installations of xp pro.
This isn't new behaviour I have never seen a log entry for checkdisk after
running it from within windows. Does your installation log is checkdisk runs
if you run it within windows. I find it hard to believe both ny computers
have a fault as both are new installations.

Glen



"Glen" wrote in message
...
You are completely misunderstanding what I wrote. There is no log entry
for checkdisk if I run checkdisk from within windows. There are only log
entries if I run checkdisk from the commandline.

Glen


"Wesley Vogel" wrote in message
...
Running chkdisk without rebooting is a waste of time. Same as CHKDSK in
read-only mode, see below.

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

This will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

From: Doug Knox
-----

Don't bother even running CHKDSK in read-only mode.

1. In My Computer or Windows Explorer, right-click the volume you want to
check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

o To run Chkdsk by using the /f parameter, select the Automatically fix
file
system errors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive
is
currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your drive
is
not available to run other tasks while the disk is being checked.]]

o To run Chkdsk by using the /r parameter, select the Scan for and
attempt
recovery of bad sectors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All
files
must be closed for this program to run. If the drive is currently in use,
a
message asks if you want to reschedule the disk checking for the next
time
you restart your computer. Your drive is not available to run other tasks
while the disk is being checked. If you select this option, you do not
need
to select Automatically fix file system errors. Windows fixes any errors
on
the disk.]]

You have to reboot for Error-checking to run.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Glen hunted and pecked:
When I run checkdisk on any drive/partition from within windows xp pro
It
doesnt seem to log its findings anywhere. If I run checkdisk from
outside
windows from commandline and boot back into windows I can see the info
in
event viewer. Where does checkdisk log its info? This behaviour is on
both
my computers even after reformating and reinstalling.

Glen

Glen,

CHKDSK does *not* work correctly in the read-only mode. So it would be a
waste of time if chkdsk logged its results in the read-only mode anyway.

Running chkdsk without rebooting is a waste of time. It is the same as
running chkdsk in the read-only mode.

You have to reboot your machine (both of them) in order for chkdsk to work
correctly.

Here are some reasons...

[[Chkdsk might not accurately report information in read-only mode.]]
From...
Chkdsk
http://www.microsoft.com/resources/d...b_tol_pwfd.asp

[[If you run chkdsk without the /f command-line option on an active
partition, it might report spurious errors because it cannot lock the
drive.]]

[[Using chkdsk with open files
If you specify the /f command-line option, chkdsk sends an error message if
there are open files on the disk. If you do not specify the /f command-line
option and open files exist, chkdsk might report lost allocation units on
the disk. This could happen if open files have not yet been recorded in the
file allocation table. If chkdsk reports the loss of a large number of
allocation units, consider repairing the disk.]]
From...
Chkdsk
http://www.microsoft.com/resources/d...us/chkdsk.mspx

[[In read-only mode, CHKDSK quits before it completes all three phases if it
encounters errors in earlier phases, and CHKDSK is prone to falsely
reporting errors. For example, CHKDSK may report disk corruption if NTFS
happens to modify areas of a disk while CHKDSK is examining the disk. For
correct verification, a volume must be static, and the only way to guarantee
a static state is to lock the volume. CHKDSK locks the volume only if you
specify the /F switch (or the /R switch, which implies /F). You may need to
run CHKDSK more than once to get CHKDSK to complete all its passes
in read-only mode. ]]
From...
An Explanation of the New C and I Switches That Are Available to Use with
Chkdsk.exe
http://support.microsoft.com/default...b;en-us;314835

To take advantage of all the Chkdsk parameters, use the command-line version
of Chkdsk.

Describes how to use the chkdsk command at the command line.
http://www.microsoft.com/windowsxp/h.../en/chkdsk.asp

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Glen hunted and pecked:
I just reread what I wrote and while I meant to say checkdisk doesnt log
its results in event viewer I didn't write it. So I'll attempt to rewrite
it for clarity. There are no entries for checkdisk in event viewer if i
run checkdisk from within windows. If I run checkdisk from the
commandline its logged in event viewer.
This behaviour is on two computers both with fresh installations of xp
pro. This isn't new behaviour I have never seen a log entry for checkdisk
after running it from within windows. Does your installation log is
checkdisk runs if you run it within windows. I find it hard to believe
both ny computers have a fault as both are new installations.

Glen



"Glen" wrote in message
...
You are completely misunderstanding what I wrote. There is no log entry
for checkdisk if I run checkdisk from within windows. There are only log
entries if I run checkdisk from the commandline.

Glen


"Wesley Vogel" wrote in message
...
Running chkdisk without rebooting is a waste of time. Same as CHKDSK in
read-only mode, see below.

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

This will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

From: Doug Knox
-----

Don't bother even running CHKDSK in read-only mode.

1. In My Computer or Windows Explorer, right-click the volume you want
to check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

o To run Chkdsk by using the /f parameter, select the Automatically fix
file
system errors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking. All files must be closed for this program to run. If the drive
is
currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your
drive is
not available to run other tasks while the disk is being checked.]]

o To run Chkdsk by using the /r parameter, select the Scan for and
attempt
recovery of bad sectors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during disk
checking, locates bad sectors, and recovers readable information. All
files
must be closed for this program to run. If the drive is currently in
use, a
message asks if you want to reschedule the disk checking for the next
time
you restart your computer. Your drive is not available to run other
tasks while the disk is being checked. If you select this option, you
do not need
to select Automatically fix file system errors. Windows fixes any errors
on
the disk.]]

You have to reboot for Error-checking to run.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Glen hunted and pecked:
When I run checkdisk on any drive/partition from within windows xp pro
It
doesnt seem to log its findings anywhere. If I run checkdisk from
outside
windows from commandline and boot back into windows I can see the info
in
event viewer. Where does checkdisk log its info? This behaviour is on
both
my computers even after reformating and reinstalling.

Glen

Even when I run it checking automatically fix file system errors and scan
for bad sectors it still doesn't log the results. I have a hard drive that
has some bad sectors but has no data on at the moment and to monitor the
ongoing state of the drive I need to run checkdisk and see the results. I
could always reboot and do it from the command line but its a pain when
windows should log its findings.

Glen


"Wesley Vogel" wrote in message
...
Glen,

CHKDSK does *not* work correctly in the read-only mode. So it would be a
waste of time if chkdsk logged its results in the read-only mode anyway.

Running chkdsk without rebooting is a waste of time. It is the same as
running chkdsk in the read-only mode.

You have to reboot your machine (both of them) in order for chkdsk to work
correctly.

Here are some reasons...

[[Chkdsk might not accurately report information in read-only mode.]]
From...
Chkdsk
http://www.microsoft.com/resources/d...b_tol_pwfd.asp

[[If you run chkdsk without the /f command-line option on an active
partition, it might report spurious errors because it cannot lock the
drive.]]

[[Using chkdsk with open files
If you specify the /f command-line option, chkdsk sends an error message
if
there are open files on the disk. If you do not specify the /f
command-line
option and open files exist, chkdsk might report lost allocation units on
the disk. This could happen if open files have not yet been recorded in
the
file allocation table. If chkdsk reports the loss of a large number of
allocation units, consider repairing the disk.]]
From...
Chkdsk
http://www.microsoft.com/resources/d...us/chkdsk.mspx

[[In read-only mode, CHKDSK quits before it completes all three phases if
it
encounters errors in earlier phases, and CHKDSK is prone to falsely
reporting errors. For example, CHKDSK may report disk corruption if NTFS
happens to modify areas of a disk while CHKDSK is examining the disk. For
correct verification, a volume must be static, and the only way to
guarantee
a static state is to lock the volume. CHKDSK locks the volume only if you
specify the /F switch (or the /R switch, which implies /F). You may need
to
run CHKDSK more than once to get CHKDSK to complete all its passes
in read-only mode. ]]
From...
An Explanation of the New C and I Switches That Are Available to Use with
Chkdsk.exe
http://support.microsoft.com/default...b;en-us;314835

To take advantage of all the Chkdsk parameters, use the command-line
version
of Chkdsk.

Describes how to use the chkdsk command at the command line.
http://www.microsoft.com/windowsxp/h.../en/chkdsk.asp

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Glen hunted and pecked:
I just reread what I wrote and while I meant to say checkdisk doesnt log
its results in event viewer I didn't write it. So I'll attempt to rewrite
it for clarity. There are no entries for checkdisk in event viewer if i
run checkdisk from within windows. If I run checkdisk from the
commandline its logged in event viewer.
This behaviour is on two computers both with fresh installations of xp
pro. This isn't new behaviour I have never seen a log entry for checkdisk
after running it from within windows. Does your installation log is
checkdisk runs if you run it within windows. I find it hard to believe
both ny computers have a fault as both are new installations.

Glen



"Glen" wrote in message
...
You are completely misunderstanding what I wrote. There is no log entry
for checkdisk if I run checkdisk from within windows. There are only log
entries if I run checkdisk from the commandline.

Glen


"Wesley Vogel" wrote in message
...
Running chkdisk without rebooting is a waste of time. Same as CHKDSK
in
read-only mode, see below.

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

This will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

From: Doug Knox
-----

Don't bother even running CHKDSK in read-only mode.

1. In My Computer or Windows Explorer, right-click the volume you want
to check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

o To run Chkdsk by using the /f parameter, select the Automatically fix
file
system errors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during
disk
checking. All files must be closed for this program to run. If the
drive
is
currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your
drive is
not available to run other tasks while the disk is being checked.]]

o To run Chkdsk by using the /r parameter, select the Scan for and
attempt
recovery of bad sectors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during
disk
checking, locates bad sectors, and recovers readable information. All
files
must be closed for this program to run. If the drive is currently in
use, a
message asks if you want to reschedule the disk checking for the next
time
you restart your computer. Your drive is not available to run other
tasks while the disk is being checked. If you select this option, you
do not need
to select Automatically fix file system errors. Windows fixes any
errors
on
the disk.]]

You have to reboot for Error-checking to run.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Glen hunted and pecked:
When I run checkdisk on any drive/partition from within windows xp pro
It
doesnt seem to log its findings anywhere. If I run checkdisk from
outside
windows from commandline and boot back into windows I can see the info
in
event viewer. Where does checkdisk log its info? This behaviour is on
both
my computers even after reformating and reinstalling.

Glen

Glen,

One of us is missing something here.

Every time chkdsk runs a Bootex.log is created. The info from Bootex.log is
usually sent to the Event Viewer and then the Bootex.log is deleted.

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

This is free.
Restoration Version 2.5.14 Author: Brian Kato
http://www3.telus.net/mikebike/RESTORATION.html

See if for some reason you still have a Bootex.log on your machine and maybe
it's corrupted.

c:\bootex.log or whateverdrive:\bootex.log

If you have a corrupted bootex.log and cannot delete it you may have to run
chkdsk /r

Or you may have to run chkdsk from the Recovery Console.
http://www.annoyances.org/exec/forum/winxp/1080019958

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Glen hunted and pecked:
Even when I run it checking automatically fix file system errors and scan
for bad sectors it still doesn't log the results. I have a hard drive
that has some bad sectors but has no data on at the moment and to monitor
the ongoing state of the drive I need to run checkdisk and see the
results. I could always reboot and do it from the command line but its a
pain when windows should log its findings.

Glen


"Wesley Vogel" wrote in message
...
Glen,

CHKDSK does *not* work correctly in the read-only mode. So it would be a
waste of time if chkdsk logged its results in the read-only mode anyway.

Running chkdsk without rebooting is a waste of time. It is the same as
running chkdsk in the read-only mode.

You have to reboot your machine (both of them) in order for chkdsk to
work correctly.

Here are some reasons...

[[Chkdsk might not accurately report information in read-only mode.]]
From...
Chkdsk

http://www.microsoft.com/resources/d...b_tol_pwfd.asp

[[If you run chkdsk without the /f command-line option on an active
partition, it might report spurious errors because it cannot lock the
drive.]]

[[Using chkdsk with open files
If you specify the /f command-line option, chkdsk sends an error message
if
there are open files on the disk. If you do not specify the /f
command-line
option and open files exist, chkdsk might report lost allocation units on
the disk. This could happen if open files have not yet been recorded in
the
file allocation table. If chkdsk reports the loss of a large number of
allocation units, consider repairing the disk.]]
From...
Chkdsk

http://www.microsoft.com/resources/d...us/chkdsk.mspx

[[In read-only mode, CHKDSK quits before it completes all three phases if
it
encounters errors in earlier phases, and CHKDSK is prone to falsely
reporting errors. For example, CHKDSK may report disk corruption if NTFS
happens to modify areas of a disk while CHKDSK is examining the disk. For
correct verification, a volume must be static, and the only way to
guarantee
a static state is to lock the volume. CHKDSK locks the volume only if
you specify the /F switch (or the /R switch, which implies /F). You may
need to
run CHKDSK more than once to get CHKDSK to complete all its passes
in read-only mode. ]]
From...
An Explanation of the New C and I Switches That Are Available to Use with
Chkdsk.exe
http://support.microsoft.com/default...b;en-us;314835

To take advantage of all the Chkdsk parameters, use the command-line
version
of Chkdsk.

Describes how to use the chkdsk command at the command line.

http://www.microsoft.com/windowsxp/h.../en/chkdsk.asp

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Glen hunted and pecked:
I just reread what I wrote and while I meant to say checkdisk doesnt log
its results in event viewer I didn't write it. So I'll attempt to
rewrite it for clarity. There are no entries for checkdisk in event
viewer if i run checkdisk from within windows. If I run checkdisk from
the commandline its logged in event viewer.
This behaviour is on two computers both with fresh installations of xp
pro. This isn't new behaviour I have never seen a log entry for
checkdisk after running it from within windows. Does your installation
log is checkdisk runs if you run it within windows. I find it hard to
believe both ny computers have a fault as both are new installations.

Glen



"Glen" wrote in message
...
You are completely misunderstanding what I wrote. There is no log entry
for checkdisk if I run checkdisk from within windows. There are only
log entries if I run checkdisk from the commandline.

Glen


"Wesley Vogel" wrote in message
...
Running chkdisk without rebooting is a waste of time. Same as CHKDSK
in
read-only mode, see below.

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

This will create a chkdsk log.

Paste this into a command prompt...

CHKDSK C: /F C:\CHKDISKLOG.TXT

Hit your Enter key.

Click YES on the popup to reboot.

After CHKDSK has run paste this in Start | Run...

C:\CHKDISKLOG.TXT

Click OK.

From: Doug Knox
-----

Don't bother even running CHKDSK in read-only mode.

1. In My Computer or Windows Explorer, right-click the volume you want
to check, and then click Properties.
2. On the Tools tab, click Check Now.
3. Check both boxes:

o To run Chkdsk by using the /f parameter, select the Automatically
fix file
system errors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during
disk
checking. All files must be closed for this program to run. If the
drive
is
currently in use, a message asks if you want to reschedule
the disk checking for the next time you restart your computer. Your
drive is
not available to run other tasks while the disk is being checked.]]

o To run Chkdsk by using the /r parameter, select the Scan for and
attempt
recovery of bad sectors check box, and then click Start.
[[Specifies whether Windows repairs file-system errors found during
disk
checking, locates bad sectors, and recovers readable information. All
files
must be closed for this program to run. If the drive is currently in
use, a
message asks if you want to reschedule the disk checking for the next
time
you restart your computer. Your drive is not available to run other
tasks while the disk is being checked. If you select this option, you
do not need
to select Automatically fix file system errors. Windows fixes any
errors
on
the disk.]]

You have to reboot for Error-checking to run.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In ,
Glen hunted and pecked:
When I run checkdisk on any drive/partition from within windows xp
pro It
doesnt seem to log its findings anywhere. If I run checkdisk from
outside
windows from commandline and boot back into windows I can see the
info in
event viewer. Where does checkdisk log its info? This behaviour is on
both
my computers even after reformating and reinstalling.

Glen