Recover Bricked USB

Getting your soundcard to work, using Debian on non-i386 hardware, etc

Recover Bricked USB

Postby oddmanout » 2019-11-07 21:50

Okay everyone, I've got a fun one. I bricked a perfectly good USB stick by misusing dd to write a FreeBSD.img file to it and it got pulled mid-transfer.

The USB stick was messed up, so I attempted to use gparted to correct it but it wouldn't modify anything. I then put it in Windows and was able to format upto about 40% before it failed. Now, my Linux machine won't even assign a block dev label to it. It's simply not coming up. The dmesg logs are telling, which I'll post below. My question to the advanced/expert level guys is, are there any tools that can work at a lower-level than /dev/sdX like flashing firmware to a PCI channel or something crazy like that?

Please help!

Here is the dmesg output...you can clearly see it's borked:

Code: Select all
[35078.615059] usb 1-4-port2: disabled by hub (EMI?), re-enabling...
[35078.615078] usb 1-4.2: USB disconnect, device number 53
[35078.615443] usblp1: removed
[35078.839010] usb 1-4.2: new high-speed USB device number 62 using xhci_hcd
[35078.941181] usb 1-4.2: New USB device found, idVendor=04f9, idProduct=0320, bcdDevice= 1.00
[35078.941192] usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[35078.941198] usb 1-4.2: Product: MFC-L2740DW
[35078.941204] usb 1-4.2: Manufacturer: Brother
[35078.941210] usb 1-4.2: SerialNumber: U63889G5N432902
[35078.953337] usblp 1-4.2:1.0: usblp1: USB Bidirectional printer dev 62 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0320
[35209.544456] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[35249.616101] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[35258.174805] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[35757.527746] usb 1-4-port2: disabled by hub (EMI?), re-enabling...
[35757.527766] usb 1-4.2: USB disconnect, device number 62
[35757.528188] usblp1: removed
[35757.750757] usb 1-4.2: new high-speed USB device number 63 using xhci_hcd
[35757.852297] usb 1-4.2: New USB device found, idVendor=04f9, idProduct=0320, bcdDevice= 1.00
[35757.852301] usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[35757.852303] usb 1-4.2: Product: MFC-L2740DW
[35757.852305] usb 1-4.2: Manufacturer: Brother
[35757.852306] usb 1-4.2: SerialNumber: U63889G5N432902
[35757.859465] usblp 1-4.2:1.0: usblp1: USB Bidirectional printer dev 63 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0320
[36249.087139] usb 1-2: new high-speed USB device number 64 using xhci_hcd
[36249.235339] usb 1-2: New USB device found, idVendor=abcd, idProduct=1234, bcdDevice= 1.00
[36249.235347] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[36249.235352] usb 1-2: Product: UDisk           
[36249.235356] usb 1-2: Manufacturer: General
[36249.235360] usb 1-2: SerialNumber: Љ
[36249.237213] usb-storage 1-2:1.0: USB Mass Storage device detected
[36249.237672] scsi host3: usb-storage 1-2:1.0
[36250.263364] scsi 3:0:0:0: Direct-Access     General  UDisk            5.00 PQ: 0 ANSI: 2
[36250.264442] sd 3:0:0:0: Attached scsi generic sg1 type 0
[36250.265209] sd 3:0:0:0: [sdb] 15974400 512-byte logical blocks: (8.18 GB/7.62 GiB)
[36250.265323] sd 3:0:0:0: [sdb] Write Protect is off
[36250.265325] sd 3:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[36250.265446] sd 3:0:0:0: [sdb] No Caching mode page found
[36250.265449] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[36250.274907]  sdb: sdb1 sdb2
[36250.276400] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[36250.706218] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[36251.119598] EXT4-fs (sdb2): mounting ext3 file system using the ext4 subsystem
[36252.710528] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
[36270.922756] JFS: nTxBlock = 8192, nTxLock = 65536
[36270.939667] NILFS version 2 loaded
[36271.005469] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[36309.424801] usb 1-2: USB disconnect, device number 64
[36309.427602] print_req_error: I/O error, dev sdb, sector 64
[36309.427622] Buffer I/O error on dev sdb1, logical block 1, lost async page write
[36309.427646] print_req_error: I/O error, dev sdb, sector 24640
[36309.427657] Buffer I/O error on dev sdb1, logical block 24577, lost async page write
[36309.507425] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[36309.520731] Buffer I/O error on dev sdb2, logical block 645, lost sync page write
[36309.520735] JBD2: Error -5 detected when updating journal superblock for sdb2-8.
[36309.520737] Aborting journal on device sdb2-8.
[36309.520739] Buffer I/O error on dev sdb2, logical block 645, lost sync page write
[36309.520740] JBD2: Error -5 detected when updating journal superblock for sdb2-8.
[36309.524695] FAT-fs (sdb1): unable to read boot sector to mark fs as dirty
[36315.684542] usb 1-2: new high-speed USB device number 65 using xhci_hcd
[36315.833096] usb 1-2: New USB device found, idVendor=abcd, idProduct=1234, bcdDevice= 1.00
[36315.833118] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[36315.833130] usb 1-2: Product: UDisk           
[36315.833143] usb 1-2: Manufacturer: General
[36315.833152] usb 1-2: SerialNumber: Љ
[36315.842500] usb-storage 1-2:1.0: USB Mass Storage device detected
[36315.844533] scsi host3: usb-storage 1-2:1.0
[36316.852657] scsi 3:0:0:0: Direct-Access     General  UDisk            5.00 PQ: 0 ANSI: 2
[36316.852859] sd 3:0:0:0: Attached scsi generic sg1 type 0
[36316.853382] sd 3:0:0:0: [sdb] 7866368 512-byte logical blocks: (4.03 GB/3.75 GiB)
[36316.853518] sd 3:0:0:0: [sdb] Write Protect is off
[36316.853519] sd 3:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[36316.853624] sd 3:0:0:0: [sdb] No Caching mode page found
[36316.853627] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[36316.859278]  sdb: sdb1 sdb2
                sdb2: <bsd: sdb5 >
