Search

Dear Linux-Wizards,

I have some USB flash drive that outputs the following errors, when i plug it in:

VGscsi 6:0:0:0: Direct-Access SMI01 USB DISK01 1100 PQ: 0 ANSI: 6 VGsd 6:0:0:0: [sdc] 491520000 512-byte logical blocks: (252 GB/234 GiB) VGsd 6:0:0:0: [sdc] Write Protect is off VGsd 6:0:0:0: [sdc] Mode Sense: 43 00 00 00 VGsd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA VGsd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s VGsd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] VGsd 6:0:0:0: [sdc] tag#0 Add. Sense: Medium not present VGsd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 VGI/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 VGBuffer I/O error on dev sdc, logical block 0, async page read VGsd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s VGsd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] VGsd 6:0:0:0: [sdc] tag#0 Add. Sense: Medium not present VGsd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 VGI/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 VGBuffer I/O error on dev sdc, logical block 0, async page read VGldm_validate_partition_table(): Disk read failed. VGsd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s VGsd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] VGsd 6:0:0:0: [sdc] tag#0 Add. Sense: Medium not present VGsd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 VGI/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 VGBuffer I/O error on dev sdc, logical block 0, async page read VG sdc: unable to read partition table VGsd 6:0:0:0: [sdc] Attached SCSI removable disk VGsd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s VGsd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] VGsd 6:0:0:0: [sdc] tag#0 Add. Sense: Medium not present VGsd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 4b ff 80 00 00 08 00 VGI/O error, dev sdc, sector 491519872 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 VGsd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s VGsd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] VGsd 6:0:0:0: [sdc] tag#0 Add. Sense: Medium not present VGsd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 1d 4b ff 80 00 00 08 00 VGI/O error, dev sdc, sector 491519872 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 VGBuffer I/O error on dev sdc, logical block 61439984, async page read

lsblk output looks okayish, disk size is reported correctly. sdc 8:32 1 234,4G 0 disk

When i first noticed, i hoped maybe only the first Sectors are broken, but now i'm trying with ddrescue and ddrescue -d and see the similar messages:

I/O error, dev sdc, sector 237172352 op 0x0:(READ) flags 0x800 phys_seg 15 prio class 2 sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current] sd 6:0:0:0: [sdc] tag#0 Add. Sense: Medium not present sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 0e 22 f7 00 00 00 80 00

It's a USB-3 flash drive, so i also tried an USB-2 port hoping that maybe its some connection thing, but it did not help, I see the same error messages.

Normally USB flash drives warm a bit when reading/writing data, this one ist still cold after 25 minutes of ddrecue

Is there anything else i can do?

Backstory is: I was helping someone with their Windows PC and unplugged the stick without ejecting it, then Windows complained and i pressed to "scan and repair drive" which took a while. At 80% a error message appeared similar to: "insert medium into drive" When clicking OK the message reappeared after one or two seconds. It only stopped after unplugging the flash drive.

The user already said something about folders appearing at wrong locations at the drive, so i hope i did not kill the drive but it was already dying. But still feeling bad about this, so i want to try everything and even reach out to you :-)

Solution

Yeah, the drive is dying. As suggested by @[email protected], and @[email protected], I ran a S.M.A.R.T. test (the short option), and received the following report: === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. Failed Attributes: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 001 001 051 Pre-fail Always FAILING_NOW 1473

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: The primary GPT table is corrupt, but the backup appears OK, so that will be used. 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: ... [ 252.090206] critical target error, dev sde, sector 8 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [ 252.090210] Buffer I/O error on dev sde, logical block 1, async page read [ 252.090292] sd 6:0:0:0: [sde] Attached SCSI disk [ 296.776697] sd 6:0:0:0: [sde] tag#13 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN [ 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 [ 296.796696] scsi host6: uas_eh_device_reset_handler start [ 296.920474] usb 4-6: reset SuperSpeed USB device number 3 using xhci_hcd [ 296.940278] scsi host6: uas_eh_device_reset_handler success [ 300.090562] sd 6:0:0:0: [sde] Unaligned partial completion (resid=12280, sector_sz=512) [ 300.090567] sd 6:0:0:0: [sde] tag#16 CDB: Read(10) 28 00 00 00 00 08 00 00 18 00 [ 300.090570] sd 6:0:0:0: [sde] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s [ 300.090572] sd 6:0:0:0: [sde] tag#16 Sense Key : Hardware Error [current] [ 300.090573] sd 6:0:0:0: [sde] tag#16 Add. Sense: Internal target failure [ 300.090574] sd 6:0:0:0: [sde] tag#16 CDB: Read(10) 28 00 00 00 00 08 00 00 18 00 [ 300.090575] critical target error, dev sde, sector 8 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2 [ 300.090640] sd 6:0:0:0: [sde] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s [ 300.090642] sd 6:0:0:0: [sde] tag#14 Sense Key : Hardware Error [current] [ 300.090643] sd 6:0:0:0: [sde] tag#14 Add. Sense: Internal target failure [ 300.090644] sd 6:0:0:0: [sde] tag#14 CDB: Read(10) 28 00 00 00 00 20 00 00 08 00 [ 300.090645] critical target error, dev sde, sector 32 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [ 326.010763] usb 4-6: USB disconnect, device number 3 [ 326.010898] sd 6:0:0:0: [sde] tag#18 uas_zap_pending 0 uas-tag 1 inflight: CMD [ 326.010901] sd 6:0:0:0: [sde] tag#18 CDB: Read(10) 28 00 00 00 00 20 00 00 08 00 [ 326.010903] sd 6:0:0:0: [sde] tag#17 uas_zap_pending 0 uas-tag 2 inflight: CMD [ 326.010905] sd 6:0:0:0: [sde] tag#17 CDB: Read(10) 28 00 00 00 00 08 00 00 08 00 [ 326.010919] sd 6:0:0:0: [sde] tag#18 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=25s [ 326.010921] sd 6:0:0:0: [sde] tag#18 CDB: Read(10) 28 00 00 00 00 20 00 00 08 00 [ 326.010922] I/O error, dev sde, sector 32 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [ 326.010925] Buffer I/O error on dev sde, logical block 4, async page read [ 326.010931] sd 6:0:0:0: [sde] tag#17 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK cmd_age=25s [ 326.010942] sd 6:0:0:0: [sde] tag#17 CDB: Read(10) 28 00 00 00 00 08 00 00 08 00 [ 326.010943] I/O error, dev sde, sector 8 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 [ 326.010945] Buffer I/O error on dev sde, logical block 1, async page read [ 326.050781] sd 6:0:0:0: [sde] Synchronizing SCSI cache [ 326.270781] sd 6:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK ... Is this drive dead? Is something just corrupt? If there is data on it, would it be straightforward to pull it off?