Checkdisk results

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When I run chkdsk on my hard drive, the results appear on the screen for such
a short time that I'm not able to read them. Are the results written to a
file which I can call up to view?
Thanks,
Robert
 
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.]]

See these for help interpreting the chkdsk log.

"CHKDSK detected minor inconsistencies" error message in Windows 2000 and in
Windows NT
http://support.microsoft.com/kb/109524

Windows 2000 Chkdsk Reports Cleaning Unused Security Descriptors
http://support.microsoft.com/kb/255008

Tip: Don't Panic At CHKDSK "Security Descriptor" Cleanup
http://www.winmag.com/columns/powerw2k/2000/46.htm#tip

How to locate and correct disk space problems on NTFS volumes in Windows XP
http://support.microsoft.com/kb/315688

See also...
Understanding what CHKDSK does
here...

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

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Thanks for your detailed reply, it answered my question. I did a chkdsk about
a half hour ago, then did a restart. There was no event 1001 listed for this
time but there was one listed for around 5PM today. Does that sound right?
Robert
 
Robert,
about a half hour ago, then did a restart. There was no event 1001 listed
for this time but there was one listed for around 5PM today. Does that
sound right?

Your post was made on Sat, 2 Sep 2006 18:18:01 -0700

I have no idea what time zone you are in, so a half your ago and 5PM do not
compute for me.

All CDO posters are at -0700 GMT.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Wes,
I'm in the eastern time zone. I just did 2 more chkdsk's, one from Start-
Run- CHKDSK and one from Drive C: - Properties - Tools - Error Checking.
Neither of them showed up as an event 1001. The latest event 1001 appearing
in the list is one at at ~ 5PM yesterday. Do you know what I'm doing wrong?
Robert
 
Robert,

It sounds like you're running chkdsk in read-only mode.

Not checking either or both boxes in the GUI version or not using the /f or
/r switches in a command prompt is running chkdsk in read-only mode.

Don't even bother running CHKDSK in read-only mode. It is a waste of time
and prone to not accurately reporting information. CHKDSK might report
spurious errors because it cannot lock the drive.

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.

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.

You have to reboot for Error-checking to run.

Checking both boxes using the Graphical User Interface is the same as using
chkdsk from a command prompt with the /f and /r switches.

chkdsk c: /f /r

You can type: chkdsk /? in a command prompt for Help.

[[Chkdsk might not accurately report information in read-only mode.]]
From...
Chkdsk
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmb_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/documentation/windows/xp/all/proddocs/en-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.aspx?scid=kb;en-us;314835

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

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Wes,

I ran checkdisk in the GUI mode and checked both boxes. It worked fine and
created an Event 1001. Bad clusters in one file were replaced by Windows, and
there were 20KB in bad sectors. That sounds pretty respectable for a 80GB
hard disk.
This process reminds me of how it used to be done in DOS.
Thanks for all your help,

Robert


Wesley Vogel said:
Robert,

It sounds like you're running chkdsk in read-only mode.

Not checking either or both boxes in the GUI version or not using the /f or
/r switches in a command prompt is running chkdsk in read-only mode.

Don't even bother running CHKDSK in read-only mode. It is a waste of time
and prone to not accurately reporting information. CHKDSK might report
spurious errors because it cannot lock the drive.

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.

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.

You have to reboot for Error-checking to run.

Checking both boxes using the Graphical User Interface is the same as using
chkdsk from a command prompt with the /f and /r switches.

chkdsk c: /f /r

You can type: chkdsk /? in a command prompt for Help.

[[Chkdsk might not accurately report information in read-only mode.]]
From...
Chkdsk
http://www.microsoft.com/resources/...windows/xp/all/reskit/en-us/prmb_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/documentation/windows/xp/all/proddocs/en-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.aspx?scid=kb;en-us;314835

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

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
rschmitt said:
Wes,
I'm in the eastern time zone. I just did 2 more chkdsk's, one from Start-
Run- CHKDSK and one from Drive C: - Properties - Tools - Error Checking.
Neither of them showed up as an event 1001. The latest event 1001
appearing in the list is one at at ~ 5PM yesterday. Do you know what I'm
doing wrong? Robert
 