[36316.862066] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[36317.184068] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[36329.287462]  sdb: sdb1 sdb2
                sdb2: <bsd: sdb5 >
[36331.421009]  sdb: sdb1 sdb2
                sdb2: <bsd: sdb5 >
[36425.176549] usb 1-4.1: new high-speed USB device number 66 using xhci_hcd
[36425.277160] usb 1-4.1: New USB device found, idVendor=abcd, idProduct=1234, bcdDevice= 1.00
[36425.277168] usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[36425.277173] usb 1-4.1: Product: UDisk           
[36425.277177] usb 1-4.1: Manufacturer: General
[36425.277181] usb 1-4.1: SerialNumber: Љ
[36425.279228] usb-storage 1-4.1:1.0: USB Mass Storage device detected
[36425.280373] scsi host4: usb-storage 1-4.1:1.0
[36426.289765] scsi 4:0:0:0: Direct-Access     General  UDisk            5.00 PQ: 0 ANSI: 2
[36426.290930] sd 4:0:0:0: Attached scsi generic sg2 type 0
[36426.291971] sd 4:0:0:0: [sdc] 15974400 512-byte logical blocks: (8.18 GB/7.62 GiB)
[36426.292212] sd 4:0:0:0: [sdc] Write Protect is off
[36426.292221] sd 4:0:0:0: [sdc] Mode Sense: 0b 00 00 08
[36426.292392] sd 4:0:0:0: [sdc] No Caching mode page found
[36426.292405] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[36426.308130]  sdc: sdc1 sdc2
[36426.311838] sd 4:0:0:0: [sdc] Attached SCSI removable disk
[36433.473044]  sdb: sdb1 sdb2
                sdb2: <bsd: sdb5 >
[36433.482600]  sdc: sdc1 sdc2
[36497.585428] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[36545.860821] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[36564.242637] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[36712.883531] usb 1-4.3: reset high-speed USB device number 6 using xhci_hcd
[36762.860798] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[37476.000929] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[37562.947714] perf: interrupt took too long (5038 > 5016), lowering kernel.perf_event_max_sample_rate to 39500
[37820.259542] INFO: task systemd-udevd:372 blocked for more than 120 seconds.
[37820.259560]       Tainted: G           OE     4.19.0-6-amd64 #1 Debian 4.19.67-2+deb10u1
[37820.259568] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[37820.259577] systemd-udevd   D    0   372      1 0x00000324
[37820.259588] Call Trace:
[37820.259613]  ? __schedule+0x2a2/0x870
[37820.259627]  schedule+0x28/0x80
[37820.259637]  schedule_preempt_disabled+0xa/0x10
[37820.259648]  __mutex_lock.isra.8+0x2b5/0x4a0
[37820.259665]  __blkdev_get+0x78/0x550
[37820.259677]  ? bd_acquire+0xd0/0xd0
[37820.259686]  blkdev_get+0x107/0x310
[37820.259701]  ? bd_acquire+0xd0/0xd0
[37820.259710]  do_dentry_open+0x13d/0x370
[37820.259719]  path_openat+0x2c6/0x1480
[37820.259727]  ? terminate_walk+0xe6/0x100
[37820.259737]  ? seccomp_run_filters+0x5c/0xb0
[37820.259746]  do_filp_open+0x93/0x100
[37820.259835]  ? _cond_resched+0x15/0x30
[37820.259846]  ? __check_object_size+0x15d/0x189
[37820.259872]  ? __check_object_size+0x15d/0x189
[37820.259939]  do_sys_open+0x186/0x210
[37820.259967]  do_syscall_64+0x53/0x110
[37820.259992]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[37820.260009] RIP: 0033:0x7f1bd59141ae
[37820.260029] Code: Bad RIP value.
[37820.260045] RSP: 002b:00007ffd08381f00 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
[37820.260060] RAX: ffffffffffffffda RBX: 00007ffd08383040 RCX: 00007f1bd59141ae
[37820.260064] RDX: 00000000000a0800 RSI: 0000560b6ad1db00 RDI: 00000000ffffff9c
[37820.260068] RBP: 0000000000000000 R08: 0000560b6ac5b140 R09: 0000560b6ace6920
[37820.260072] R10: 0000000000000000 R11: 0000000000000246 R12: 0000560b6ad8b830
[37820.260076] R13: 0000000000000000 R14: 00007ffd08383008 R15: 0000560b6ac62ac0
[37843.809047] usb 1-2: USB disconnect, device number 65
[37846.066710] usb 1-2: new high-speed USB device number 67 using xhci_hcd
[37846.215278] usb 1-2: New USB device found, idVendor=abcd, idProduct=1234, bcdDevice= 1.00
[37846.215288] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[37846.215295] usb 1-2: Product: UDisk           
[37846.215301] usb 1-2: Manufacturer: General
[37846.215306] usb 1-2: SerialNumber: Љ
[37846.220434] usb-storage 1-2:1.0: USB Mass Storage device detected
[37846.238857] scsi host3: usb-storage 1-2:1.0
[37847.267410] scsi 3:0:0:0: Direct-Access     General  UDisk            5.00 PQ: 0 ANSI: 2
[37847.268397] sd 3:0:0:0: Attached scsi generic sg1 type 0
[37847.268653] sd 3:0:0:0: [sdb] 7866368 512-byte logical blocks: (4.03 GB/3.75 GiB)
[37847.268815] sd 3:0:0:0: [sdb] Write Protect is off
[37847.268820] sd 3:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[37847.268974] sd 3:0:0:0: [sdb] No Caching mode page found
[37847.268986] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[37847.275906]  sdb: sdb1 sdb2
                sdb2: <bsd: sdb5 >
