CHKDSK inserting thousands of indexes

[Paul B.]

Looks like I've suddenly got a problem. While rebooting a keyboard driver
installation, Chkdsk wanted to check the C drive. It seemed to be stalled
well after Stage 3 of 3 was completed, so I forced the system down.

Sure enough, it came back with the reboot and I let it run again. This time
it found errors related to "File 9" in Stage 2, Index checking. In Stage 3
it began to Insert *thousands* of Indexes into File 9. I was determined to
let it do its thing, but after maybe 1500 insertions I began to think Chkdsk
was hosing my entire drive.

I forced shutdown again and overrode Chkdsk's desire to run again. I'm
booted up now, but I'm getting corrupt files notices all over the place.

The way forward?

Thanks much,
Paul

 

[Homer J. Simpson]

If there are problems with your disk structure, chkdsk sole purpose in life
is to fix them--let it do its job to completion. By interrupting it
(repeatedly), you may very well be compounding the problem.

Realistically, after you've stopped it, what did you intend to do next
anyway? At that point you're not in any better state than before.

 

[Paul B]

If there are problems with your disk structure, chkdsk sole purpose in life
is to fix them--let it do its job to completion. By interrupting it
(repeatedly), you may very well be compounding the problem.

Realistically, after you've stopped it, what did you intend to do next
anyway? At that point you're not in any better state than before.

I've heard too many stories of chkdsk gone wild, overwriting whole disks,
and I believe that's exactly what it was on its way to do. Anyway, I think
the install was melting down. I did a low level format and reinstall today.

Thanks,
p.

 

[Homer J. Simpson]

If there are problems with your disk structure, chkdsk sole purpose in

I've heard too many stories of chkdsk gone wild, overwriting whole disks,
and I believe that's exactly what it was on its way to do. Anyway, I think
the install was melting down. I did a low level format and reinstall
today.

Still--what were your alternatives? Continue using a disk with a bad file
allocation table?