[Solved] Hard drive not detected in bios-disk spins and heads move

Hey guys,
I'm in a sticky situation. My parent's computer had a Seagate Barracuda 7200.11 750 GB hard drive and an Intel DG35EC mobo. The Northbridge on the motherboard fried, and now the hard drive can't be detected in the BIOS on our other computer. I replaced the mobo and the drive, and got it working again for them, but I really need to get data off of the drive.

When I plug it into the other computer and into the new motherboard, the drive spins and the heads move at startup, but then nothing happens. While the BIOS detects the drives, it hangs on the port where the old hard drive is plugged in, and then finishes booting normally. It doesn't make any weird noises, sounds the same as the day it was installed.

I've seen other posts about replacing the PCB on the drive, but I'd rather not go to that length if it is not necessary. Any help would be greatly appreciated.
Thank You.

Your drive may be a victim of the Seagate 7200.11 BSY bug. The bug affects Maxtors, too.

Here are repair procedures for Seagate 7200.11 drives:
http://sites.google.com/site/seagatefix/
http://www.msfn.org/board/index.php?showtopic=128807

Tutorial with photos:
http://www.overclock.net/hard-driv [...] -pics.html

Pinout of Nokia CA-42 cable's Pop-port connector (use pins 6,7,8):
http://pinouts.ru/CellularPhones-N [...] nout.shtml

See the following technical bulletin:

Urgent Field Update. Topic: Drive Hang after Power Cycle:
http://www.expreview.com/img/topic [...] Update.pdf

Seagate were at one time offering free data recovery services to those customers whose drives were affected by the bug. This may still be the case.

After you have repaired your drive, you can apply the following firmware update.

Firmware Updates for Seagate Products [207931]:
http://seagate.custkb.com/seagate/ [...] cId=207931

The procedure is data safe. The "partitions" referred to in the article are not in the user data area. They are part of the hidden System Area (SA) of the drive. The SA is where the firmware, bad-block list, SMART data, etc are stored.

Well, it turns out that it's a thermal problem with the controller board. It works for about 30 seconds, and then you can fry an egg on the board. Any suggestions on where I could find a working board?

Best answer selected by bigj231.