Need to run chkdsk /f but C: drive locked

Soldato
Joined
7 Mar 2005
Posts
19,607
Location
LU7
Running a simple chkdsk as:
Code:
chkdsk c:
I find there is something wrong and needs to be fixed. Obviously
Code:
chkdsk c: /f
won't work in XP. So I accept the offer to run chkdsk on next reboot. chkdsk runs but it doesn't invoke the /f parameter so the error is never fixed.

I also tried booting into Safe mode so I could run
Code:
chkdsk c: /f
but Windows is saying that C: is still locked. How can I force XP or my PC to run
Code:
chkdsk c: /f
?

I just ran
Code:
chkdsk c: /f
then restarted. Yet another
Code:
chkdsk c:
reveals the errors are still there so I'm not getting the /f parameter run during the reboot at all.

So how can I fix these errors?
 
Could boot to XP CD and choose Recovery console.

Then you can force a CHKDSK, think its CHKDSK /P

I cannot remember but it tells you every CMD by typing HELP and when you try CHKDSK and it tells you it does not need run one it will tell you the CMD to force it to CHKDSK.
 
Right click the drive in My Computer then choose Properties, Tools, Check Now. Tick both boxes and Start. Reboot and see if the error gets fixed.
 
Could boot to XP CD and choose Recovery console.

Then you can force a CHKDSK, think its CHKDSK /P

I cannot remember but it tells you every CMD by typing HELP and when you try CHKDSK and it tells you it does not need run one it will tell you the CMD to force it to CHKDSK.
Interesting. This is what I concluded last night. :) Will try it later.

Right click the drive in My Computer then choose Properties, Tools, Check Now. Tick both boxes and Start. Reboot and see if the error gets fixed.
Tried that. It won't run with both boxes ticked as the drive is locked.
 
OK I rebooted after doing the My Computer procedure. chkdsk ran for much longer this time but when I did another chkdsk c: in the command prompt after getting back into XP there were still errors.

I'll try the Recovery console on the XP cd later.
 
I ran the chkdsk from the Recovery console last night. It claimed to have fixed the errors. So when I ran a chkdsk from the command prompt in Windows to check I was a bit suprised to see some errors being reported. Doesn't sound too good tbh. Anyone else reckon hard drive is about to pack it in if I keep getting errors on the disk after fixing them?
 
Back
Top Bottom