Ok, so I got two drives of this model (ST2000DL003-9VT166) that both died at the same time after a power shortage of ReadyNAS 1100 I got. Neither of them was found in a regular computers BIOS, but they where identified by the NAS unit, altough they failed to initialize - Error messages said that the drives were BUSY. After some paniciing and fury I found this thread, ordered a CA-42 (copy) cable. Got it the other day, took it apart and today I finally got acces using serial connection. Drive 1: Success. Before I got the cable I shortned the two pins (found in image in post #9), hoping that would work solely - it did not. So when I go the cable I connected it and finally got some output from the boot process: Rst 0x40M MC Internal LPC Process(P) SATA Reset User Data Base 00991680 MCMainPOR: Start: Check MCMT Version: Current MCMainPOR: Non-Init Case MC Seg Disc and Cache Nodes: 4011A624 40118734 Seg Write Preamble VBM start: 000010A7 end: 000010CE Footer - start: 000010D0 end: 000010F7 Seg Read Preamble VBM - start: 000010F9 end: 00001120 Footer - start: 00001122 end: 00001149Reconstruction: MCMT Reconstruction Start Max number of MC segments 22E0 Nonvolatile MCMT sequence number 00000002 [RSRS] 0000Reconstruction: Completed 0: HeadPtr was unwritten [MCMTWS] MCMainPOR: MCTBufferPtr->Header.MCStateFlagsDisc = 00000001 MCMainPOR: MCTBufferPtr->Header.MCTStateFlags = 0000002A MCMainPOR: MCStateFlags = 00000001 MCMainPOR: Feature Enabled...There the output ended. Pressing Ctrl+Z did not do anything. So I started to short the pins, and I got: InitiateMarkPendingReallocateRequest for disc_lba: 08EFAE2AAfter that the drive sounded a bit more than usual and after each periodic sound it added a "!" at the end of "08EFAE2A". I tried Ctrl+Z again and finally got access! So I ran the commands: F3 2>Z(took around 14 secs to spin down)F3 2>UCtrl+ZF3T>i4,1,22F3 2>/1F3 1>N1Then powered down.Connected the drive to a computer and it was found in BIOS. Booted Ubuntu, formated it, ran some SMART tests. It's now connected to my NAS again and is initializing. Disk 2: Bad.. Booting: (P) SATA ResetUser Data Base 00991CC0MCMainPOR: Start:Check MCMT Version: CurrentMCMainPOR: Non-Init CaseMC Seg Disc and Cache Nodes: 4011A624 40118734Seg Write Preamble VBM start: 000010A7 end: 000010CEFooter - start: 000010D0 end: 000010F7Seg Read Preamble VBM - start: 000010F9 end: 00001120Footer - start: 00001122 end: 00001149Reconstruction: MCMT Reconstruction StartMax number of MC segments 22E0Nonvolatile MCMT sequence number 000000A6[RSRS] 0061Reconstruction: Completed 0: HeadPtr was unwritten[MCMTWS]MCMainPOR: MCTBufferPtr->Header.MCStateFlagsDisc = 00000041MCMainPOR: MCTBufferPtr->Header.MCTStateFlags = 00000022MCMainPOR: MCStateFlags = 00000041MCMainPOR: Feature Enabled...Rst 0x40MMC Internal LPC ProcessLED:000000BD FAddr:000058E4Ctrl+Z not working. Power down, power up, shortned the pins the whole time. The drive gave a loud beep. Nothing else changed. After a few retries I got access to the terminal by using the window (of a few seconds) between "Feature enabled..." and "LED:000000BD FAddr:000058E" Ran the same commands as for disk 1. Powered down, connected it to a PC - No change: it still was not found my BIOS. Plugging it back into serial connection, running the commands a few more times, restarting the drive and found that the "LED:000000BD FAddr:000058E" issue persisted. Trying the "paper over header, under PCB". Gave nothing. At all. So I thought (I know....) "The hell with it!" (I know... I know.." and then I ran: >m0,2,2,,,,,22User Partition Format Successful - Elapsed Time 0 mins 00 secs Zone re-format was skipped.No change when power cycling. Ran the first commands that worked for the dirst disk anothe time, no change, so I started to shortned the pins even longer after restart of the drive. No I started to get these new messages: FAIL Op=0900 Resp=0005FAIL Op=0600 Resp=0005No HOST FIS-ReadyStatusFlags 0002A1A4huh? Pressing Ctrl+Z again - still got terminal access. But now when I ran the previous commands, including m0(...) and so on, I started to get: Init SMART FailThen I get kicked out of the terminal and the error message is followed by the old: Rst 0x40M MC Internal LPC ProcessLED:000000BD FAddr:000058E4Using the window to get into terminal again I can still spin up and down, but N1 or m0 gives me "Init SMART fail" and I get kicked out. And that's where I am at right now.