[37847.282734] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[37867.216638]  sdc: sdc1 sdc2
[37867.230013]  sdb: sdb1 sdb2
                sdb2: <bsd: sdb5 >
[37867.440820]  sdb: sdb1 sdb2
                sdb2: <bsd: sdb5 >
[38463.236150]  sdc: sdc1 sdc2
[38490.235943]  sdc: sdc1 sdc2
[38622.935072] usb 1-4.1: USB disconnect, device number 66
[38648.250592] usb 1-4.1: new high-speed USB device number 68 using xhci_hcd
[38648.351764] usb 1-4.1: New USB device found, idVendor=0781, idProduct=5530, bcdDevice= 1.00
[38648.351778] usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38648.351786] usb 1-4.1: Product: Cruzer
[38648.351793] usb 1-4.1: Manufacturer: SanDisk
[38648.351800] usb 1-4.1: SerialNumber: 200515362207D0A3935C
[38648.353869] usb-storage 1-4.1:1.0: USB Mass Storage device detected
[38648.361734] scsi host5: usb-storage 1-4.1:1.0
[38649.387463] scsi 5:0:0:0: Direct-Access     SanDisk  Cruzer           1.00 PQ: 0 ANSI: 2
[38649.388588] sd 5:0:0:0: Attached scsi generic sg2 type 0
[38649.388872] sd 5:0:0:0: [sdd] 15625216 512-byte logical blocks: (8.00 GB/7.45 GiB)
[38649.389977] sd 5:0:0:0: [sdd] Write Protect is off
[38649.389983] sd 5:0:0:0: [sdd] Mode Sense: 03 00 00 00
[38649.390217] sd 5:0:0:0: [sdd] No Caching mode page found
[38649.390228] sd 5:0:0:0: [sdd] Assuming drive cache: write through
[38649.397269]  sdd: sdd1 sdd2
[38649.400787] sd 5:0:0:0: [sdd] Attached SCSI removable disk
[38666.058225] INFO: task systemd-udevd:11752 blocked for more than 120 seconds.
[38666.058242]       Tainted: G           OE     4.19.0-6-amd64 #1 Debian 4.19.67-2+deb10u1
[38666.058247] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[38666.058255] systemd-udevd   D    0 11752      1 0x00000320
[38666.058266] Call Trace:
[38666.058288]  ? __schedule+0x2a2/0x870
[38666.058298]  schedule+0x28/0x80
[38666.058307]  schedule_preempt_disabled+0xa/0x10
[38666.058316]  __mutex_lock.isra.8+0x2b5/0x4a0
[38666.058330]  __blkdev_get+0x78/0x550
[38666.058341]  ? bd_acquire+0xd0/0xd0
[38666.058350]  blkdev_get+0x107/0x310
[38666.058361]  ? bd_acquire+0xd0/0xd0
[38666.058370]  do_dentry_open+0x13d/0x370
[38666.058380]  path_openat+0x2c6/0x1480
[38666.058388]  ? terminate_walk+0xe6/0x100
[38666.058399]  ? seccomp_run_filters+0x5c/0xb0
[38666.058408]  do_filp_open+0x93/0x100
[38666.058419]  ? _cond_resched+0x15/0x30
[38666.058428]  ? __check_object_size+0x15d/0x189
[38666.058435]  ? __check_object_size+0x15d/0x189
[38666.058447]  do_sys_open+0x186/0x210
[38666.058459]  do_syscall_64+0x53/0x110
[38666.058470]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[38666.058479] RIP: 0033:0x7fb258f041ae
[38666.058493] Code: Bad RIP value.
[38666.058498] RSP: 002b:00007ffeac913300 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
[38666.058507] RAX: ffffffffffffffda RBX: 00007ffeac914440 RCX: 00007fb258f041ae
[38666.058511] RDX: 00000000000a0800 RSI: 00005608236622a0 RDI: 00000000ffffff9c
[38666.058515] RBP: 0000000000000000 R08: 0000560822032140 R09: 0000560823672e70
[38666.058519] R10: 0000000000000000 R11: 0000000000000246 R12: 0000560823662150
[38666.058523] R13: 0000000000000000 R14: 00007ffeac914408 R15: 0000560822039ac0
[38786.886586] INFO: task systemd-udevd:11752 blocked for more than 120 seconds.
[38786.886599]       Tainted: G           OE     4.19.0-6-amd64 #1 Debian 4.19.67-2+deb10u1
[38786.886604] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[38786.886610] systemd-udevd   D    0 11752      1 0x00000324
[38786.886618] Call Trace:
[38786.886636]  ? __schedule+0x2a2/0x870
[38786.886644]  schedule+0x28/0x80
[38786.886651]  schedule_preempt_disabled+0xa/0x10
[38786.886658]  __mutex_lock.isra.8+0x2b5/0x4a0
[38786.886670]  __blkdev_get+0x78/0x550
[38786.886680]  ? bd_acquire+0xd0/0xd0
[38786.886688]  blkdev_get+0x107/0x310
[38786.886698]  ? bd_acquire+0xd0/0xd0
[38786.886705]  do_dentry_open+0x13d/0x370
[38786.886714]  path_openat+0x2c6/0x1480
[38786.886721]  ? terminate_walk+0xe6/0x100
[38786.886729]  ? seccomp_run_filters+0x5c/0xb0
[38786.886737]  do_filp_open+0x93/0x100
[38786.886764]  ? _cond_resched+0x15/0x30
[38786.886772]  ? __check_object_size+0x15d/0x189
[38786.886779]  ? __check_object_size+0x15d/0x189
[38786.886790]  do_sys_open+0x186/0x210
[38786.886802]  do_syscall_64+0x53/0x110
[38786.886814]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[38786.886821] RIP: 0033:0x7fb258f041ae
[38786.886836] Code: Bad RIP value.
[38786.886840] RSP: 002b:00007ffeac913300 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
[38786.886847] RAX: ffffffffffffffda RBX: 00007ffeac914440 RCX: 00007fb258f041ae
[38786.886851] RDX: 00000000000a0800 RSI: 00005608236622a0 RDI: 00000000ffffff9c
[38786.886855] RBP: 0000000000000000 R08: 0000560822032140 R09: 0000560823672e70
[38786.886859] R10: 0000000000000000 R11: 0000000000000246 R12: 0000560823662150
[38786.886863] R13: 0000000000000000 R14: 00007ffeac914408 R15: 0000560822039ac0
[38786.886898] INFO: task blkid:14792 blocked for more than 120 seconds.
[38786.886907]       Tainted: G           OE     4.19.0-6-amd64 #1 Debian 4.19.67-2+deb10u1
[38786.886911] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[38786.886917] blkid           D    0 14792  14790 0x00000000
[38786.886925] Call Trace:
[38786.886936]  ? __schedule+0x2a2/0x870
[38786.886945]  schedule+0x28/0x80
[38786.886953]  schedule_preempt_disabled+0xa/0x10
[38786.886962]  __mutex_lock.isra.8+0x2b5/0x4a0
[38786.886970]  ? _cond_resched+0x15/0x30
[38786.886979]  __blkdev_get+0x78/0x550
[38786.886989]  ? bd_acquire+0xd0/0xd0
[38786.886997]  blkdev_get+0x107/0x310
[38786.887008]  ? bd_acquire+0xd0/0xd0
[38786.887017]  do_dentry_open+0x13d/0x370
[38786.887026]  path_openat+0x2c6/0x1480
[38786.887036]  ? __check_object_size+0x15d/0x189
[38786.887045]  do_filp_open+0x93/0x100
[38786.887055]  ? __check_object_size+0x15d/0x189
[38786.887066]  do_sys_open+0x186/0x210
[38786.887077]  do_syscall_64+0x53/0x110
[38786.887087]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[38786.887093] RIP: 0033:0x7f264e2fa1ae
[38786.887102] Code: Bad RIP value.
[38786.887106] RSP: 002b:00007fffc71f52d0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
[38786.887113] RAX: ffffffffffffffda RBX: 0000555deacba590 RCX: 00007f264e2fa1ae
[38786.887117] RDX: 0000000000080000 RSI: 0000555deacb9570 RDI: 00000000ffffff9c
[38786.887121] RBP: 0000555deacb72b0 R08: 000000000000102f R09: 0000555deacba490
[38786.887124] R10: 0000000000000000 R11: 0000000000000246 R12: 000000005dc48e02
[38786.887128] R13: 00007f264e4253c4 R14: 00000000ddc48e02 R15: 00007f264e414425
[38821.916455]  sdb: sdb1 sdb2
                sdb2: <bsd: sdb5 >
