Hello,

I have a recently broken Seagate Barracuda 7200.12, possibly affected by the firmware bug. Model and firmware:

Seagate Barracuda 7200.12 750 GB
ST3750528AS
FW: CC38

The stuff on it is not really worth the charge of a data recovery lab so I want to try the DIY approach (PCB change etc.). But first I need your help with the diagnosis.

Here’s the problem: when I boot my computer the HDD is not listed by the BIOS during POST. Instead I get a message “AHCI Init” for up to 1 minute (usually this takes less than a second). Two other drives are recognized and listed correctly. I tried different cables, changed SATA ports and used other HDDs. Everything is working fine except when I use the Seagate Barracuda 7200.12.
After a while I get to the bootloader (GRUB) and I’m able to boot my OS which is on another drive. Of course the Barracuda is NOT found by the OS (I’ve tried different OS’s including Win7 and Linux Live systems).
Next, I have put the Barracuda in an external HDD case. The Barracuda definitely spins up, no clicking or strange noise. Win7 detects that a USB device has been connected but the HDD is listed as “Unknown Device”.
The Linux kernel will also recognize that a USB device has been connected and gives me the following message (output of dmesg):


The HDD never dropped. It sits in a desktop case along with other drives which are running fine so we can rule out external damages (voltage peaks etc.).

I would like to know if the 7200.12 also suffers from the 7200.11 firmware bug. Since the motor seems to be fine, a PCB swap might do the trick. What do you guys think?

Get a terminal log from the drive's serial diagnostic port. Don't write anything to it, though.

_________________
A backup a day keeps DR away.

They say here that only some 7200.12 can be affected by the 7200.11 firmware bug, but why not all of them?

http://www.hdd-parts.com/seonelithseb.html

I may be wrong, but 7200.12 with large pcb like 7200.11 can, and 7200.12 with small pcb can not?

Yo got vvery probably FW problems, Maybe bad heads or media damage too.

Firs you need a godd diagnostic. you need serial conection to get access to terminal and see HDD log.

wittch tools and skilss you have? if you have not and data is important better contact with a pro.

A serial to TTL converter is on its way. I hope I it arrives in time and I can assemble it on Sunday. I'll get back to you when I have more information.

Report is when you hace it, people yere can help you