ST2000DM001 - Not recognized in bios - Can't access terminal

[Purblod]

Hi,

 

I have a problem similar to the ones in these posts;

 

http://www.msfn.org/board/topic/161029-seagate-barracuda-lp-green-is-not-recognized-in-bios-suddenly/

http://www.msfn.org/board/topic/150475-st2000dl003-seagate-barracuda-lp-green-2000gb-suddenly-ceases/

http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/page-167#entry997493

http://www.msfn.org/board/topic/142565-how-to-solve-error-1009-detsec-00006008-fix/

 

Here are some pics of the pcb;

 

http://imageshack.com/a/img850/7997/jjha.jpg

http://imageshack.com/a/img829/4638/3c94.jpg

http://imageshack.com/a/img850/7053/0jrb.jpg

 

What I have tried so far are;

1- Connected to the serial interface of the hdd. Bi-directional data transfer verified.

2- Issued the ctrl+z command but didn't seem to have any effect. Then tried issuing the command repeatedly during boot. For a brief moment, command prompt "F3 T>" appeared. Before I can type any other command, firmware responded "(P) SATA Reset" and the terminal became unresponsive again;

Boot 0x40M Spin Up Trans. Spin UpSpinOKASCII Diag modeF3 T>(P) SATA Reset 

3- I have tried isolating the motor pins and the head pins (seperately and at the same time) with a piece of plastic but got the response;

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 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ResponseFrame 1DC0 0000 0000 7FC0 0008 0000 0000 0000 FBE7 0000 0000 0000 00000000 0000 0000 A5C2 9F1F 906E D627 664A 656A B158 36BD 78B5 4551 0000 007F 00040000 FFF7 0004 0010 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 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ResponseFrame 25C0 0000 0000 7FC0 0008 0000 0000 0000 FBE7 0000 0000 0000 00000000 0000 0000 A5C2 9F1F 906E D627 664A 656A B158 36BD 78B5 4551 0000 007F 00040000 FFF7 0004 0000

4- I couldn't find which pins are the "read pins", the ones to short. But then I read that  isolating the head pins after accessing the command prompt. I tried that by lifting the pcb and breaking the connection to the head pins. I tried sending "/2" + enter but there was no echo to the characters I typed. Then the "FAIL Servo..." response again.

Boot 0x40M Spin Up Trans. Spin UpSpinOKASCII Diag modeF3 T> FAIL  Servo Op=000E Resp=000B 000E 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ResponseFrame 0000 0001 FFFF FF14 0004 FC30 E670 DDF5 0003 0000 0000 0000 00000000 1000 0000 A5C2 9A1F 906E D627 FFFF 1000 E18A 0000 0004 A209 7F43 214A 5855F271 6752 D3A6 005C

5- In 1 of 10 tries, the hdd responded to the repeating "ctrl+z" command as below. The last row repeats itself in every 30 seconds or so.

Boot 0x40M Spin Up Trans. Spin UpSpinOK(P) SATA Reset SIM Error 1009 LBA 0000000000097DB8 FD FCFFF3FF RW Error 00000080 SIM Error 1009 LBA 0000000000097DB8 FD FCFFF3FF RW Error 00000080 EDAC Value = 00000000FFFFF285 EDAC Value = 00000000FFFFF285 MCMainPOR: Start: User Data Base  009AB6C8 Check MCMT Version: CurrentMC026: Reconstruction: MCMT Reconstruction Start [RSRS] 0D79LED:000000BD FAddr:00006220LED:000000BD FAddr:00006220LED:000000BD FAddr:00006220LED:000000BD FAddr:00006220

I have been reading and trying things for 3 days now and I am not yet ready to give up but I am exhausted so I am asking for help. Thanks in advance.

 

[jaclaz]

Unless I am mistaken that disk (ST2000DM001) is a 7200.14.

 

What we have is some (limited) information about the 7200.11 (originally intended for a specific issue) and the later finding that the same procedure may work as a form of "general" reset when a disk (still 7200.11) bricks itself for other reasons.

Later experiments revealed that (with a needed added step of shorting the "read channel") the same "general" reset worked in *some* cases of 7200.11 ES that were bricked for *some* reason. 

Even later we had a few, incomplete , confused , unconfirmed (and possibly void of any validity) reports that the same procedure worked for the 7200.12 model.

 

Your 7200.14 may need a completely different procedure (IF such a procedure exists, i.e. IF it is fixable in a DIY way) and we don't even know in which state it is and what caused it.

 

You may want to try asking for assistance on hddguru:

http://forum.hddguru.com/

(though with 99.99% probabilities you will be told that you should not do it and go to a professional) or, with more possibilities to get a valid answer, here:

http://malthus.zapto.org/index.php

where some of the more friendly guys with some experience with hard disk usually hang around.

 

jaclaz