How long does it take for chkdsk to correct errors in the boot file?

[BBCMember]

One of the wires came out of the socket of the power plug that goes into the back of the hard drive, which was the cause of it not showing up. So, I replaced it. When I started the computer back up again, it said that it needed to perform a chkdsk on the drive that I just plugged back in (it was still plugged into the mobo the whole time, and the wire had busted about a week ago). So, I let it.

A lot of areas were "unreadable." Then, it started to repair them. It then got to the boot file (even though there is no OS on it), and it has been "Correcting errors in the Boot File" for about 25 minutes. Is this normal based on this situation? How much longer will it take?

TIA

 

[Severian]

depends on the amount of corruption it finds. I've seen instances where running chkdsk /r from the recovery console, for example, takes at least an hour, often times more.

If you still have problems after checkdisk finishes, you may want to try the above command from the recovery console.

good luck

 

[BBCMember]

OK. Thanks. When it does a chkdsk on its own without you prompting it to, does it include the processes that occur when you use the /r command?

 

[Severian]

frankly I'm not sure, it seems to, but since they are done from different angles, so to speak, I suppose there might be some areas in which they differ. Whenever I've gotten the checkdisk prompt on startup, it usually takes less time than throught the recovery console, so my impression has always been that doing it from the console is more thorough, although I don't really have any proof of that.

 

[BBCMember]

OK. Thanks.

 

[kingtas]

I once let checkdisk repair some corrupt files on a PC I was working on and it totally trashed files Windows needs to boot and run properly (renamed them). I had to reformat and load everything after I salvaged the documents from the drive.

Ever since then, I'm afraid of checkdisk.

 

[BBCMember]

Wow. Not cool.