Cleaning up minor inconsistencies on the drive.

[aldi]

Anyone used to seeing this error on chkdsk /f on a regular basis? i.e. every reboot if you force a chkdsk you get this in the event log. I've been kicking this bloody machine for far too long now, replaced every component and still on a clean format of XP I get:

Cleaning up minor inconsistencies on the drive.
Cleaning up 153 unused index entries from index $SII of file 0x9.
etc.
etc.

Which since the origional fault was a badly corrupted drive (twice) had me convinced that something was fecked. However this article amongst other google hits:
http://support.microsoft.com/kb/25500
Suggests that its nothing to worry about. Now maybe I'm being a bit old fasioned but I've never noticed these errors as a routine matter before, normally you expect chkdsk results to be clean... has anyone come accross this before? I'm loathe to put this back out again and get it back next week...

[BliarOut]

The article suggests it was fixed in 2K SP1. Is your XP installation fully service packed?

Does sound like it's time to replace the drive though.

[aldi]

Fresh format from an SP2 OEM CD - tried a couple of CDs, CD-drives, 2x SATA HDD's and a PATA HDD, moby, cables, PSU, RAM - all the same symptoms!

[BliarOut]

So nothing is the same but you are getting the same symptom?

Just want to apply some logic to this

[aldi]

Yep all new bits, same symptoms

Newsflash, IBM drive fitness test back to back with the origional disk and the current disk consistently reports the origional bad and the current one good, which makes me think the origional problem *was* caused by the origional disk, and these current errors are something that can be ignored... or am I grasping at straws?? I'm just sure its not normal to see these 'minor inconsistencies' in the chkdsk results all the time

[BliarOut]

So a vendors drive test comes back good, but on the original drive it shows errors... That's a start. And chkdsk isn't kicking in automatically, you're instructing it to run?

As I see it there must be something common between your installs. Are the replacement components identical, just replaced? I would suggest you need to identify the common components and investigate the drivers/firmware IMO.

[aldi]

All parts replaced with the same model, except the drives - replaced a maxtor (bad) with a samsung. Tried disablind the drive's write cache and jumpering it down to sata-1, no change! I know its not a hardware incompatability because I've got 7-8 identical machines out there with no problems, all built with the same drivers & BIOS. How wierd is it that it can run 100% fine with no crashes except this unusual chkdsk result?

I've ghosted a no-probs machine onto this one, will run it for a week on this non-knackered disk and see what happens...