Keep having fun, Robert. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
rschmitt said:
Wes,

I ran checkdisk in the GUI mode and checked both boxes. It worked fine and
created an Event 1001. Bad clusters in one file were replaced by Windows,
and there were 20KB in bad sectors. That sounds pretty respectable for a
80GB hard disk.
This process reminds me of how it used to be done in DOS.
Thanks for all your help,

Robert


Wesley Vogel said:
Robert,

It sounds like you're running chkdsk in read-only mode.

Not checking either or both boxes in the GUI version or not using the /f
or /r switches in a command prompt is running chkdsk in read-only mode.

Don't even bother running CHKDSK in read-only mode. It is a waste of
time and prone to not accurately reporting information. CHKDSK might
report spurious errors because it cannot lock the drive.

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.

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.

You have to reboot for Error-checking to run.

Checking both boxes using the Graphical User Interface is the same as
using chkdsk from a command prompt with the /f and /r switches.

chkdsk c: /f /r

You can type: chkdsk /? in a command prompt for Help.

[[Chkdsk might not accurately report information in read-only mode.]]
From...
Chkdsk
http://www.microsoft.com/resources/...mentation/windows/xp/all/reskit/en-us/prmb_to
l_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/documentation/windows/xp/all/proddocs/en-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.aspx?scid=kb;en-us;314835

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

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
rschmitt said:
Wes,
I'm in the eastern time zone. I just did 2 more chkdsk's, one from
Start- Run- CHKDSK and one from Drive C: - Properties - Tools - Error
Checking. Neither of them showed up as an event 1001. The latest event
1001 appearing in the list is one at at ~ 5PM yesterday. Do you know
what I'm doing wrong? Robert


:

Robert,

about a half hour ago, then did a restart. There was no event 1001
listed for this time but there was one listed for around 5PM today.
Does that sound right?

Your post was made on Sat, 2 Sep 2006 18:18:01 -0700

I have no idea what time zone you are in, so a half your ago and 5PM do
not compute for me.

All CDO posters are at -0700 GMT.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In rschmitt <[email protected]> hunted and pecked:
Thanks for your detailed reply, it answered my question. I did a
chkdsk about a half hour ago, then did a restart. There was no event
1001 listed for this time but there was one listed for around 5PM
today. Does that sound right? Robert



:

When I run chkdsk on my hard drive, the results appear on the screen
for such a short time that I'm not able to read them. Are the results
written to a file which I can call up to view?
Thanks,
Robert
 
Wes,

Thank you for your help and patience.

Robert


Wesley Vogel said:
Keep having fun, Robert. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
rschmitt said:
Wes,

I ran checkdisk in the GUI mode and checked both boxes. It worked fine and
created an Event 1001. Bad clusters in one file were replaced by Windows,
and there were 20KB in bad sectors. That sounds pretty respectable for a
80GB hard disk.
This process reminds me of how it used to be done in DOS.
Thanks for all your help,

Robert


Wesley Vogel said:
Robert,

It sounds like you're running chkdsk in read-only mode.

Not checking either or both boxes in the GUI version or not using the /f
or /r switches in a command prompt is running chkdsk in read-only mode.

Don't even bother running CHKDSK in read-only mode. It is a waste of
time and prone to not accurately reporting information. CHKDSK might
report spurious errors because it cannot lock the drive.

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.

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.

You have to reboot for Error-checking to run.

Checking both boxes using the Graphical User Interface is the same as
using chkdsk from a command prompt with the /f and /r switches.

chkdsk c: /f /r

You can type: chkdsk /? in a command prompt for Help.

