Has something effected chkdsk?

[stduc]

Has anyone noticed that recently (I assume in the last few months) that running chkdsk on the C drive never gives a clean result? At least not for me on 2 machines. If you use the /F parameter and reboot then no errors are found!

A typical live result is like this.

The type of the file system is NTFS.
Volume label is Boot_8757.

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 is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

61440560 KB total disk space.
31464076 KB in 97416 files.
34396 KB in 9988 indexes.
0 KB in bad sectors.
270320 KB in use by the system.
65536 KB occupied by the log file.
29671768 KB available on disk.

4096 bytes in each allocation unit.
15360140 total allocation units on disk.
7417942 allocation units available on disk.

Thoughts? anyone?

 

[goombawaho]

Why would you not be running CHKDSK /F in the first place. That's the only option that will clean up the errors found.

So, doing the above should get a clean result after running it a couple times in a row.

If errors persist, I'd check the hard drives in question with the manufacturer's utility. Could be disks starting to croak.