Yet another brokcn ST3000DM001

[koehlma]

Hi there,

I am new to hard drive recovery and stumbled across this forum searching for a solution for my Seagate ST3000DM001. It is not recognized by BIOS anymore and the Linux kernel gives me the following error messages when plugging it in:

Code:

[  136.461770] ata10: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
[  136.461775] ata10: irq_stat 0x80400040, connection status changed
[  136.461779] ata10: SError: { PHYRdyChg CommWake DevExch }
[  136.461785] ata10: hard resetting link
[  146.453427] ata10: softreset failed (1st FIS failed)
[  146.453432] ata10: hard resetting link
[  149.311826] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  149.342248] ata10.00: ATA-8: ST3000DM001-1E6166, CC45, max UDMA/133
[  149.342253] ata10.00: 5860533168 sectors, multi 0: LBA48
[  149.343091] ata10.00: configured for UDMA/133
[  149.343285] ata10: EH complete
[  149.343373] scsi 9:0:0:0: Direct-Access     ATA      ST3000DM001-1E61 CC45 PQ: 0 ANSI: 5
[  149.343694] sd 9:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[  149.343699] sd 9:0:0:0: [sdb] 4096-byte physical blocks
[  149.343894] sd 9:0:0:0: [sdb] Write Protect is off
[  149.343900] sd 9:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[  149.343985] sd 9:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  149.353983] sdb: unknown partition table
[  149.354454] sd 9:0:0:0: [sdb] Attached SCSI disk
[  157.380625] ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[  157.380632] ata10.00: failed command: SMART
[  157.380638] ata10.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 12 pio 512 in
                         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[  157.380641] ata10.00: status: { DRDY }
[  157.380645] ata10: hard resetting link
[  167.374910] ata10: softreset failed (1st FIS failed)
[  167.374916] ata10: hard resetting link


Because it spins up and sounds normally I think there is a problem with the PCB. After the initial spin up I can not hear the heads move anymore. I managed to build an USB to Serial converter with TTL level shifter yesterday and the terminal gives me the following output (disk is not attached to a computer):

Code:

Boot 0x40M
  Spin Up
  Trans.

  Spin Up
SpinOK

(P) SATA Reset


If the disk is attached to a computer this is followed by:

Code:

(S) SATA Reset


If I press Strg + z nothing happens although according to my oscilloscope the data is transmitted correctly.

Drive information:

• SN: W1F2W8P8
• PN: 1E6166-570
• FW: CC45
• Date: 13407
• Site: WU

The data is not too important but it would be nice to get it back. Any ideas what could be wrong with the drive?

Thank you in advance.

Greetings
Maximilian

[labtech]

Likely bad sectors, high chance of firmware issue, or even mechanical problem.
Noticed anything out of the ordinary before it went kaput?

P.S. Don't try things off the internet without understanding clearly what is going on. Educate yourself first before issuing commands in the terminal. A lot of people screw up badly.

[LarrySabo]

Given their history, I don't know why anyone would want to resurrect a failing DM drive, especially as there is no data recovery required. Just bin it and vow not to buy another Seagate, is my advice.

[guru]

Drive ID's ok. However looks like the drive has a timeout on a SMART command. Check the error handler.

[Amarbir[CDR-Labs]]

Given their history, I don't know why anyone would want to resurrect a failing DM drive, especially as there is no data recovery required. Just bin it and vow not to buy another Seagate, is my advice.

Mr Larry ,
How about those slim st1000dm00X [ X i do not remember might be its 1 ] drives they are bad also .IMHO they are very fast then any other drive i have seen .I have a few 2TB also .None of them have failed after repeat use in my own data recovery lab work .Also not have sea gates are coming for recovery to lab in chandigarh my hometown .Lots of external samsung drive that are a joy to work with

[koehlma]

Good news, I managed to rescue all my data (except a few blocks) by reading many threads in this forum and experimenting a lot. Thank you very much for all the information here.

Given their history, I don't know why anyone would want to resurrect a failing DM drive, especially as there is no data recovery required. Just bin it and vow not to buy another Seagate, is my advice.

It was an interesting experience, I have learned a lot and finally got all my data back, so was totally worth it. However I will never buy a Seagate device again − this was clearly a software related issue and it was a way too hard to find some good information about this particular devices. Especially if you have no specific data recovery software or hardware.

P.S. Don't try things off the internet without understanding clearly what is going on. Educate yourself first before issuing commands in the terminal.

This was a really good advice, however at the time of your reply I had already messed up my device by issuing some commands (I am a little bit risky sometimes). In retrospect I think clearing all the SMART data should have been enough, but I also regenerated the translator with the wrong command which does not take the NRG list into account. So I ended up with the partial access error. I had a backup (terminal dump) of the old NRG list but I was unable to find out how to add entries manually. I finally cleared the NRG list with i40,1,22 and regenerated the translator again. After this I was able to access the full device but I got some bad sector errors because all the previous mappings had gone (if I understand this correctly). But it worked and all my "nice to have them back"-files are not damaged.

Initially I was unable to send commands to the drive because the voltage was too low. Although the device sends using a 2V logic level voltage it does not recognize any input using this voltage. I simply used the direct 5V output of the USB to Serial converter and it worked.

[labtech]

P.S. Don't try things off the internet without understanding clearly what is going on. Educate yourself first before issuing commands in the terminal.

This was a really good advice, however at the time of your reply I had already messed up my device by issuing some commands (I am a little bit risky sometimes)...

Nice of you to provide meaningful feedback. Hopefully, at least one person will read this before potentially screwing up. You got lucky.

[thatdellguy]

However I will never buy a Seagate device again

Probably the best advice anyone can learn from this forum.