Posted 21 June 2010 - 01:54 PM
Over a year ago I started trying to run CHKDSK. It zooms thru task one verifying files. Then it creeps to 5% on verifying indexes and seems to hang up there. It never gives an error msg. It just sits on 5%. Iv'e let it sit like that for as long as 4 or 5 hours before choking the machine w/ the power button. If I knew that it was still running and would eventually finish, I would be happy to let it peacefully grind away. After a recent write error, XP again scheduled me for a CHKDSK session with the same result. Now DEFRAGMENTER won't run b/c the popup says "chkdsk is scheduled, run chkdsk". My HP dv2000t is about 5 yrs old but the HD is only about 2 yrs. I used a drive cloning kit to upgrade to a bigger 7200 rpm HD. So... How long can CHKDSK take? 8 hours? 12 hours? (gulp) Days? It seems like 5 hours is plenty of time to go from 5% to 6% done. The CHKDSK front end is so spectacularly uninformative that I end up feeling like a fool. I love troubleshooting and fiddling w/ stuff but this has got me stopped for the moment.
I've tried to run CHKDSK several ways; from the command prompt, from the run box, double clicking the .exe file in sys32, as well as the CHKDSK bootup prompt of course. I've even tried the disk check utility in Partition Magic. CHKDSK will run with no parameters and finish file and index verification smartly, even deleting a few index entries. But the /r parameter produces this (apparent) hang.
This seems to be similiar to the problem posted by "linlan" above. One of the responses to him was "let it run". My question is; how long?
Let's allow more ram than anyone will ever need, say, 640 kilobytes.