[Solved] Is this hard drive failing?

Solution

Yeah, the drive is dying. As suggested by @nous, and @Granixo, I ran a S.M.A.R.T. test (the , and received the following report:

<pre style="background-color:#ffffff;">
<span style="color:#323232;">=== START OF READ SMART DATA SECTION ===
</span><span style="color:#323232;">SMART overall-health self-assessment test result: FAILED!
</span><span style="color:#323232;">Drive failure expected in less than 24 hours. SAVE ALL DATA.
</span><span style="color:#323232;">Failed Attributes:
</span><span style="color:#323232;">ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
</span><span style="color:#323232;">  1 Raw_Read_Error_Rate     0x002f   001   001   051    Pre-fail  Always   FAILING_NOW 1473
</span>

Original Post

I have a pulled hard drive from an old Western Digital external hard drive. I connected it to my desktop to see what was on it, and, after running fdisk -l (which took a weirdly long time to run while also keeping one core at 100%), it gave the error message:

<pre style="background-color:#ffffff;">
<span style="color:#323232;">The primary GPT table is corrupt, but the backup appears OK, so that will be used.
</span>

However, trying to mount it resulted in another error saying that the drive doesn’t exist. Looking at dmesg reveals a ton of other errors like the following:

<pre style="background-color:#ffffff;">
<span style="color:#323232;">...
</span><span style="color:#323232;">[  252.090206] critical target error, dev sde, sector 8 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
</span><span style="color:#323232;">[  252.090210] Buffer I/O error on dev sde, logical block 1, async page read
</span><span style="color:#323232;">[  252.090292] sd 6:0:0:0: [sde] Attached SCSI disk
</span><span style="color:#323232;">[  296.776697] sd 6:0:0:0: [sde] tag#13 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
</span><span style="color:#323232;">[  296.776712] sd 6:0:0:0: [sde] tag#13 CDB: ATA command pass through(12)/Blank a1 08 2e 00 01 00 00 00 00 ec 00 00
</span><span style="color:#323232;">[  296.796696] scsi host6: uas_eh_device_reset_handler start
</span><span style="color:#323232;">[  296.920474] usb 4-6: reset SuperSpeed USB device number 3 using xhci_hcd
</span><span style="color:#323232;">[  296.940278] scsi host6: uas_eh_device_reset_handler success
</span><span style="color:#323232;">[  300.090562] sd 6:0:0:0: [sde] Unaligned partial completion (resid=12280, sector_sz=512)
</span><span style="color:#323232;">[  300.090567] sd 6:0:0:0: [sde] tag#16 CDB: Read(10) 28 00 00 00 00 08 00 00 18 00
</span><span style="color:#323232;">[  300.090570] sd 6:0:0:0: [sde] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s
</span><span style="color:#323232;">[  300.090572] sd 6:0:0:0: [sde] tag#16 Sense Key : Hardware Error [current] 
</span><span style="color:#323232;">[  300.090573] sd 6:0:0:0: [sde] tag#16 Add. Sense: Internal target failure
</span><span style="color:#323232;">[  300.090574] sd 6:0:0:0: [sde] tag#16 CDB: Read(10) 28 00 00 00 00 08 00 00 18 00
</span><span style="color:#323232;">[  300.090575] critical target error, dev sde, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2
</span><span style="color:#323232;">[  300.090640] sd 6:0:0:0: [sde] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s
</span><span style="color:#323232;">[  300.090642] sd 6:0:0:0: [sde] tag#14 Sense Key : Hardware Error [current] 
</span><span style="color:#323232;">[  300.090643] sd 6:0:0:0: [sde] tag#14 Add. Sense: Internal target failure
</span><span style="color:#323232;">[  300.090644] sd 6:0:0:0: [sde] tag#14 CDB: Read(10) 28 00 00 00 00 20 00 00 08 00
</span><span style="color:#323232;">[  300.090645] critical target error, dev sde, sector 32 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
</span><span style="color:#323232;">[  326.010763] usb 4-6: USB disconnect, device number 3
</span><span style="color:#323232;">[  326.010898] sd 6:0:0:0: [sde] tag#18 uas_zap_pending 0 uas-tag 1 inflight: CMD 
</span><span style="color:#323232;">[  326.010901] sd 6:0:0:0: [sde] tag#18 CDB: Read(10) 28 00 00 00 00 20 00 00 08 00
</span><span style="color:#323232;">[  326.010903] sd 6:0:0:0: [sde] tag#17 uas_zap_pending 0 uas-tag 2 inflight: CMD 
</span><span style="color:#323232;">[  326.010905] sd 6:0:0:0: [sde] tag#17 CDB: Read(10) 28 00 00 00 00 08 00 00 08 00
</span><span style="color:#323232;">[  326.010919] sd 6:0:0:0: [sde] tag#18 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=25s
</span><span style="color:#323232;">[  326.010921] sd 6:0:0:0: [sde] tag#18 CDB: Read(10) 28 00 00 00 00 20 00 00 08 00
</span><span style="color:#323232;">[  326.010922] I/O error, dev sde, sector 32 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
</span><span style="color:#323232;">[  326.010925] Buffer I/O error on dev sde, logical block 4, async page read
</span><span style="color:#323232;">[  326.010931] sd 6:0:0:0: [sde] tag#17 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=25s
</span><span style="color:#323232;">[  326.010942] sd 6:0:0:0: [sde] tag#17 CDB: Read(10) 28 00 00 00 00 08 00 00 08 00
</span><span style="color:#323232;">[  326.010943] I/O error, dev sde, sector 8 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
</span><span style="color:#323232;">[  326.010945] Buffer I/O error on dev sde, logical block 1, async page read
</span><span style="color:#323232;">[  326.050781] sd 6:0:0:0: [sde] Synchronizing SCSI cache
</span><span style="color:#323232;">[  326.270781] sd 6:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
</span><span style="color:#323232;">...
</span>

Is this drive dead? Is something just corrupt? If there is data on it, would it be straightforward to pull it off?

gian,

I don’t think the drive is totally dead, it is somehow reactive to commands, but I would not trust to use it.

You should be able to pull of at least some of the data, but there is no guarantee.

I would copy all what I can and then try to run a low level format and mark the bad blocks, then run the S.M.A.R.T. test to see if something change, but I would do it just out of curiosity.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • wartaberita
  • uselessserver093
  • Food
  • [email protected]
  • aaaaaaacccccccce
  • test
  • CafeMeta
  • testmag
  • MUD
  • RhythmGameZone
  • RSS
  • dabs
  • Socialism
  • TheResearchGuardian
  • SuperSentai
  • feritale
  • oklahoma
  • Testmaggi
  • KbinCafe
  • Ask_kbincafe
  • KamenRider
  • All magazines