Chkdsk finding unfixable errors?

  • Thread starter Thread starter Chaoticwhizz
  • Start date Start date
C

Chaoticwhizz

Whenever I run chkdsk in read only mode I get the following message that
is pasted below. First, I have ran the error-checking program in the
Tools tab when right-clicking drive C and select Properties. I have
checked both boxes that say "Automatically fix file system errors" and
"Scan for and attempt recovery of bad sectors" It says it must reboot to
scan which I do. It scans in 5 different stages and then reboots again
and acts normally. I don't get any disk errors anywhere else and have no
idea if I should try to fix the errors or not worry about them. Maybe a
false positive? Also it mentions towards the bottom that there is a 65
MB log file that I cannot find. How do I access this log file? I have
Windows XP Home SP 2. The hard drive in question is a SATA from Western
Digital. It's model number is WDC WD800JD-75JNA0. Any info would be
appreciated.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\(user)>chkdsk
The type of the file system is NTFS.
Volume label is Wasteland.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is recovering lost files.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

78116030 KB total disk space.
43266528 KB in 90039 files.
31032 KB in 5627 indexes.
0 KB in bad sectors.
183082 KB in use by the system.
65536 KB occupied by the log file.
34635388 KB available on disk.

4096 bytes in each allocation unit.
19529007 total allocation units on disk.
8658847 allocation units available on disk.
 
You can review CHKDSK in event viewer.Also,youre best bet for running
CHKDSK /R Which combines fix file errors and attempt recovery of bad
sectors,
is to boot to xp cd,recovery,in recovery type:CHKDSK C: /R Type:EXIT When
its thru.
 
Don't bother even running CHKDSK in read-only mode. It is a waste of time
and might not accurately report information. Read on.

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

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

Describes how to use the chkdsk command at the command line.
http://www.microsoft.com/windowsxp/...WINDOWSXP/home/using/productdoc/en/chkdsk.asp


--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Chaoticwhizz said:
Whenever I run chkdsk in read only mode I get the following message that
is pasted below. First, I have ran the error-checking program in the
Tools tab when right-clicking drive C and select Properties. I have
checked both boxes that say "Automatically fix file system errors" and
"Scan for and attempt recovery of bad sectors" It says it must reboot to
scan which I do. It scans in 5 different stages and then reboots again
and acts normally. I don't get any disk errors anywhere else and have no
idea if I should try to fix the errors or not worry about them. Maybe a
false positive? Also it mentions towards the bottom that there is a 65
MB log file that I cannot find. How do I access this log file? I have
Windows XP Home SP 2. The hard drive in question is a SATA from Western
Digital. It's model number is WDC WD800JD-75JNA0. Any info would be
appreciated.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\(user)>chkdsk
The type of the file system is NTFS.
Volume label is Wasteland.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is recovering lost files.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

78116030 KB total disk space.
43266528 KB in 90039 files.
31032 KB in 5627 indexes.
0 KB in bad sectors.
183082 KB in use by the system.
65536 KB occupied by the log file.
34635388 KB available on disk.

4096 bytes in each allocation unit.
19529007 total allocation units on disk.
8658847 allocation units available on disk.
Click to expand...
 
Oops. Forgot...

You have to reboot for Error-checking to run.

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
Wesley Vogel said:
Don't bother even running CHKDSK in read-only mode. It is a waste of time
and might not accurately report information. Read on.

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

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

Describes how to use the chkdsk command at the command line.
http://www.microsoft.com/windowsxp/...WINDOWSXP/home/using/productdoc/en/chkdsk.asp


--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Chaoticwhizz said:
Whenever I run chkdsk in read only mode I get the following message that
is pasted below. First, I have ran the error-checking program in the
Tools tab when right-clicking drive C and select Properties. I have
checked both boxes that say "Automatically fix file system errors" and
"Scan for and attempt recovery of bad sectors" It says it must reboot to
scan which I do. It scans in 5 different stages and then reboots again
and acts normally. I don't get any disk errors anywhere else and have no
idea if I should try to fix the errors or not worry about them. Maybe a
false positive? Also it mentions towards the bottom that there is a 65
MB log file that I cannot find. How do I access this log file? I have
Windows XP Home SP 2. The hard drive in question is a SATA from Western
Digital. It's model number is WDC WD800JD-75JNA0. Any info would be
appreciated.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\(user)>chkdsk
The type of the file system is NTFS.
Volume label is Wasteland.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
CHKDSK is recovering lost files.
CHKDSK is verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

78116030 KB total disk space.
43266528 KB in 90039 files.
31032 KB in 5627 indexes.
0 KB in bad sectors.
183082 KB in use by the system.
65536 KB occupied by the log file.
34635388 KB available on disk.

4096 bytes in each allocation unit.
19529007 total allocation units on disk.
8658847 allocation units available on disk.
Click to expand...
Click to expand...
 
Yes, you would have. You would have eventually done what I usually do,
discovered it by accident. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
Chaoticwhizz said:
Cool, thanks. I never would have found it in event viewer without your
help.

Wesley said:
Oops. Forgot...

You have to reboot for Error-checking to run.

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.]]
Click to expand...
Click to expand...
 
Back
Top