[39215.305220] usb 1-2: USB disconnect, device number 67
[39218.565588] usb 1-2: new high-speed USB device number 69 using xhci_hcd
[39218.714220] usb 1-2: New USB device found, idVendor=abcd, idProduct=1234, bcdDevice= 1.00
[39218.714228] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[39218.714232] usb 1-2: Product: UDisk           
[39218.714236] usb 1-2: Manufacturer: General
[39218.714240] usb 1-2: SerialNumber: Љ
[39218.718793] usb-storage 1-2:1.0: USB Mass Storage device detected
[39218.719367] scsi host3: usb-storage 1-2:1.0
[39219.737992] scsi 3:0:0:0: Direct-Access     General  UDisk            5.00 PQ: 0 ANSI: 2
[39219.739126] sd 3:0:0:0: Attached scsi generic sg1 type 0
[39219.741832] sd 3:0:0:0: [sdb] 7866368 512-byte logical blocks: (4.03 GB/3.75 GiB)
[39219.742070] sd 3:0:0:0: [sdb] Write Protect is off
[39219.742093] sd 3:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[39219.742460] sd 3:0:0:0: [sdb] No Caching mode page found
[39219.742478] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[39219.753208] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[39226.990935]  sdd: sdd1 sdd2
[39254.587467]  sdd: sdd1 sdd2
[39254.738749]  sdd: sdd1 sdd2
[39267.803587]  sdd: sdd1 sdd2
[39344.929413] usb 1-2: USB disconnect, device number 69
[39345.289517] usb 1-2: new high-speed USB device number 70 using xhci_hcd
[39389.309506]  sdd: sdd1 sdd2
[39655.343917]  sdd: sdd1 sdd2
                sdd2: <bsd: sdd5 >
