ST3000DM001: Spins, no terminal access (S) Sata reset lastly

[danielholm]

Hi all,

As I can see there are many of us with a faulty ST3000DM001 drive. Mine seems to be in busy state since it spins up (with some clicking at first) and then just stays that way (like an old ST2000 I fixed a few months ago, which was stuck in BSY state).

Now, I don't get access to the terminal. I can see the output, however and the log is shown below. I've tried to shorted the 1+3 pin, without any luck. Seen here:
viewtopic.php?f=1&t=25981 (original post)

Many others with this drive model gets a LOT of output from boot, but I don't; I just get this:

Code:

!�닁0x40M
Spin Up
Trans.

Spin Up
SpinOK
TCC:0024

(P) SATA Reset

(H) SATA Reset

(S) SATA Reset

So that's why I'm starting a seperate thread.
That last "(S) SATA Reset" is outputted around five minutes after the "(H) SATA Reset". Also the "(S) SATA Reset" continues to be printed continuously - three more times while posting this.

The drive is somewhat regonised by my Ubuntu Linux system, but does not give any info about it (in disk utility, but in terminal it presents a little - still unusable, though).

Code:

usb-storage 2-1.4.3:1.0: USB Mass Storage device detected
[333849.570295] scsi host21: usb-storage 2-1.4.3:1.0
[333850.567793] scsi 21:0:0:0: Direct-Access     ST3000DM 001-1CH166            PQ: 0 ANSI: 5
[333850.568163] sd 21:0:0:0: Attached scsi generic sg3 type 0
[333850.568939] sd 21:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
[333850.569400] sd 21:0:0:0: [sdc] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)
[333850.570402] sd 21:0:0:0: [sdc] Write Protect is off
[333850.570423] sd 21:0:0:0: [sdc] Mode Sense: 28 00 00 00
[333850.571514] sd 21:0:0:0: [sdc] No Caching mode page found
[333850.571520] sd 21:0:0:0: [sdc] Assuming drive cache: write through
[333850.572559] sd 21:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
[333881.077480] usb 2-1.4.3: reset high-speed USB device number 49 using ehci-pci
[333912.111940] usb 2-1.4.3: reset high-speed USB device number 49 using ehci-pci
[333922.276763] usb 2-1.4.3: reset high-speed USB device number 49 using ehci-pci
[333927.343119] usb 2-1.4.3: USB disconnect, device number 49
[333927.343318] sd 21:0:0:0: Device offlined - not ready after error recovery
[333927.345619] sd 21:0:0:0: [sdc] FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[333927.345624] sd 21:0:0:0: [sdc] CDB:
[333927.345627] Read(16): 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00
[333927.345639] blk_update_request: I/O error, dev sdc, sector 0
[333927.345652] Buffer I/O error on dev sdc, logical block 0, async page read
[333927.345705] ldm_validate_partition_table(): Disk read failed.
[333927.345741] Dev sdc: unable to read RDB block 0
[333927.345794]  sdc: unable to read partition table
[333927.346039] sd 21:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[333927.346052] sd 21:0:0:0: [sdc] Sense not available.
[333927.346101] sd 21:0:0:0: [sdc] Attached SCSI disk
[334017.916333] usb 2-1.4.3: new high-speed USB device number 50 using ehci-pci
[334018.010146] usb 2-1.4.3: New USB device found, idVendor=152d, idProduct=2338
[334018.010159] usb 2-1.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[334018.010162] usb 2-1.4.3: Product: USB to ATA/ATAPI bridge
[334018.010164] usb 2-1.4.3: Manufacturer: JMicron
[334018.010166] usb 2-1.4.3: SerialNumber: 000000000000
[334018.011209] usb-storage 2-1.4.3:1.0: USB Mass Storage device detected
[334018.011484] scsi host22: usb-storage 2-1.4.3:1.0
[334040.098148] usb 2-1.4.3: reset high-speed USB device number 50 using ehci-pci
[334854.921705] usb 2-1.4.3: USB disconnect, device number 50


Any ideas? I've tried pressing Ctrl+Z during the whole process, and while shortening the pins; shortening the pins from boot, during boot, after boot. Nothing.
Also I might have some connection issue since I get some: "������������" while Pressing Ctrl+Z to many times (also shown in the first line of the disk output). Using pl2303 usb serial at baud 38400.

Thanks in advance,
Daniel

[mr_spokk]

Hi, if the data is importent...stop messing with it.
I can see the drive sometimes read the correct size: 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB)

At this stage the cost should not be too high.

Regards/
Bosse

[danielholm]

The data is not important. Screw it, I just want to get it working.

[mr_spokk]

You don't want that drive to be working again...trust me
Found this report somewhere, it speaks for it self:

Attachments

[danielholm]

But I really do want it to work again, unfortunately...

Why does Seagate create these incredibly bad and unreliable drives? This is my third one, and they refuse to acknowledge when I speak to them on the phone.

[jermy]

isn't it cheaper to buy 1 from another manufacturer (toshiba for example) instead of 3 (and counting) from seagate

[danielholm]

isn't it cheaper to buy 1 from another manufacturer (toshiba for example) instead of 3 (and counting) seagate's

I wasn't making myself clear: this is my first 3TB drive that I've had issues with, but I've had problems with two Seagate drives in the past. But yes, it is indeed the end of getting Seagate drives.

[pepe]

the 9YNxxx series was the one affected with the high failure rates AFAIK.

[LarrySabo]

Reliability of the ST3000DM001 was bad from the get-go and has gotten worse each year. The failure rate, from BackBlaze's reliability report for 2015, was 28%!

[pepe]

ST3000DM001 means nothing. P/N does.

pepe

[LarrySabo]

Okay, thanks for the tip pepe.

[pcguru006]

the 9YNxxx series was the one affected with the high failure rates AFAIK.