[[Chkdsk might not accurately report information in read-only mode.]]
From...
Chkdsk
http://www.microsoft.com/resources/...mentation/windows/xp/all/reskit/en-us/prmb_to
l_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/documentation/windows/xp/all/proddocs/en-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.aspx?scid=kb;en-us;314835

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

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In rschmitt <[email protected]> hunted and pecked:
Wes,
I'm in the eastern time zone. I just did 2 more chkdsk's, one from
Start- Run- CHKDSK and one from Drive C: - Properties - Tools - Error
Checking. Neither of them showed up as an event 1001. The latest event
1001 appearing in the list is one at at ~ 5PM yesterday. Do you know
what I'm doing wrong? Robert


:

Robert,

about a half hour ago, then did a restart. There was no event 1001
listed for this time but there was one listed for around 5PM today.
Does that sound right?

Your post was made on Sat, 2 Sep 2006 18:18:01 -0700

I have no idea what time zone you are in, so a half your ago and 5PM do
not compute for me.

All CDO posters are at -0700 GMT.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In rschmitt <[email protected]> hunted and pecked:
Thanks for your detailed reply, it answered my question. I did a
chkdsk about a half hour ago, then did a restart. There was no event
1001 listed for this time but there was one listed for around 5PM
today. Does that sound right? Robert



:

When I run chkdsk on my hard drive, the results appear on the screen
for such a short time that I'm not able to read them. Are the results
written to a file which I can call up to view?
Thanks,
Robert
 
You are entirely welcome, Robert.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
robert said:
Wes,

Thank you for your help and patience.

Robert


Wesley Vogel said:
Keep having fun, Robert. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
rschmitt said:
Wes,

I ran checkdisk in the GUI mode and checked both boxes. It worked fine
and created an Event 1001. Bad clusters in one file were replaced by
Windows, and there were 20KB in bad sectors. That sounds pretty
respectable for a 80GB hard disk.
This process reminds me of how it used to be done in DOS.
Thanks for all your help,

Robert


:

Robert,

It sounds like you're running chkdsk in read-only mode.

Not checking either or both boxes in the GUI version or not using the
/f or /r switches in a command prompt is running chkdsk in read-only
mode.

Don't even bother running CHKDSK in read-only mode. It is a waste of
time and prone to not accurately reporting information. CHKDSK might
report spurious errors because it cannot lock the drive.

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.

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.

You have to reboot for Error-checking to run.

Checking both boxes using the Graphical User Interface is the same as
using chkdsk from a command prompt with the /f and /r switches.

chkdsk c: /f /r

You can type: chkdsk /? in a command prompt for Help.

[[Chkdsk might not accurately report information in read-only mode.]]
From...
Chkdsk
http://www.microsoft.com/resources/...mentation/windows/xp/all/reskit/en-us/prmb_to
l_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/documentation/windows/xp/all/proddocs/en-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.aspx?scid=kb;en-us;314835

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

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In rschmitt <[email protected]> hunted and pecked:
Wes,
I'm in the eastern time zone. I just did 2 more chkdsk's, one from
Start- Run- CHKDSK and one from Drive C: - Properties - Tools - Error
Checking. Neither of them showed up as an event 1001. The latest event
1001 appearing in the list is one at at ~ 5PM yesterday. Do you know
what I'm doing wrong? Robert


:

Robert,

about a half hour ago, then did a restart. There was no event 1001
listed for this time but there was one listed for around 5PM today.
Does that sound right?

Your post was made on Sat, 2 Sep 2006 18:18:01 -0700

I have no idea what time zone you are in, so a half your ago and 5PM
do not compute for me.

All CDO posters are at -0700 GMT.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In rschmitt <[email protected]> hunted and pecked:
Thanks for your detailed reply, it answered my question. I did a
chkdsk about a half hour ago, then did a restart. There was no event
1001 listed for this time but there was one listed for around 5PM
today. Does that sound right? Robert



:

When I run chkdsk on my hard drive, the results appear on the
screen for such a short time that I'm not able to read them. Are
the results written to a file which I can call up to view?
Thanks,
Robert
 

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

Similar Threads


Back
Top