[39655.353711]  sdd: sdd1 sdd2
                sdd2: <bsd: sdd5 >
[39667.312446] usb 1-4.1: USB disconnect, device number 68
[39813.639116] usb 1-2: new high-speed USB device number 71 using xhci_hcd
[39818.919051] usb 1-2: device descriptor read/64, error -110
[39834.534566] usb 1-2: device descriptor read/64, error -110
[39834.770534] usb 1-2: new high-speed USB device number 72 using xhci_hcd
[39839.914359] usb 1-2: device descriptor read/64, error -110
[39855.529969] usb 1-2: device descriptor read/64, error -110
[39855.641893] usb usb1-port2: attempt power cycle
[39856.293865] usb 1-2: new high-speed USB device number 73 using xhci_hcd
[39861.541768] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[39866.917620] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[39867.125570] usb 1-2: device not accepting address 73, error -62
[39867.253547] usb 1-2: new high-speed USB device number 74 using xhci_hcd
[39872.293495] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[39877.673263] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[39877.881185] usb 1-2: device not accepting address 74, error -62
[39877.881328] usb usb1-port2: unable to enumerate USB device
[39898.331904] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[39927.448987] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[39937.507034] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[39958.612902] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[39972.436572] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[39990.089090] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[40052.738246] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[40135.941268] usb 1-2: new high-speed USB device number 75 using xhci_hcd
[40141.213102] usb 1-2: device descriptor read/64, error -110
[40156.828711] usb 1-2: device descriptor read/64, error -110
[40157.064584] usb 1-2: new high-speed USB device number 76 using xhci_hcd
[40162.208505] usb 1-2: device descriptor read/64, error -110
[40177.820072] usb 1-2: device descriptor read/64, error -110
[40177.928054] usb usb1-port2: attempt power cycle
[40178.579948] usb 1-2: new high-speed USB device number 77 using xhci_hcd
[40183.835819] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[40189.211691] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[40189.419630] usb 1-2: device not accepting address 77, error -62
[40189.547628] usb 1-2: new high-speed USB device number 78 using xhci_hcd
[40194.587451] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[40199.963350] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[40200.171285] usb 1-2: device not accepting address 78, error -62
[40200.171470] usb usb1-port2: unable to enumerate USB device
[40261.286260] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[40423.689986] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[40440.247072] usb 1-4.1: new high-speed USB device number 79 using xhci_hcd
[40445.538848] usb 1-4.1: device descriptor read/64, error -110
[40461.154313] usb 1-4.1: device descriptor read/64, error -110
[40461.342304] usb 1-4.1: new high-speed USB device number 80 using xhci_hcd
[40466.530201] usb 1-4.1: device descriptor read/64, error -110
[40482.145682] usb 1-4.1: device descriptor read/64, error -110
[40482.253824] usb 1-4-port1: attempt power cycle
[40482.865599] usb 1-4.1: new high-speed USB device number 81 using xhci_hcd
[40487.957491] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[40493.330396] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[40493.545241] usb 1-4.1: device not accepting address 81, error -62
[40493.629194] usb 1-4.1: new high-speed USB device number 82 using xhci_hcd
[40498.705144] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[40504.080977] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[40504.288942] usb 1-4.1: device not accepting address 82, error -62
[40504.289093] usb 1-4-port1: unable to enumerate USB device
[41030.292716] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[41210.382949] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[41287.175132] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[41332.434574] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[41346.550030] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
[41376.968439] usb 1-2: new high-speed USB device number 83 using xhci_hcd
[41382.260189] usb 1-2: device descriptor read/64, error -110
[41397.876845] usb 1-2: device descriptor read/64, error -110
[41398.111647] usb 1-2: new high-speed USB device number 84 using xhci_hcd
[41403.251606] usb 1-2: device descriptor read/64, error -110
[41418.867074] usb 1-2: device descriptor read/64, error -110
[41418.975203] usb usb1-port2: attempt power cycle
[41419.638968] usb 1-2: new high-speed USB device number 85 using xhci_hcd
[41424.887071] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[41430.258724] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[41430.466677] usb 1-2: device not accepting address 85, error -62
[41430.594622] usb 1-2: new high-speed USB device number 86 using xhci_hcd
[41435.634617] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[41441.014871] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[41441.222288] usb 1-2: device not accepting address 86, error -62
[41441.222397] usb usb1-port2: unable to enumerate USB device
[41528.596990] snd_hda_codec_conexant hdaudioC0D0: action: 2 gpio_led: 0
oddmanout
 
