ChkDsk Finds Errors, But Does Not Fix?

  • Thread starter Thread starter (PeteCresswell)
  • Start date Start date
P

(PeteCresswell)

-----------------------------------------------------------
D:\>chkdsk C:
The type of the file system is NTFS.
Volume label is System.

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)...
Deleting index entry ad192216_0.gif in index $I30 of file 57313.
Deleting index entry AD1922~1.GIF in index $I30 of file 57313.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

D:\>CHKDSK C: /F
ttype of the file system is NTFS.
clock current drive.

chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) Y

This volume will be checked the next time the system restarts.
-----------------------------------------------------------

I've been through this four times already. Each time, when I
reboot, ChkDsk runs before XP's window comes up. It seems to
end normally, but the summary screen flashes by so fast I can't
read the details.

Last time around, I made a movie of the screen. On that
iteration, at least, ChkDsk reported no errors at all.

But ChkDsk run immediately after that reboot reported errors
different from the screeen paste above - but seemingly the same
as a number or prior runs:
-------------------------------------------------------
C:\>chkdsk C:
The type of the file system is NTFS.
Volume label is System.

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 verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

41945683 KB total disk space.
23800572 KB in 166703 files.
92396 KB in 6397 indexes.
0 KB in bad sectors.
295999 KB in use by the system.
65536 KB occupied by the log file.
17756716 KB available on disk.

4096 bytes in each allocation unit.
10486420 total allocation units on disk.
4439179 allocation units available on disk.
-------------------------------------------------------

Bottom line, though, I keep getting these errors back-to-back.
i.e. Run ChkDsk, see errors, Schedule ChkDsk /F for next boot,
reboot, run ChkDsk, see errors.....

I've run a utility called HD Tune that purports to do a detailed
scan for errors on the drive; but it does not find any.

Is there a way out of this situation without rebuilding the
system?
 
(PeteCresswell) said:
-----------------------------------------------------------
D:\>chkdsk C:
The type of the file system is NTFS.
Volume label is System.

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)...
Deleting index entry ad192216_0.gif in index $I30 of file 57313.
Deleting index entry AD1922~1.GIF in index $I30 of file 57313.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

D:\>CHKDSK C: /F
ttype of the file system is NTFS.
clock current drive.

chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) Y

This volume will be checked the next time the system restarts.
-----------------------------------------------------------

I've been through this four times already. Each time, when I
reboot, ChkDsk runs before XP's window comes up. It seems to
end normally, but the summary screen flashes by so fast I can't
read the details.

Last time around, I made a movie of the screen. On that
iteration, at least, ChkDsk reported no errors at all.

But ChkDsk run immediately after that reboot reported errors
different from the screeen paste above - but seemingly the same
as a number or prior runs:
-------------------------------------------------------
C:\>chkdsk C:
The type of the file system is NTFS.
Volume label is System.

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 verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

41945683 KB total disk space.
23800572 KB in 166703 files.
92396 KB in 6397 indexes.
0 KB in bad sectors.
295999 KB in use by the system.
65536 KB occupied by the log file.
17756716 KB available on disk.

4096 bytes in each allocation unit.
10486420 total allocation units on disk.
4439179 allocation units available on disk.
-------------------------------------------------------

Bottom line, though, I keep getting these errors back-to-back.
i.e. Run ChkDsk, see errors, Schedule ChkDsk /F for next boot,
reboot, run ChkDsk, see errors.....

I've run a utility called HD Tune that purports to do a detailed
scan for errors on the drive; but it does not find any.

Is there a way out of this situation without rebuilding the
system?
Click to expand...


Click on 'Start' then click 'run' and type cmd (enter)
In the black screen command line type
CHKDSK C: /F /R
( I'm not remembering clearly if one leaves a space between two
parameters. I would try it the way I typed it above first, then if you don't
get satisfaction try it with no space between the /f and /r parameter.)

When windows starts the next time it will run chkdsk in repair mode to
delete the entries and repair bad sectors.

You can read about the different parameters below.
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx?mfr=true

and this from Norton
http://service1.symantec.com/support/powerquest.nsf/docid/2004066687571562

Don't be surprised that it takes longer to run it in the /f/r mode.

If you keep getting errors I would consider checking the integrity of the
hard disk with the manufacturer's diagnostic utility. Additionally, if that
comes up negative but you still are getting chkdsk runs on bootup I would
run memtest86 to check the RAM.
 
(PeteCresswell) said:
-----------------------------------------------------------
D:\>chkdsk C:
The type of the file system is NTFS.
Volume label is System.

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)...
Deleting index entry ad192216_0.gif in index $I30 of file 57313.
Deleting index entry AD1922~1.GIF in index $I30 of file 57313.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

D:\>CHKDSK C: /F
ttype of the file system is NTFS.
clock current drive.

chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) Y

This volume will be checked the next time the system restarts.
-----------------------------------------------------------

I've been through this four times already. Each time, when I
reboot, ChkDsk runs before XP's window comes up. It seems to
end normally, but the summary screen flashes by so fast I can't
read the details.

Last time around, I made a movie of the screen. On that
iteration, at least, ChkDsk reported no errors at all.

But ChkDsk run immediately after that reboot reported errors
different from the screeen paste above - but seemingly the same
as a number or prior runs:
-------------------------------------------------------
C:\>chkdsk C:
The type of the file system is NTFS.
Volume label is System.

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 verifying security descriptors (stage 3 of 3)...
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

41945683 KB total disk space.
23800572 KB in 166703 files.
92396 KB in 6397 indexes.
0 KB in bad sectors.
295999 KB in use by the system.
65536 KB occupied by the log file.
17756716 KB available on disk.

4096 bytes in each allocation unit.
10486420 total allocation units on disk.
4439179 allocation units available on disk.
-------------------------------------------------------

Bottom line, though, I keep getting these errors back-to-back.
i.e. Run ChkDsk, see errors, Schedule ChkDsk /F for next boot,
reboot, run ChkDsk, see errors.....

I've run a utility called HD Tune that purports to do a detailed
scan for errors on the drive; but it does not find any.

Is there a way out of this situation without rebuilding the
system?
Click to expand...

Just for fun, if you have the WinXP installer disc, start up
the recovery console (MSDOS command line window) and run CHKDSK
from there. I was playing around with that, a few hours ago,
in a virtual machine.

(Press "R" for recovery)

http://images.techtree.com/ttimages/story/105281_recoveryconsole.gif

(Multiple OS partitions may be identified.
Type the number next to the one you want.
You'll be prompted to enter the Administrator password.)

http://cdnsupport.gateway.com/s/tutorials/images/Topic_37929/160844.gif

Once the command prompt is present, you can type

chkdsk /?

to see the options. And when finished, this will cause a reboot.

exit

The advantage of running chkdsk that way, is C: is not busy, so the
check can repair things. There is no need for it to schedule
a check on the next reboot.

HTH,
Paul
 
Back
Top