I had two of these fail simultaneously (both members of a RAID 1 array) They both became unrecognizable by the RAID controller and the BIOS. I have a few good drives of the same model. On a good drive, if you place a card between the voicecoil/head connectors and the PCB you get the following errors:
Boot 0x40M
Spin Up
FAIL Servo Op=0100 Resp=0003
0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000
ResponseFrame 1F40 0000 0000 7FC0 0008 0000 0000 0000 FBE7 0000 0000 0000 0000 0000 0000 0000 722F 31A5 0
FAIL Servo Op=0100 Resp=0003
0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000
ResponseFrame 2580 0000 0000 7FC0 0008 0000 0000 0000 FBE7 0000 0000 0000 0000 0000 0000 0000 722F 31A5 0
If you remove the card and allow the PCB to connect to the head/voicecoil connections I see this:
Boot 0x40M
Spin Up
Trans.
Spin Up
SpinOK
TCC:001E
(P) SATA Reset
In neither case does my CTRL-Z give me a prompt, but I think that is because my 3.3V USB serial adapter which I modified using the schematic here:
http://www.mobileread.com/forums/showth ... ?p=1897643is not sending the right voltage on TX pin, so the drive never sees the CTRL-Z.
I have been going on the assumption that these drives have the firmware BSY bug, because the odds of simultaneous disk failure are so remote. These drives did not get bumped or jarred in any way, so mechanical failure would have had to happen for other reasons. Two failures at the exact same time is something I have not come across before, but I have seen abysmal failure rates on some Seagate 1TB drives over the last 4 years or so. As soon as I work out the TX problem I'll have good and bad drives to work with. I hope it turns out to be a simple firmware issue.