Posts: 3
Joined: 2019-11-07 21:41

Re: Recover Bricked USB

Postby sunrat » 2019-11-07 22:17

Try writing a new partition table to it. Gparted can do that.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 2882
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: Recover Bricked USB

Postby oddmanout » 2019-11-08 00:58

sunrat wrote:Try writing a new partition table to it. Gparted can do that.


I've tried that and every other thing I could find on the internet. The problem is that the device won't actually initiate. The OS will never assign it as a block device. You can see that the MB and Kernel see it in the dmesg output, but there is an I/O timeout error that prevents it from ever fully coming up. The only thing I haven't tried yet is putting it in my FreeBSD box and attempting the solution outlined here: https://groups.google.com/forum/#!topic ... uiTGpiMw54

Code: Select all
Try to set:

sysctl hw.usb.xhci.xhci_port_route=-1

In /boot/loader.conf


This seems promising, and I'll report back on the status.

For information purposes, I even tried downloading HP's Storage Low Level Format tool, and the problem there was the same. Window's device manager see's the device but it has an error'd status. The disk mgmt utility doesn't even see the thumb drive.

I'm convinced this should be fixable since it's a problem I caused with software, and I know it was working just fine up until that point. This would be the second USB stick that I've had this happen to in as many months. Anyway, the search continues. Thanks for responding.
oddmanout
 
Posts: 3
Joined: 2019-11-07 21:41

Re: Recover Bricked USB

Postby Soul Singin' » 2019-11-08 02:08

oddmanout wrote:advanced/expert level guys

I am not one of those guys, but:

oddmanout wrote:it got pulled mid-transfer.

That sounds bad.

A new device costs money, but your time is valuable too. ("Time is money"). So if I were in your position, I would consider:

  • the time cost of a repair
  • the probability of a successful repair
  • the financial cost of a new device
Then I would make the appropriate decision.

Best wishes,
- Soul
User avatar
Soul Singin'
 
Posts: 1578
Joined: 2008-12-21 07:02

Re: Recover Bricked USB

Postby Deb-fan » 2019-11-08 02:41

Also not any sort of "expert", tell the truth don't think I'll ever be able to consider myself such. No matter how long I dork with gnu/Linux will be a perma-noob. It's an endless and ever changing moving target anyway. :D

Really nothing to add, was going to suggest what Sunrat already had. Never come up against a usb drive which couldn't be recovered ... YET. Not supposed to dd drives that are mounted anyway. Is gparted detecting it in the list of devices ? Mentioned you've already tried using it for many things on the thumb drive, so assuming it is and thus if so, very likely it's able to be recovered in my opinion. Good luck.
Deb-fan
 
Posts: 445
Joined: 2012-08-14 12:27

Re: Recover Bricked USB

Postby peer » 2019-11-08 05:48

You can try to write a new partiotiontable with Gparted in to steps. First, write a different parttiontable(f.e loop) and then the standard msdos partitiontable. Sometimes this works with unwilling usb sticks.

