new hard drive problems

[tyjohnson]

I'll try and keep this as short as possible. Last Saturday my 120gig Maxtor HD failed to boot so I ordered a 160gig Hitachi one from Newegg. It got here Thursday and the install went great. I left it disconnected from the net while I installed Norton and my drivers. Then I did a virus scan and ran Windows Update. After that I connect my 120gig Maxtor as a Slave so I can get my MP3/Favorites/Pics and some school work off it. It gets past the post all the way to the XP loading screen and everthing seems to work fine...... untill I see the post screen again. It seems the computer rebooted its self. I boot from the Ultimate Boot CD and it sees the 120gig drive and both its partitions from FDISK. MaxDrive gave me and error code of Y42S57, no clue what that means but it offered to try and fix the problem at the risk of loosing data, so I passed. Now my question is is there anything I can do to recover the data from the drive? I've tried messing with jumpers, putting them on seperate IDE channels, and messing with the bios. Only other things I can think of are Fdisk /mbr or the Savepart program on the UBC. Are there any other things I'm overlooking?

Specs incase it helps:
p4pe
2.66b
512mb RAM
Antec True 430
Win XP Pro w/ Updates

 

[Ice Czar]

first, welcome to the forums

2nd, BIOS > Boot Order, make sure its not trying to boot to the old HDD and hanging up, try changing the boot order from HDD0 to HDD1

fixmbr isnt really applicable as its not booting to that HDD

more than likely youll need to take it up on that offer to fix the drive and recover what you can, there is probably some corruption and it needs to lockout sectors that have gone bad
that would more than likely would be unrecoverable with anything other than forensic data recovery (read lab work)

basically chkdsk lockouts (see Corrupt Files 13th post

If you have the space available to Savepart, go for it first (if its accessable) Ghost has advanced options to ignore errors, do sector by sector copy ect. I havent used savepart yet (or read the manual) so review that for similar options

 

[tyjohnson]

Tried messing with the boot order, that didn't do anything. The 120 gig drive has a was split into 2 partitions, 100gigs and 20gigs each, so I decided to format the 20gig partion from the XP cd, as soon as it started collecting info about the computer I got a blue screen with a STOP: 0x00000024 error. Microsoft Knowledge Base saids it's due to a bad/corrupted ntfs.sys file. They suggest running chkdsk /f to try and fix it. So far it looks like I'm going to 1)chkdsk /f 2)Sector by sector copy with Ghost/SavePart. Thanks for the help, I'll post back with how it went later on.

 

[Ice Czar]

well here we come on the boundary of repair and salvage
your filesystem architecture is damaged, and it maybe repairable (there are considerable features for this built in to NTFS), and its possible to repair past that as well if it doesnt fullty recover (so you have access and functionality)

but as far as the data goes, its more than likely fine (maybe some local corruption here and there individual files) and could be salvaged with a direct scan

but the long term concern would be what caused the corruption in the first place (and the HDD itself is pretty far down the list of culprits)

what was the full STOP code? (the following 4 0x00ect codes)

 

[tyjohnson]

0x001902FA, 0xF89B5700, 0xF89B5400, and 0xF81B2BEF.

I'm fairly sure that my PSU is to blame for the falure. The day the drive failed to boot I was looking at the voltages and all the rails exceded the 10%+/- that is usually exceptable. The PSU is now gone though, I replaced it with the True 430 I listed above at the same time as the drive.

I found a program that allows me to browse a NTFS partion from DOS and even view/save the files to a floppy or FAT partition. All the data is still there from what I see, I'm just not sure how to go about recovering it, would Ghost be the best way or is there a better way?