[lug] Gparted doesn't recognize new USB drive

D. Stimits stimits at comcast.net
Fri Mar 12 13:09:39 MST 2021


...
> > question on what dmesg shows during USB insert.
> 
> [172200.686184] usb 2-4.3: new SuperSpeed Gen 1 USB device number 6 using
> xhci_hcd
> [172231.537318] usb 2-4.3: New USB device found, idVendor=13fe,
> idProduct=6300, bcdDevice= 1.00
> [172231.537323] usb 2-4.3: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [172231.539755] usb-storage 2-4.3:1.0: USB Mass Storage device detected
> [172231.540234] scsi host5: usb-storage 2-4.3:1.0
> [172232.562124] scsi 5:0:0:0: Direct-Access 2309 PRAM        1.00 PQ: 0
> ANSI: 0 CCS
> [172232.562996] sd 5:0:0:0: Attached scsi generic sg5 type 0
> [172232.581860] sd 5:0:0:0: [sde] Attached SCSI removable disk
> 
> Still seems odd that as root, gnome-disks and Gparted don't have the option
> to just go ahead and operate on the device. Unless eufi is what's actually
> getting in the way. But that seems at odds with using a fake MBR to protect
> a GPT scheme.
...

The above says the USB is working, the device uses the standard USB mass storage drivers. Currently it shows up as "/dev/sde". No errors.

You might check the result of:
lsblk -f /dev/sde

This should result in some rather generic listing of a mass storage device. The main reason to do this is to simply see if the device responds or is recognized beyond USB (USB is just a pipe, disk drivers do the real work).

If you use "sudo gdisk -l /dev/sde" to see what shows up (mostly to see if it has any error), what shows up?

If needed, I would then suggest ordinary use of gdisk to see if partitions can be created or deleted. Skip partition resizing applications at the start.

Then, if there is still a problem, you can zero out everything using dd and partition from a clean drive. Any previous content (which any partitioned drive has even if it has no content) would not interfere. Do keep in mind the device might actually have something wrong, but at this point you know the USB is working as expected, and the correct mass storage driver is also working.


More information about the LUG mailing list