Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
October 8th, 2010, 20:42
I have a Seagate ST31000340AS 1TB drive that I am trying to recover some data off of. Specs are as follows
Seagate Barracuda 7200.11 1000 gbytes
S/N 5QJ062LP
ST31000340AS (B)
P/N 9BX158
Firmware SD35
Date Code 08292
Site Code WUXISG
PCB# 100468979
Sata
Drive is recognized in bios.
Drive is recognized in windows loads driver and can be see in device manager. If you try to access windows explorer, disk management, or get volume info in device manager the operations freeze until the drive is removed. (plugged in via sata to usb)
Drive spins properly, no clicking etc.
I have visually inspected the pcb and it does not to appear to have any burnt areas on the board.
I am trying to determine which method I would like to go about fixing the drive. Replacing the pcb (and probably moving the eeprom) or to mess with the firmware. Just having to remove one of the TVS diodes would be nice but does not seem like this would be the issue. Ant input would be greatly appreciated.
October 8th, 2010, 23:00
MHDD is ur friend. Check the drive with it. See if it gets ready. Try surface scan. Try bit copying the drive onto a good working drive and working with the clone. If drive is stuck at BUSY in mhdd then -
http://www.msfn.org/board/topic/138316- ... h-sd3biso/Do all above mentioned at ur won risk. Be aware that u can kill all ur data in an instant.
October 10th, 2010, 5:53
You say that the drive is recognized in BIOS, but does BIOS report its correct capacity?
Does Windows Disk Management report the correct capacity?
October 10th, 2010, 5:57

THE DRIVE IS RECOGNISED both in BIOS AND Windows AND doesn't click in any case (at least what the OP said) , the problem is "somewhere else" (I have an idea or two but should analyze the drive to confirm).
October 17th, 2010, 20:15
It was the firmware, ordered my ca 42 cable and reloaded the firmware and all is well now.
October 17th, 2010, 23:44
JTech wrote:It was the firmware, ordered my ca 42 cable and reloaded the firmware and all is well now.
Congratulations. :-)
Powered by phpBB © phpBB Group.