Hello,

I have a SanDisk USB Storage (Cruzer Blade) that is clearly faulty and seems completely inaccessible on a Raspberry Pi Zero, running Linux version 5.10.103+. Despite the content being very important to me, I would give up except for the fact that I have no problem accessing it on a Samsung Smart TV...

The device is detected when I run lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sde 8:64 1 14.3G 0 disk
└─sde1 8:65 1 14.3G 0 part


If I run udevadm, I get the device information fine

udevadm info --query=all --name=/dev/sde
P: /devices/platform/soc/20980000.usb/usb1/1-1/1-1:1.0/host4/target4:0:0/4:0:0:0/block/sde
N: sde
L: 0
S: disk/by-id/usb-SanDisk_Cruzer_Blade_XXX-0:0
S: disk/by-path/platform-20980000.usb-usb-0:1:1.0-scsi-0:0:0:0
E: DEVPATH=/devices/platform/soc/20980000.usb/usb1/1-1/1-1:1.0/host4/target4:0:0/4:0:0:0/block/sde
E: DEVNAME=/dev/sde
E: DEVTYPE=disk
E: MAJOR=8
E: MINOR=64
E: SUBSYSTEM=block
E: USEC_INITIALIZED=2088707039
E: ID_VENDOR=SanDisk
E: ID_VENDOR_ENC=SanDisk\x20
E: ID_VENDOR_ID=0781
E: ID_MODEL=Cruzer_Blade
E: ID_MODEL_ENC=Cruzer\x20Blade\x20\x20\x20\x20
E: ID_MODEL_ID=5567
E: ID_REVISION=1.00
E: ID_SERIAL=SanDisk_Cruzer_Blade_XXX-0:0
E: ID_SERIAL_SHORT=XXX
E: ID_TYPE=disk
E: ID_INSTANCE=0:0
E: ID_BUS=usb
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=usb-storage
E: ID_PATH=platform-20980000.usb-usb-0:1:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=platform-20980000_usb-usb-0_1_1_0-scsi-0_0_0_0
E: ID_PART_TABLE_UUID=0003ba58
E: ID_PART_TABLE_TYPE=dos
E: DEVLINKS=/dev/disk/by-id/usb-SanDisk_Cruzer_Blade_XXX-0:0 /dev/disk/by-path/platform-20980000.usb-usb-0:1:1.0-scsi-0:0:0:0
E: TAGS=:systemd:

I have tried to mount, fsck or smartctl. Every time the process freeze before the device is disconnected.

Running dmesg clearly shows that there is something wrong although I don't have the expertise to understand what (this is what I get after trying to run fsck)


