search

mbusb / multibootusb

Create multiboot live Linux on a USB disk...
http://multibootusb.org/
GNU General Public License v2.0
1.38k stars 199 forks source link

Unable to detect USB disk #265

Open marinmo opened 6 years ago

marinmo commented 6 years ago

Hello,

I'm running Fedora Workstation 27 and multibootusb doesn't seem to be able to recognize my USB-disk. The disk itself is formatted as vfat and located at /dev/sdc. Relevant logs (I believe);

[user@computer:/tmp]$ multibootusb-pkexec Running multibootusb version 9.1.0 from installed system... Starting multibootusb GUI... Cleaning old multibootusb directory... Syslinux exist in multibootusb directory... Using pyudev for detecting USB drives... /dev/sdb /dev/sdb1 /dev/sdd /dev/sdd1 /dev/sdd2 Selected device /dev/sdb Device /dev/sdb is a GPT disk... USB disk is not mounted and can't update list widget...

Where sdb/sdd are external harddrives. Relevant dmesg output from plugging in the USB-stick;

[610376.857551] usb 4-2: new SuperSpeed USB device number 8 using xhci_hcd [610376.870484] usb 4-2: New USB device found, idVendor=0951, idProduct=1666 [610376.870486] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [610376.870488] usb 4-2: Product: DataTraveler 3.0 [610376.870490] usb 4-2: Manufacturer: Kingston [610376.870501] usb 4-2: SerialNumber: 08606E6B64C4BE30733D543E [610376.871485] usb-storage 4-2:1.0: USB Mass Storage device detected [610376.871649] scsi host7: usb-storage 4-2:1.0 [610377.936626] scsi 7:0:0:0: Direct-Access Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6 [610377.937369] sd 7:0:0:0: Attached scsi generic sg3 type 0 [610377.937452] sd 7:0:0:0: [sdc] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB) [610377.938663] sd 7:0:0:0: [sdc] Write Protect is off [610377.938669] sd 7:0:0:0: [sdc] Mode Sense: 2b 80 00 08 [610377.939862] sd 7:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [610378.236401] sdc: [610378.239751] sd 7:0:0:0: [sdc] Attached SCSI removable disk

No idea why multibootusb doesn't recognize the drive, but I'm thinking pyudev?

marinmo commented 6 years ago

Also, checking "All drives" doesn't do anything but show my main harddrive (at sda), just for reference.

mbusb commented 6 years ago

It is really strange. I have not encountered such issue till date neither I could reproduce it now.

nobicycle commented 6 years ago

Hi this issue is present in my Manjaro Linux PC.

Linux linux.local 4.14.24-1-MANJARO #1 SMP PREEMPT Sun Mar 4 21:28:02 UTC 2018 x86_64 GNU/Linux

You will see below

However there is a UDB disk present: thunar

sudo pacman  -S python-pyqt5  p7zip parted mtools python-pyudev python-dbus python-six
warning: python-pyqt5-5.10.1-1 is up to date -- reinstalling
warning: p7zip-16.02-4 is up to date -- reinstalling
warning: parted-3.2-6 is up to date -- reinstalling
warning: mtools-4.0.18-4 is up to date -- reinstalling
warning: python-pyudev-0.21.0-2 is up to date -- reinstalling
warning: python-dbus-1.2.6-1 is up to date -- reinstalling
warning: python-six-1.11.0-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (7) mtools-4.0.18-4  p7zip-16.02-4  parted-3.2-6  python-dbus-1.2.6-1
             python-pyqt5-5.10.1-1  python-pyudev-0.21.0-2  python-six-1.11.0-1

