You are not logged in.
Pages: 1
I recently tried to format an old USB stick with GParted, but an error occurred. Now the USB stick is completely undetectable by the OS. I know for a fact that the USB is getting power, and the error doesn't lie with my USB ports.
How do I fix this? I just need it to be detectable. Then I can format it with cfdisk. Does anybody know what the issue is, or if it is even reparable?
To those reading this with the same issue with their USB sticks,
After some running some commands, as seen below, and some discussion, the conclusion of this post is that
my USB stick has died. There really is no solution, but if you find yourself having these same issues, please
look over the commands below. If you have the same output from them, it is likely that your USB has also died.
Last edited by Tx86 (2023-01-27 20:59:43)
Offline
What does dmesg say when you plug the stick in?
You can use wipefs(8) to clear the device but be careful. It's very easy to nuke your system with that command.
How would I find out what dmesg says? I've only been using GParted (which doesn't detect it at all) and fdisk -l (which also doesn't detect it at all). What command should I use to see what dmesg says?
Offline
Run
# dmesg -w
Then plug in the USB stick and read any new text that appears afterwards. Or post it here if you can't understand it. Just the new text though.
Offline
@Head_on_a_Stick,
[135352.837059] usb 7-2: new SuperSpeed USB device number 4 using xhci_hcd
[135352.863132] usb 7-2: New USB device found, idVendor=8564, idProduct=1000, bcdDevice=11.00
[135352.863141] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[135352.863144] usb 7-2: Product: Mass Storage Device
[135352.863147] usb 7-2: Manufacturer: JetFlash
[135352.863150] usb 7-2: SerialNumber: 350IV78O0H6QXLF4
[135352.865866] usb-storage 7-2:1.0: USB Mass Storage device detected
[135352.866101] scsi host5: usb-storage 7-2:1.0
[135354.193758] scsi 5:0:0:0: Direct-Access JetFlash Transcend 16GB 1100 PQ: 0 ANSI: 6
[135354.195490] sd 5:0:0:0: [sdc] 30851072 512-byte logical blocks: (15.8 GB/14.7 GiB)
[135354.196892] sd 5:0:0:0: [sdc] Write Protect is off
[135354.196902] sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
[135354.197637] sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[135354.203698] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[135354.203707] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
[135354.203711] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[135354.203714] sd 5:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[135354.203717] I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[135354.203725] Buffer I/O error on dev sdc, logical block 0, async page read
[135354.204890] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[135354.204899] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
[135354.204903] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[135354.204907] sd 5:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[135354.204910] I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[135354.204917] Buffer I/O error on dev sdc, logical block 0, async page read
[135354.204938] ldm_validate_partition_table(): Disk read failed.
[135354.206081] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[135354.206089] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
[135354.206093] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[135354.206097] sd 5:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[135354.206100] I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[135354.206107] Buffer I/O error on dev sdc, logical block 0, async page read
[135354.207156] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[135354.207162] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
[135354.207165] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[135354.207169] sd 5:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[135354.207171] I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[135354.207176] Buffer I/O error on dev sdc, logical block 0, async page read
[135354.208088] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[135354.208097] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
[135354.208101] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[135354.208106] sd 5:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
[135354.208109] I/O error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[135354.208116] Buffer I/O error on dev sdc, logical block 0, async page read
[135354.208150] sdc: unable to read partition table
[135354.208234] sd 5:0:0:0: [sdc] Attached SCSI removable disk
[135354.270324] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[135354.270333] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
[135354.270337] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[135354.270341] sd 5:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 01 d6 bf 80 00 00 08 00
[135354.270344] I/O error, dev sdc, sector 30850944 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[135354.271525] sd 5:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[135354.271534] sd 5:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
[135354.271538] sd 5:0:0:0: [sdc] tag#0 Add. Sense: Medium not present
[135354.271542] sd 5:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 01 d6 bf 80 00 00 08 00
[135354.271545] I/O error, dev sdc, sector 30850944 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[135354.271553] Buffer I/O error on dev sdc, logical block 3856368, async page read
This is what it said after I plugged in the USB. I'm going to be honest here, I have no idea what most of this means. There's obviously some kind of error with the partition table, which I mentioned that GParted had an error occur during my attempt at formatting it. So I guess the next question is, how do I fix this? It is good to see that there may be hope, as dmesg apparently can detect it.
Offline
Offline
The multiple I/O errors suggest that the USB stick might be dead or dying.
With the stick plugged in please post the output of
lsblk -f /dev/sdc
wipefs /dev/sdc
If you have unplugged the stick check dmesg again after re-plugging it to make sure it is still assigned to /dev/sdc. Change the above commands if it is assigned to a different device node.
Offline
The multiple I/O errors suggest that the USB stick might be dead or dying.
With the stick plugged in please post the output of
lsblk -f /dev/sdc wipefs /dev/sdc
If you have unplugged the stick check dmesg again after re-plugging it to make sure it is still assigned to /dev/sdc. Change the above commands if it is assigned to a different device node.
[user@computer ~]$ sudo lsblk -f /dev/sdc
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sdc
[user@computer ~]$ sudo wipefs /dev/sdc
[user@computer ~]$
The second command didn't output anything.
Offline
So the device looks completely blank. I think it's probably dead.
What actually happens when you try to run
# fdisk /dev/sdc
Please post the exact output.
And don't use sudo unless you have to: https://en.wikipedia.org/wiki/Principle … _privilege
Offline
So the device looks completely blank. I think it's probably dead.
What actually happens when you try to run
# fdisk /dev/sdc
Please post the exact output.
And don't use sudo unless you have to: https://en.wikipedia.org/wiki/Principle … _privilege
I do have to use sudo, as I'm not using the root account.
This was the output of sudo fdisk /dev/sdc.
Welcome to fdisk (util-linux 2.38.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
fdisk: cannot open /dev/sdc: Input/output error
I'm guessing that there's probably no way to fix this.
Offline
You don't need sudo for the lsblk command. And yes, I think the USB stick is no more. It has ceased to be. It has expired and gone to meet it's maker. It's a stiff. Bereft of life. It rests in peace. Etc.
Offline
You don't need sudo for the lsblk command. And yes, I think the USB stick is no more. It has ceased to be. It has expired and gone to meet it's maker. It's a stiff. Bereft of life. It rests in peace. Etc.
Lmao, well, it happens. I guess I'll just have to go get another one. I have others, but I kinda wanted to use this specific one. A mild inconvenience. Anyways, I appreciate your time and insight. I definitely learned a few things from all of this. Have a nice day, and again, thank you. (:
Offline
Pages: 1