Another possiblity is to use hddguru HDD Low Level Format utility(in windows: http://hddguru.com/software/HDD-LLF-Low ... rmat-Tool/
peer
 
Posts: 75
Joined: 2017-03-26 10:14

Re: Recover Bricked USB

Postby pylkko » 2019-11-08 11:04

The kernel log seems to show that the device is being initiated multiple times and that there are i/o related processes that timeout. This suggests that either the device is
not working and producing results that the kernel expects or the kernel module is getting confused. I think something like this could happen for multiple reasons. First, it
could be that the control electronics on the device are damaged. In this case, fixing it would be a waste of time.

Second, it could be that the firmware (i.e UEFI or BIOS) is doing something that prevents the device from co-operating with the kernel. For example, in theory it could be that the devices gets offlined by power management quickly if it is in some abnormal state for long. So if you just turn off all power management in firmware, it might work.

I have read some stories online where people claim that their mass storage device didn't work under USB3 and xhci
so they either used USB2 ports or blocked the driver and then managed to get it to work.

Lastly, it could be some kind of bug in the driver. In this case it might work on older versions of the kernel or on other kernels from other OS's.

This is all pretty much guessing, because I don't have the time to google all those error numbers and messages.

In any case, if you not get a block device, you cannot expect to be able to write a new working partition table.
Last edited by pylkko on 2019-11-08 19:10, edited 1 time in total.
User avatar
pylkko
 
Posts: 1588
Joined: 2014-11-06 19:02

Re: Recover Bricked USB

Postby v&n » 2019-11-08 17:35

pylkko wrote:First, it could be that the control electronics on the device are damaged..

+1
The "pulled mid-transfer" thing may just be a coincidence, or the internal circuitry (most likely the flash memory) of the drive might have been too sensitive.

I usually get this "unable to enumerate USB device" error when a device (e.g. a usb hdd) can't be initialized due to a bad cable/connection or a port that can't provide enough power to it. This error occurs more frequently when trying the same device on an old PC/laptop compared to a new one. My personal observations suggest that old usb hdd's tend to require more power, while the 5v supply in computers tends to get weaker with time.

An interesting experience of mine (..and my conclusion may be wrong; I haven't done enough experiments to establish that this is always true) is that memory cards/pendrives that are frequently used in cheap devices (like those dirt-cheap Chinese multifunction music players) succumb to this error more often, probably due to the badly managed power supply in them that tends to send higher voltage or 'voltage surge' sometimes (the 5v supply in these devices seems to be directly proportional to the incoming 12v supply that is taken directly from the car batteries whose peak charge can go as high as 16.8v).

Now an UNCONFIRMED AND RISKY method that I've been told (but have never tested myself) can provide a temporary solution in case of the above 'succumbed to high voltage' type cases (can't say if it can apply to your case as well; the highlighted error message is the only similarity) -

If you can control the 5v supply on the device using some properly regulated control circuit, then stepping up the supply in steps of 0.1v can make the device readable/writable again in many cases. Usually a pen drive that acts like an empty card reader, or a memory card that has become 'read-only' or unreadable, starts working again around a supply of 5.5 volts (pure D.C.). But in any case, anything above 6.5v should be considered as intentionally 'burning the device' !! (although the person who says they use this trick also say that most of the pendrives can tolerate much higher voltage). Once again, I can not confirm this method as I haven't yet found an opportunity to test this myself, even though the theory sounds satisfactory. Besides, the device won't be usable on a normal computer again, so this can only be helpful for data recovery.

I guess this boils down to what Soul Singin already said. :)
v&n
 
Posts: 621
Joined: 2015-02-04 02:57

Re: Recover Bricked USB

Postby pylkko » 2019-11-08 19:06

Something like this is also the reason why sometimes a few of the ports work, while other don't. This is simply because in many computer cases there is an integrated usb hub that splits "one real port" into more physical ports. However, if the wires (and ohter pieces) are low quality, they might have enough resistance to take the voltage down some minuscule amount. I believe the USB spec has some range around 5 V that it allows. So people plug a device into one port and it does not work, put it into another and it does, wondering, but not realizing that the other port is way on the other side of the case and has long, thin wires with high internal resistance ultimately causing the device to not get a decent 5 V.

However, if the microcontroller or other parts of the control electronics are gone, you can just toss it because fixing it will cost more money and time than what makes sense.
User avatar
pylkko
 
Posts: 1588
Joined: 2014-11-06 19:02

Re: Recover Bricked USB

Postby shep » 2019-11-08 21:25

Windows will reformat older USB2.0 drives. IRC, you can right click on the drive in the file manager to launch the tool.
You can also do it in Linux.
If you are using Debian 10, Xorg and a VTE you will need the full path for some of these commands.

As root /bin/dmesg after plugging the drive in. The last dmesg entry should show the usb device.

