USB stick not recognised not mounting Reformat

Hello,

I have a bricked USB stick I’m trying to reformat. I have found useful information on the forums here and this is where I have gotten so far:
lsblk = USB stick not recognised
inxi -Jxxx = USB stick not recognised
Then, I tried to run
sudo dmesg -Hw
And plug the stick after. This allowed to see the following:
[ +3,939471] [UFW BLOCK] IN=wlo1 OUT= MAC=14:4f:8a:aa:ff:96:5c:54:6d:6f:9e:92:08:00 SRC=10.56.150.50 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=33692 PROTO=2 MARK=0x3214
[ +1,490301] usb 1-2: new full-speed USB device number 35 using xhci_hcd
[ +0,123359] usb 1-2: device descriptor read/64, error -71
[ +0,229890] usb 1-2: device descriptor read/64, error -71
[ +0,230094] usb 1-2: new full-speed USB device number 36 using xhci_hcd
[ +0,123352] usb 1-2: device descriptor read/64, error -71
[ +0,229877] usb 1-2: device descriptor read/64, error -71
[ +0,106713] usb usb1-port2: attempt power cycle
[ +0,403367] usb 1-2: new full-speed USB device number 37 using xhci_hcd
[ +0,000266] usb 1-2: Device not responding to setup address.
[ +0,206625] usb 1-2: Device not responding to setup address.
[ +0,206419] usb 1-2: device not accepting address 37, error -71
[ +0,123354] usb 1-2: new full-speed USB device number 38 using xhci_hcd
[ +0,000274] usb 1-2: Device not responding to setup address.
[ +0,206569] usb 1-2: Device not responding to setup address.
[ +0,206490] usb 1-2: device not accepting address 38, error -71
[ +0,000108] usb usb1-port2: unable to enumerate USB device
What can I do next?
Thanks

First thing - do you have a pending reboot after receiving a new kernel?

If that is the case - then reboot - and recheck.

Judging from the output - I looks like you have moved the stick between 4 USB ports and you get the same message every time so not recognized by the running kernel - try using a live system - then insert the stick in question and recheck - if the issue persist - it is most likely turned into a paperweight.

I know the stick has an issue, I’m not trying to install Manjaro, I have it already running.
The stick went bad upon etching an image for Pf-Sense.
What I’m trying to do is use Linux tools/tricks to unbrick the USB stick.

Most command line options aren’t able to detect a damaged device, sometimes Gparted or KDE Partition Manager can’t. I’d say that you install the gnome-disk-utility package and run the gnome-disks program, by far it’s the best option I’ve found till now.

1 Like

Thanks I’ll try that!

1 Like

Ok, Installed and opened. USB stick still not listed in there.

please post the output of ‘ls /dev/disk/by-id’

ata-Samsung_SSD_860_EVO_500GB_S3Z2NY0M537663E
ata-Samsung_SSD_860_EVO_500GB_S3Z2NY0M537663E-part1
ata-Samsung_SSD_860_EVO_500GB_S3Z2NY0M537663E-part2
ata-Samsung_SSD_860_EVO_500GB_S3Z2NY0M537663E-part3
ata-Samsung_SSD_860_EVO_500GB_S3Z2NY0M537663E-part4
ata-Samsung_SSD_860_EVO_500GB_S3Z2NY0M537663E-part5
ata-Samsung_SSD_860_EVO_500GB_S3Z2NY0M537663E-part6
nvme-eui.002538b581ba8e03
nvme-eui.002538b581ba8e03-part1
nvme-eui.002538b581ba8e03-part2
nvme-eui.002538b581ba8e03-part3
nvme-eui.002538b581ba8e03-part4
nvme-eui.002538b581ba8e03-part5
nvme-SAMSUNG_MZVLW256HEHP-000H1_S340NX1K531579
nvme-SAMSUNG_MZVLW256HEHP-000H1_S340NX1K531579-part1
nvme-SAMSUNG_MZVLW256HEHP-000H1_S340NX1K531579-part2
nvme-SAMSUNG_MZVLW256HEHP-000H1_S340NX1K531579-part3
nvme-SAMSUNG_MZVLW256HEHP-000H1_S340NX1K531579-part4
nvme-SAMSUNG_MZVLW256HEHP-000H1_S340NX1K531579-part5
wwn-0x5002538e001a241c
wwn-0x5002538e001a241c-part1
wwn-0x5002538e001a241c-part2
wwn-0x5002538e001a241c-part3
wwn-0x5002538e001a241c-part4
wwn-0x5002538e001a241c-part5
wwn-0x5002538e001a241c-part6

Is there any chance that the usb was physically damaged?

Nope. It’s fine, it’s got a led light on it and the led is lit. It crashed when etching the image.

You mean while right? Send me the log

1 Like

you can try a small hack to disable autosuspend and bypass power-issues but first post what ‘cat /sys/module/usbcore/parameters/autosuspend’ does reply

1 Like

It’s not there with this listing.
I was looking at a forum talking about mkUSB, maybe the “restore to atorage device could help” but I can’t find the commands for Manjaro and I’m not sure it’s a good option.

yes, correct

“Ficheiro ou pasta inexistente”
That’s portugues, means file or folder does not exist

is this the output of ‘cat /sys/module/usbcore/parameters/autosuspend’ ?

it is yes

Please send the etcher log… :expressionless:

that was on windows with Balena. I’m on dual boot. It died at 98%.
I think the issue is with the image from Netgear since it crashed 2 drives while etching them.
An prior to this it bricked my firewall while performing standard firmware update.
The image doesn’t pass checksum.

So I’m 99% confident this is an issue with the image that was being etched. Since I don’t want to brick a million USB sticks I’m trying to find a way to unbrick these 2 poor fellas…

I’m asking for the log bro