[ 3389.694711] usb 1-1: New USB device found, idVendor=0781, idProduct=5567, bcdDevice= 1.00
[ 3389.694781] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3389.694804] usb 1-1: Product: Cruzer Blade
[ 3389.694829] usb 1-1: Manufacturer: SanDisk
[ 3389.694875] usb 1-1: SerialNumber: 4C530000840511105494
[ 3389.715481] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 3389.726487] scsi host6: usb-storage 1-1:1.0
[ 3390.734484] scsi 6:0:0:0: Direct-Access SanDisk Cruzer Blade 1.00 PQ: 0 ANSI: 6
[ 3390.749396] sd 6:0:0:0: Attached scsi generic sg0 type 0
[ 3390.752166] sd 6:0:0:0: [sdg] 30031872 512-byte logical blocks: (15.4 GB/14.3 GiB)
[ 3390.763291] sd 6:0:0:0: [sdg] Write Protect is off
[ 3390.763334] sd 6:0:0:0: [sdg] Mode Sense: 43 00 00 00
[ 3390.765036] sd 6:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 3390.813661] sdg: sdg1
[ 3390.834428] sd 6:0:0:0: [sdg] Attached SCSI removable disk
[ 3423.873628] Indeed it is in host mode hprt0 = 00001101
[ 3424.093241] usb 1-1: reset high-speed USB device number 9 using dwc_otg
[ 3429.133130] Indeed it is in host mode hprt0 = 00001101
[ 3429.353063] usb 1-1: device descriptor read/64, error -110
[ 3444.573403] Indeed it is in host mode hprt0 = 00001101
[ 3444.793285] usb 1-1: device descriptor read/64, error -110
[ 3444.913324] Indeed it is in host mode hprt0 = 00001101
[ 3445.133152] usb 1-1: reset high-speed USB device number 9 using dwc_otg
[ 3450.173369] Indeed it is in host mode hprt0 = 00001101
[ 3450.393296] usb 1-1: device descriptor read/64, error -110
[ 3465.613382] Indeed it is in host mode hprt0 = 00001101
[ 3465.833200] usb 1-1: device descriptor read/64, error -110
[ 3465.953261] Indeed it is in host mode hprt0 = 00001101
[ 3466.173642] usb 1-1: reset high-speed USB device number 9 using dwc_otg
[ 3471.214171] usb 1-1: device descriptor read/8, error -110
[ 3476.413406] usb 1-1: device descriptor read/8, error -110
[ 3476.533484] Indeed it is in host mode hprt0 = 00001101
[ 3476.753171] usb 1-1: reset high-speed USB device number 9 using dwc_otg
[ 3481.853372] usb 1-1: device descriptor read/8, error -110
[ 3487.053192] usb 1-1: device descriptor read/8, error -110
[ 3487.174190] usb 1-1: USB disconnect, device number 9
[ 3487.213374] blk_update_request: I/O error, dev sdg, sector 2048 op 0x1WRITE) flags 0x800 phys_seg 1 prio class 0
[ 3487.213428] Buffer I/O error on dev sdg1, logical block 0, lost sync page write
[ 3487.230351] blk_update_request: I/O error, dev sdg, sector 30031744 op 0x0READ) flags 0x80700 phys_seg 1 prio class 0
[ 3487.230600] blk_update_request: I/O error, dev sdg, sector 30031744 op 0x0READ) flags 0x0 phys_seg 1 prio class 0
[ 3487.230635] Buffer I/O error on dev sdg1, logical block 30029696, async page read
[ 3487.236284] Buffer I/O error on dev sdg1, logical block 30029697, async page read
[ 3487.236330] Buffer I/O error on dev sdg1, logical block 30029698, async page read
[ 3487.236356] Buffer I/O error on dev sdg1, logical block 30029699, async page read
[ 3487.236379] Buffer I/O error on dev sdg1, logical block 30029700, async page read
[ 3487.236401] Buffer I/O error on dev sdg1, logical block 30029701, async page read
[ 3487.236422] Buffer I/O error on dev sdg1, logical block 30029702, async page read
[ 3487.236444] Buffer I/O error on dev sdg1, logical block 30029703, async page read
[ 3487.463453] Indeed it is in host mode hprt0 = 00001501
[ 3487.934369] usb 1-1: new high-speed USB device number 10 using dwc_otg
[ 3488.384162] FAT-fs (sdg1): Directory bread(block 32768) failed
[ 3488.384207] FAT-fs (sdg1): Directory bread(block 32769) failed
[ 3488.384256] FAT-fs (sdg1): Directory bread(block 32770) failed
[ 3488.384285] FAT-fs (sdg1): Directory bread(block 32771) failed
[ 3488.384310] FAT-fs (sdg1): Directory bread(block 32772) failed
[ 3488.384333] FAT-fs (sdg1): Directory bread(block 32773) failed
[ 3488.384373] FAT-fs (sdg1): Directory bread(block 32774) failed
[ 3488.384403] FAT-fs (sdg1): Directory bread(block 32775) failed
[ 3488.384428] FAT-fs (sdg1): Directory bread(block 32776) failed
[ 3488.384452] FAT-fs (sdg1): Directory bread(block 32777) failed
[ 3492.973372] Indeed it is in host mode hprt0 = 00001101
[ 3493.193264] usb 1-1: device descriptor read/64, error -110
[ 3508.413625] Indeed it is in host mode hprt0 = 00001101
[ 3508.633248] usb 1-1: device descriptor read/64, error -110
[ 3508.753404] Indeed it is in host mode hprt0 = 00001101
[ 3508.973263] usb 1-1: new high-speed USB device number 11 using dwc_otg
[ 3514.013517] Indeed it is in host mode hprt0 = 00001101
[ 3514.243321] usb 1-1: device descriptor read/64, error -110


The easy answer would be: "Your device is dead" except that if I plug it in the smart TV it can access the content fine.

The TV runs some version of Linux, that I'm guessing is not too regarding to some issues on the USB drive. However, I lack the technical expertise to understand why and how. Maybe using another version of Linux, or disabling some features. I would very much appreciate any help as it is extremely frustrating to know that there is a solution but I just lack knowledge to find it.

Not sure why you think your TV runs 'some version of Linux', but the obvious answer is that the filesystem ON the device can't be read by your RPI. You posted the filesystem type...FAT. What command are you using to try to mount it?? And typically that bread error comes because the stick was yanked out without being unmounted correctly, and it's trying to 'rebuild' the array. Try to run 'fsck.vfat -nVv' on it, and see what happens.

Also, have you tried to mount it anywhere ELSE? Such as on a Windows system? After running the fsck, it may be readable. And if that content is so 'very important', why don't you have backups of it, and why are you entrusting it to a cheap USB stick?

Sounds like a file format issue to me. What format is the partition? It could be something weird.

Samsung Smart TVs (since 2015) run `some version of Linux` called Tizen.

Huh...good catch. Not surprising, though, but first I heard of it. Regardless, they can either fsck the device in question or try to mount it elsewhere. The fact they posted from a Windows system indicates they can probably just plug in a FAT formatted device, and it'll just come up.

How?
Please show us, with 'mount -v ....'.
Please use CODE tags for code & output, see my signature.