Code: Select all
[11463.224298] usb 1-7: new high-speed USB device number 4 using xhci_hcd
[11463.467824] usb 1-7: New USB device found, idVendor=090c, idProduct=1000, bcdDevice=12.19
[11463.467828] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[11463.467830] usb 1-7: Product: DISK 2.0
[11463.467831] usb 1-7: Manufacturer: USB
[11463.467833] usb 1-7: SerialNumber: AL5GR75JEPN4EPUW
[11463.532283] usb-storage 1-7:1.0: USB Mass Storage device detected
[11463.532492] scsi host9: usb-storage 1-7:1.0
[11463.532727] usbcore: registered new interface driver usb-storage
[11463.551463] usbcore: registered new interface driver uas
[11464.559051] scsi 9:0:0:0: Direct-Access     USB      DISK 2.0         1219 PQ: 0 ANSI: 0 CCS
[11464.559450] sd 9:0:0:0: Attached scsi generic sg2 type 0
[11464.562615] sd 9:0:0:0: [sdb] 1957888 512-byte logical blocks: (1.00 GB/956 MiB)
[11464.563082] sd 9:0:0:0: [sdb] Write Protect is off
[11464.563085] sd 9:0:0:0: [sdb] Mode Sense: 43 00 00 00
[11464.563595] sd 9:0:0:0: [sdb] No Caching mode page found
[11464.563604] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[11464.566764]  sdb: sdb1 sdb2
[11464.569270] sd 9:0:0:0: [sdb] Attached SCSI removable disk


My device has an OpenBSD install image. Be absolutely sure that you have the usb device. If you zero-out the partition table on the drive with Debian (usually sda on single hard drive systems) you will blow away your Debian install. :(

Zero-out the initial sectors where the partition table normally goes.

dd if=/dev/zero of=/dev/sdb bs=512 count=32.

Most drives have MBR partition table and you can use fdisk, parted or other disk partitioning tool, to generate a new MBR.
Make one partition that uses all the available space, enter that partition info into the MBR table.

Decide partition type. vfat will not support over 4mb and drives > 4mb are typically formated with ntfs.or with exfat (extended vfat). Use the partition tool to set partition type in the MBR table and write the table to the usb drive. [Edit] - see correction on file sizes below.

Assuming the first partition is vfat
mkfs.fat -F32 /dev/sdb1

Here are some web guides:
https://appuals.com/how-to-format-a-drive-as-exfat-on-linux/
https://askubuntu.com/questions/934560/format-usb-drive-to-ntfs-so-it-is-usable-under-windows
https://www.lostsaloon.com/technology/how-to-format-usb-drives-flash-drive-from-linux-command-line/

Some newer usb3 drives have firmware and are more difficult, I rebuilt one on a Windows system with the Transcend repair tool. I am distrustful of "Repair Tools" and I made sure I downloaded the "tool w/ firmware" from the drive manufacturers web site.
https://www.easeus.com/data-recovery-solution/transcend-usb-pen-drive-not-detected.html
If you have a second drive of the same manufacture/model/size you may be able to dd the image of the good drive to the bad drive. Note: I have not tested this but I think it should work.
dd if=/dev/sdc (good drive) of=dev sdb(bad drive) bs=1M ; sync
Last edited by shep on 2019-11-09 12:21, edited 5 times in total.
shep
 
Posts: 325
Joined: 2011-03-15 15:22

Re: Recover Bricked USB

Postby sunrat » 2019-11-08 21:58

shep wrote:Decide partition type. vfat will not support over 4mb and drives > 4mb are typically formated with ntfs.or with exfat (extended vfat). Use the partition tool to set partition type in the MBR table and write the table to the usb drive.


Correction. FAT32 (vfat) can be used for up to 2TB partitions, although not recommended as it's relatively inefficient for large drives. The maximum file size is 4GB.

https://answers.microsoft.com/en-us/win ... a6976ac0c0
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 2882
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Re: Recover Bricked USB

Postby oswaldkelso » 2019-11-08 22:47

Bit pissed so ymmv but :

dd and testdisk always seem to fix it if it's possible...

https://www.cgsecurity.org/wiki/TestDisk
Ash init durbatulûk, ash init gimbatul,
Ash init thrakatulûk agh burzum-ishi krimpatul.
User avatar
oswaldkelso
 
Posts: 1184
Joined: 2005-07-26 23:20
Location: UK

Re: Recover Bricked USB

Postby v&n » 2019-11-09 08:26

Formatting, dd, testdisk, low-level format, disk repairing software tools etc. all will work only if the flash memory inside the device becomes 'readable' first (at hardware level). That is, a 'Communication Link' between the flash memory and the computer is the first and foremost requirement for such things to work. Obviously they can't fix it if they can't talk to it.

In this case, all of above come AFTER the 'enumeration' of the device by the system. As long as the "unable to enumerate USB device" error persists, all the 'logical correction' tricks (all of above) are simply ruled out.
v&n
 
Posts: 621
Joined: 2015-02-04 02:57

Re: Recover Bricked USB

Postby pylkko » 2019-11-09 09:18

+1

all of the suggestions posted after my last post require that there is a block device... and according to the OP there isn't...
User avatar
pylkko
 
Posts: 1588
Joined: 2014-11-06 19:02

Re: Recover Bricked USB

Postby sunrat » 2019-11-09 12:53

If the time everyone has taken to post in this thread is accounted for, that <$10 USB stick is worth at least 50 bucks now. :lol:
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!
User avatar
sunrat
 
Posts: 2882
Joined: 2006-08-29 09:12
Location: Melbourne, Australia

Next

Return to Hardware

Who is online

Users browsing this forum: No registered users and 11 guests

fashionable