Arch Linux

mutterhunt

Member

From: Groningen / NL

Registered: 2021-07-27

Posts: 12

is this USB-stick for the waste-basket now?

usb 2-1.2: new high-speed USB device number 21 using ehci-pci
[32997.048439] usb 2-1.2: config 1 interface 0 altsetting 0 bulk endpoint 0x2 has invalid maxpacket 64

[32997.048461] usb 2-1.2: config 1 interface 0 altsetting 0 bulk endpoint 0x82 has invalid maxpacket 64

[32997.048812] usb 2-1.2: New USB device found, idVendor=23a9, idProduct=ef18, bcdDevice= 1.00

[32997.048825] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[32997.048832] usb 2-1.2: Product: Mass Storage
[32997.048837] usb 2-1.2: Manufacturer: AI210
[32997.049421] usb-storage 2-1.2:1.0: USB Mass Storage device detected
[32997.065463] scsi host7: usb-storage 2-1.2:1.0

and from time to time:

usb 2-1.2: reset high-speed USB device number 16 using ehci-pci
[11815.208786] usb 2-1.2: device descriptor read/64, error -110

I installed FreeBSD and it booted wonderful from the stick, but after a reboot it has been suddenly inacessable; no rescue with "usbdump" possible, as it goes into an infinite loop.

what has linux to do with it, you might ask? there's also no recovery possible on android/iphone so linux is the choice. I'm not interested in the data but for "dd if=/dev/sdb of=/dev/null BS=1" it misses sdb as not present.

any hints, someone told me it has something to do with the voltage, but I think simple superblock and magic number are broken. It has just one partition in FreeBSDs UFS. It's not mountable and not available at lsusb.

lizbeth

Last edited by mutterhunt (2022-01-27 00:47:30)

mpan

Member

Registered: 2012-08-01

Posts: 1,597

Website

Re: is this USB-stick for the waste-basket now?

The error is a communication error on the USB protocol level. Therefore it may also be a faulty USB port or hub. Test it on another computer⁽¹⁾ or, if you are using an external hub, without it. If the USB stick also fails there, you may assume it is broken and throw it away. If it’s indeed broken, there is no sane method of retrieving the data. The “insane” method is connecting directly to the NAND memory, as with this chip it’s probably separate from the USB controller, in hope it is fine and dumping everything directly. But that is forensics lab level task that requires skill and would cost you more than a $1 stick was worth — both in terms of equipment and effort.

I will skip the obligatory “stop thinking ‘dd’ each time word ‘disk’ appears” section, but since you used a dd invocation that suggests some particular misunderstanding: that `bs=1` there is effectively somewhere between doing nothing and “make a syscall per every byte written to ‘/dev/null’”.
____
⁽¹⁾ I assume that by “no recovery possible on android/iphone” you meant no relevant software available, not that it can’t be accessed there. If the latter is true, there is no need to test it further: it’s dead.

Last edited by mpan (2022-01-27 18:24:29)

---

Paperclips in avatars? | Sometimes I seem a bit harsh — don’t get offended too easily!