Help diagnosing possible fault origins from noises (mp3)

[inflex]

Hi all, client bought in a Seagate external 2TB USB3 drive, it has been dropped from what I can see (enclosure scuffed and slightly parted along one of the seams).

It's quite a noisy beast when it fires up - http://dxp.me/i/seagate-2TB-enclosure.mp3

Under linux I get this in the logs:

[1746841.013798] end_request: critical target error, dev sdd, sector 0
[1746841.014927] sd 107:0:0:0: [sdd] Unhandled sense code
[1746841.014938] sd 107:0:0:0: [sdd] Result: hostbyte=invalid driverbyte=DRIVER_SENSE
[1746841.014947] sd 107:0:0:0: [sdd] Sense Key : Medium Error [current]
[1746841.014957] sd 107:0:0:0: [sdd] Add. Sense: Unrecovered read error
[1746841.014968] sd 107:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 01 00 00 01 00
[1746841.014990] end_request: critical target error, dev sdd, sector 1
[1746841.016195] sd 107:0:0:0: [sdd] Unhandled sense code
[1746841.016205] sd 107:0:0:0: [sdd] Result: hostbyte=invalid driverbyte=DRIVER_SENSE
[1746841.016214] sd 107:0:0:0: [sdd] Sense Key : Medium Error [current]
[1746841.016225] sd 107:0:0:0: [sdd] Add. Sense: Unrecovered read error
[1746841.016237] sd 107:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 02 00 00 06 00
[1746841.016257] end_request: critical target error, dev sdd, sector 2
[1746841.017189] sd 107:0:0:0: [sdd] Unhandled sense code
[1746841.017195] sd 107:0:0:0: [sdd] Result: hostbyte=invalid driverbyte=DRIVER_SENSE
[1746841.017205] sd 107:0:0:0: [sdd] Sense Key : Medium Error [current]
[1746841.017215] sd 107:0:0:0: [sdd] Add. Sense: Unrecovered read error
[1746841.017225] sd 107:0:0:0: [sdd] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00

[dobrevjetser]

If it has been dropped and makes a lot of noise its never a good idea to power the drive. I would not be amazed when you open it up (in a clean environment) you'll see some nice rings on the platters.

[northwind]

I agree, this sound is often a result of severe media damage.