Seagate ST4000LM016 failure

Don't Lose Your Data Forever!

DIY data recovery has risks. You could lose your data forever! Don't want to risk it? Talk to a professional now.

jaijaikalima

New member
Hi,

Seagate Backup Plus:
Model: SRD00F1

HDD: 4000GB
SN: W800KC1Q
Board: PCB 100771588 Rev A

So, two weeks ago, after coming home i noticed the drive was turned off. which never happens.. I reconnected it and it works.
The day after, i had some freezing issues on linux while trying to connect to the attached drive. Didn't think much of it, i thought it was the operation system.
Now, after connecting the drive, it spins but i can hear a repeating 3 soft clicks, like it's trying to read the drive but fails. and nothing else happens.

Tried different usb ports, cable and another laptop. Same thing..
Also took it out of the case, connected with SATA-USB connector. No luck.

The drive is 6y old, pretty much everyday use. And it's pretty full, i think 16gb of free space was left.

I talked about this on linux mint forum: https://forums.linuxmint.com/viewtopic.php?f=50&t=373402

output of dmesg -w:
$ dmesg -w
[33166.607135] usb 2-1: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[33166.627733] usb 2-1: New USB device found, idVendor=0bc2, idProduct=ab28, bcdDevice= 1.00
[33166.627734] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[33166.627735] usb 2-1: Product: BUP BK
[33166.627736] usb 2-1: Manufacturer: Seagate
[33166.627737] usb 2-1: SerialNumber: NA7P8Y82
[33166.631473] scsi host3: uas
[33166.631918] scsi 3:0:0:0: Direct-Access Seagate BUP BK 0304 PQ: 0 ANSI: 6
[33166.632407] sd 3:0:0:0: Attached scsi generic sg3 type 0
[33166.632634] sd 3:0:0:0: [sdc] Spinning up disk...
[33167.655026] .................ready
[33184.039200] sd 3:0:0:0: [sdc] 7814037167 512-byte logical blocks: (4.00 TB/3.64 TiB)
[33184.039205] sd 3:0:0:0: [sdc] 2048-byte physical blocks
[33214.677022] sd 3:0:0:0: tag#8 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[33214.677030] sd 3:0:0:0: tag#8 CDB: Mode Sense(6) 1a 00 3f 00 04 00
[33214.697039] scsi host3: uas_eh_device_reset_handler start
[33219.781011] usb 2-1: Disable of device-initiated U1 failed.
[33224.900748] usb 2-1: Disable of device-initiated U2 failed.
[33230.276530] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[33235.652352] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[33235.860215] usb 2-1: device not accepting address 5, error -62
[33241.284072] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[33246.659896] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[33246.867788] usb 2-1: device not accepting address 5, error -62
[33252.291671] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[33257.667452] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[33257.875336] usb 2-1: device not accepting address 5, error -62
[33263.299225] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[33268.674992] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[33268.882838] usb 2-1: device not accepting address 5, error -62

I uploaded an audio file of what the drive sounds like.
Recorded with a Tascam recorder, very upclose, +15db.
https://e1.pcloud.link/publink/show?code=XZKdczZcSoEtvpjxi7TW3i8IWTnmJXD9R9k

Can someone listen and determine what could be wrong?
Is there anything else i can try for testing?
Would the next step be replacing the circuit board, or could it be the sound of a stuck head?

Thank you.
 

pclab

Moderator
Unfortunately that sounds as heads problem or even platter damage.
Heads are trying to find SA and can't do it.
If data is really important, take it to a lab to proper assesment.
Replacing PCB would not solve it....
 

jaijaikalima

New member
Can platter damage happen when the disk is just sitting there?
Sorry what SA stands for?

The only backup i have is a Virtual Volumes View.
It's a 15 year collection of hard to find materials.
Will take forever to find everything back. But not impossible for most things.
 

pclab

Moderator
Seagate drives have some problems with degradation. They tend to do it over time.
SA means Service Area (where firmware is written and where heads try to read)
 
Top