CHKDSK takes hours and hangs on the free space part

[stevvie]

I set chkdsk to run on next bootup on my XP and now it runs but takes about 2.5 hours to complete on a Samsung Spinpoint 512Gb SATA2 on an MSI P35 NEO2 motherboard. It then hangs on the free space part. If I then reboot again It starts the process all over again. I have since run the disk through the windows7 diskcheck program with flying colours. I'm now looking for a way to STOP chkdsk from starting when booting XP as it gives NO countdown what so ever and hangs EVERY time on the free space part after about 2-2.5 hours of running.

Thanks

 

[VinDSL]

Hrm. Well...

I go by gut *feelings* a lot, and my gut is telling me something might be dreadfully wrong with that drive. You're just living in a period of grace...

Don't take this the wrong way, but I don't *think* sticking your head in the sand is going to fix the problem!

Personally, I don't like playing games with drive faults.

If it was me... rather than turning off the flag bit (or whatever), I would backup my data and do an fdisk, format, and fresh install.

If the problem persists, I'd drill holes in it and throw it way.

How old is that drive?!?!?!

 

[stevvie]

NO I turned the flag on to check it on next startup. So far I've checked the drive in windows 7, on anotrher PC running XP X86 SP3 and it passed on both of them with NO problems. It's just when I use this drive as my main bootup OS (XP X64 SP2) that it hangs. Somebody suggested doing it in a safemode bootup, that I'm gonna try later. Drives only about 6-7 months old so still under warranty and passes all the drive checks I've tried in hirens 9.9 and XP X86 and windows7. The only one it is having a problem with is the main OS XP X64.

 

[lopri]

What anti-virus program do you use?

 

[bloodugly]

Try formatting/partitioning/installing in a different computer with a different OS. If it still does weird stuff after all variables have been accounted for, then the drive needs to be replaced. Only way I can think of to definitely check it, unless somebody else can think of something else. I don't claim to be all-knowing I'm just into the process of elimination.

 

[stevvie]

anti virus is nod32 Version3 64bit.
renamed ALL the windows folders on this drive installed windows X64. I then set chkdsk to check on startup and it checked the disk in about 15 minutes with NO error what so ever. So I renamed my old X64 back and tried again and still the same problem. So I just renamed chkdsk.exe in both system32 and sys64wow and the same with autochk in another OS. and the origional X64 system booted and then removed the offending registry entry and renamed all the autochk and chkdsk back and it's ok now. Just a borked X64 install I suppose. I'll live with it seeing as Windows7 is so close. Thanks for the help everyone

 

[ImDonly1]

Didn't read whole thread. but from first post you are having the chkdsk loop where chkdsk keeps running everytime you restart the computer.

This just happened to me yesterday. So I will tell you how to do it.

First you need Ultimate Boot CD 4 Win. From here http://www.ubcd4win.com/downloads.htm
This will allow you to edit the registry.

Next when you boot from the ultimate boot cd run the remote registry editor.

Next change this registry entry at this link http://support.microsoft.com/kb/158675

This will stop chkdsk from running at the next boot.

 

[lopri]

Well, if you can, it's not a bad idea to let it run through overnight. Sometimes chkdsk can take veeeeeeeeeeeeeeerrrrrry long time.

But if it hangs for sure (usually at the same spot), then well.. it's complicated. Did you search MS hotfixes? There are some Hftfixes available from MS that are not seen in Windows Updates. You'll have to find them. It may or may not help resolving the issue.

I had a chkdsk problem with Kaspersky in the past. Kaspersky uses a whatever 'engine' to verify the system's integrity and it caused chkdsk hang. It's a known issue and they gave me an uninstall tool to remove Kaspersky completely, in order to finish chkdsk. I don't know whether NOD32 can do something like that or not.

 

[stevvie]

I did indeed let it run overnight and when I got up windows had booted after about 7 hours of CHKDSK, ascertained from uptime. I may do another one later to see if it still takes the time. I'm thinking it's the one that is with XP X64 that is to fault as it has a different version number than the one that is installed on my XP X86 system.

 

[VinDSL]

LoL! Sounds like a Linux mega server story...

I've seen RAID 10 arrays go read-only and take 2-3 days to fsck!