Total Download Size:    0.23 MiB
Total Installed Size:  31.80 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
 mtools-4.0.18-4-x86_64   179.1 KiB   101K/s 00:02 [######################] 100%
 python-pyudev-0.21....    56.4 KiB   182K/s 00:00 [######################] 100%
(7/7) checking keys in keyring                     [######################] 100%
(7/7) checking package integrity                   [######################] 100%
(7/7) loading package files                        [######################] 100%
(7/7) checking for file conflicts                  [######################] 100%
(7/7) checking available disk space                [######################] 100%
:: Processing package changes...
(1/7) reinstalling python-pyqt5                    [######################] 100%
(2/7) reinstalling p7zip                           [######################] 100%
(3/7) reinstalling parted                          [######################] 100%
(4/7) reinstalling mtools                          [######################] 100%
(5/7) reinstalling python-pyudev                   [######################] 100%
(6/7) reinstalling python-dbus                     [######################] 100%
(7/7) reinstalling python-six                      [######################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating the info directory file...
[me@linux Videos]$ multibootusb
multibootusb         multibootusb-pkexec  
[me@linux Videos]$ sudo multibootusb
Running multibootusb version 9.1.0 from installed system...
Starting multibootusb GUI...
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Cleaning old multibootusb directory...
Syslinux exist in multibootusb directory...
Using pyudev for detecting USB drives...
No USB device found...
[me@linux Videos]$ sudo multibootusb -v
multibootusb version: 9.1.0
mbusb commented 6 years ago

what does lsblk show?

nobicycle commented 6 years ago

@mbusb Too late to check the lsblk cos multibootusb 9.1 was removed. However I cloned the repo and ran the app manually. All is fine.

leggewie commented 6 years ago

I believe I run into the same issue. Only my SSD at /dev/sda is detected when I tick "All Drives". lsblk shows the USB/microSD as

mmcblk0 179:0 0 956,5M 0 disk /media/leggewie/Ubuntu Inst

when in the internal SD card reader and as

sdb 8:16 1 956,5M 0 disk /media/leggewie/Ubuntu Inst

when mounted in an external USB reader. When starting the program there is an error of the form

"Could not find resource 'data/tools/gdisk/gdisk.exe'."

shown on the console.

shinji-s commented 6 years ago

Can you post the log file or the whole console output?

wredbeard commented 6 years ago

I had the exact same issue. Same console output.

I played around with GParted:

Mounted/Unmounted - didn't work. Reformatted - didn't work. Set new UUID - didn't work. Turned on boot flag - didn't work. Cleared partitions - didn't work. Ran disk check and repair - didn't work.

Just before I considered sticking the device in the microwave.

Set new device label - worked.

I set the device label with the Pop OS utility and nothing changed.

Setting the device label to "red" in GParted somehow worked though.

I'm going to guess it has something to do with pyudev and drive labels since the detect drives button showed the pyudev call in the console repeatedly returning that no USB device was found.

But I'm not sure. It's not my area of expertise. I hope this helps 😄

Alderin1974 commented 5 years ago

My USB drive is being excluded due to device.get('ID_PART_TABLE_TYPE') (in usb.py) returning 'NONE'. Once I traced it here, I used fdisk to create a new MBR and forced DOS mode, but the drive still shows 'NONE' for the PART_TABLE_TYPE from pyudev. This drive was detected before I reformatted it from exfat to fat32 (vfat).

Somehow, using fdisk and repeatedly wiping and re-creating the partition table, and formatting the partition to exfat and back to fat32 did finally get the drive to show up again. I am not sure what the point of eliminating devices with a missing Partition Table Type is, or if there is a better way to ensure the USB devices are valid drives, but I am guessing that this is the reason that so many USB drives get lost.

mzalazar commented 4 years ago

You need to have ONE VALID PARTITION in usb drive, otherwise it wouldn't be detected. Example: (look at /dev/sdc1, it's my usb device)

mzalazar@notebook-mz ~ $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 232,9G 0 disk ├─sda1 8:1 0 225,4G 0 part / └─sda2 8:2 0 7,5G 0 part [SWAP] sdb 8:16 0 465,8G 0 disk └─sdb1 8:17 0 465,8G 0 part /mnt/sdb1 sdc 8:32 1 29,1G 0 disk └─sdc1 8:33 1 29,1G 0 part

DougOliver12 commented 4 years ago

work for me

You need to have ONE VALID PARTITION in usb drive, otherwise it wouldn't be detected. Example: (look at /dev/sdc1, it's my usb device)

mzalazar@notebook-mz ~ $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 232,9G 0 disk ├─sda1 8:1 0 225,4G 0 part / └─sda2 8:2 0 7,5G 0 part [SWAP] sdb 8:16 0 465,8G 0 disk └─sdb1 8:17 0 465,8G 0 part /mnt/sdb1 sdc 8:32 1 29,1G 0 disk └─sdc1 8:33 1 29,1G 0 part

work for me!!!

vsarce commented 3 years ago

I had the exact same issue. Same console output.

I played around with GParted:

Mounted/Unmounted - didn't work. Reformatted - didn't work. Set new UUID - didn't work. Turned on boot flag - didn't work. Cleared partitions - didn't work. Ran disk check and repair - didn't work.

Just before I considered sticking the device in the microwave.

Set new device label - worked.

I set the device label with the Pop OS utility and nothing changed.

Setting the device label to "red" in GParted somehow worked though.

I'm going to guess it has something to do with pyudev and drive labels since the detect drives button showed the pyudev call in the console repeatedly returning that no USB device was found.

But I'm not sure. It's not my area of expertise. I hope this helps smile

yeah it s work for me .....thanks !!!

geek-merlin commented 3 years ago

I ran into this too. After quite some fiddling this worked for me:

(Side note: I don't grok why gparted did NOT ask me partition size and only allowed one full size partition for MBR...)