Chkdsk - "Windows was unable to complete the disk check" stuck on phase 2

[esbo]

Take the HDD out and stick into another system with the same OS and run the CHKDSK /F on it and see if you can get pass the stage your stuck on. That other system HDD Controller might be acting up on you causing the scan to get stuck at random spots. I won't stick with one system if it's acting up. Need to move on to another system to test the drive on.

If you don't want to take out the unit you can run IOBIT Disk Doctor through XP up to Windows 7 and let it scan for errors/fix them. HD Tune is another one you can use under Windows on that HDD.

Well I only have one system (that would support a drive of that size).
It has got past stage 2 and completed through stage 3 now.
Not sure why it did no do that before, maybe it was because I was running other
stuff (surfing) at the time, probably not too surprising really.
It may also have been that deleting a lot of temporary files helped, that would certainly
have seeded things up.
Also I have a dual core processor now (X2 3800 as opposed to a Sempron 3000) so if
it was taking 3 times longer to run before it may have looked like it had got stuck when in reality it just needed more time.
I may try some of those utilities some time when I do not require my computer so much for other things, so thanks.

 

[tipstir]

Sounds like you had way to many lost or bad clusters on the HDD. Sounds like your all set now.

 

[esbo]

Sounds like you had way to many lost or bad clusters on the HDD. Sounds like your all set now.

Yes well I was getting a lot of reboots due to having a stick of bad memeory inso I would expect some problems from that.
Maybe I had other (very minor) issues in the past when chkdsk would not run, however it
I did have to power off hard reboot it never ran chkdsk at start-up before.

I am not sure if I had lost or bad clusters, the errors I reported here were such as:-

"Index entry PPC047~1.JPG of index $I30 in file 0x37c4d points to unused file 0x2157c."

I think these were just caused by bad memory, not a bad drive.

eg
0 KB in bad sectors.

Sounds promising!!

I wish the new memory I got was in as good shape as my drive, that memory has caused me so much grief (still have to get a refund yet).

So that's another issue isn't it? Your 'brand new drive' which you got at a great price on ebay may turn out to be in worse shape than the drive you just slung in the bin!! :haha:

That's not far off my memory buying experience!

However I was just increasing my memory with another 1 gig, the existing memory, which
I have put back in is running fine!! (touch wood )

 

[tipstir]

Bad memory then the OS would swap memory to VRM (HDD) instead. This all gets so complex. So then you get bad index (clusters called differently on other software fixers) but in all now you know. I had the same thing happen last week. It was the PSU keep dropping the system and then the OS dump memory chunks to the VRM (HDD) so then the HDD won't boot into the OS. Caused the OS to load a startup repairer. In all everything works here. This is the only method available.