USB only boots Grub Minimal Bash-Like

[David-Lor]

I installed a few Linux and Windows ISOs on a USB with MultiBootUSB. When I boot the usb, I just get this screen:

Tried a second USB flash drive and installed just one ISO, and I'm getting the same screen,.

[openprivacy]

Same issue with me after:

• installing kali-linux-2017.2-amd64.iso to a
• USB 3.0 stick /dev/sdb3 that was
• zeroed out then formatted FAT32

System:    Host: truckin Kernel: 4.13.7-1-ARCH x86_64 bits: 64 Desktop: N/A Distro: Arch Linux
Machine:   Device: laptop System: LENOVO product: 20F9CTO1WW v: ThinkPad T460s serial: N/A
           Mobo: LENOVO model: 20F9CTO1WW v: SDK0J40697 WIN serial: N/A
           UEFI: LENOVO v: N1CET47W (1.15 ) date: 08/08/2016
Drives:    HDD Total Size: 1065.2GB (46.4% used)
           ID-1: /dev/sda model: Samsung_SSD_850 size: 1000.2GB
           ID-2: USB /dev/sdb model: STORE_N_GO size: 65.0GB

[openprivacy]

Hmmm... this is probably a duplicate of:

• UEFI Boot Fails grub prompt #186 (UEFI Boot Fails grub prompt)
• after boot from usb, just getting empty grub shell #165 (after boot from usb, just getting empty grub shell)

But I'm not seeing an answer that currently makes sense (other than a suggestion that perhaps I may have to change my BIOS, which I'd rather not do unless that is clearly the only way to resolve the issue).

[David-Lor]

Well, It seems it might be the problem. I was trying on a new laptop, but I can't disable UEFI on it D:

Anyway, tried on an old laptop I have lying around and it booted ok. So, yeah, seems like the problem is with the UEFI, sadly.

[TravisAbram]

Also experiencing this issues on HP and Dell, both with UEFI. Changing to Legacy Bios works, but is not ideal and requires a BitLocker key on our setups.

[mbusb]

Next version should support Uefi boot.

[prudx]

I have the same problem, also on a lenovo laptop. Not sure if that's anything to do with it. Changing to legacy works as a temp fix. Looking forward to next version :)

[mbusb]

Can you test again using devel version...

…

On 15-Nov-2017 4:08 AM, "Daniel" ***@***.***> wrote: I have the same problem, also on a lenovo laptop. Not sure if that's anything to do with it. Changing to legacy works as a temp fix. Looking forward to next version :) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#209 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEC34COmHYgQRWg8VxjuOxBN0wuZ17Yxks5s2hZ9gaJpZM4Pt32A> .

[laurent-indermuehle]

I've the same problem. So I tried the devel branch.
What I did:

• On Ubuntu 16.04.3 LTS I git cloned the repo.
• git checkout -b origin/devel
• sudo chmod +x ./install.py
• sudo ./install.py
  Everything goes fine, but when I run /usr/local/bin/multibootusb I got the error:

Traceback (most recent call last):
File "/usr/local/bin/multibootusb", line 164, in
if config.debug is True:
NameError: name 'config' is not defined

Is it the right way to test the devel version ?

[mbusb]

Looks like you have installed multibootusb under python2 environment and multibootusb does not support python2.

Instead of installing the source, directly run the program from source itself by using this command:-

cd /path/to/multibootusb/source/dir
sudo /usr/bin/python3 ./multibootusb

[mbusb]

@Honiix
Meanwhile, why don't you use the latest version 8.9.0. I just merged devel with master few days ago and released it to public.

[laurent-indermuehle]

@mbusb you're right, I should have thought about python 3.

I already tested the 8.9.0 and it gave me the grub prompt when trying to boot. I've tested so many things this morning that I can't give you a precise way to reproduce. As soon as I get the chance to test again, I'll get back here (probably thursday).

I've access to alot of laptops from HP and Lenovo. So if you need it, I can test many models with any configurations.

[mbusb]

If the bootable USB fails to load and shows grub shell, can you type 'ls' and post the output....

…

On 21-Nov-2017 3:49 AM, "Honiix" ***@***.***> wrote: @mbusb <https://github.com/mbusb> you're right, I should have thought about python 3. I already tested the 8.9.0 and it gave me the grub prompt when trying to boot. I've tested so many things this morning that I can't give you a precise way to reproduce. As soon as I get the chance to test again, I'll get back here (probably thursday). I've access to alot of laptops from HP and Lenovo. So if you need it, I can test many models with any configurations. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#209 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEC34MAFbrkwXCzxd2mVuXfx3MKDV9joks5s4fr8gaJpZM4Pt32A> .

[laurent-indermuehle]

To reproduce I have to set the Lenovo to "UEFI only". With or without CSM, in both case I land on the GNU GRUB version 2.02~rc1 minimal Bash.

ls return: (proc)

If I build the key on a Ubuntu and then I boot the key in BIOS LEGACY mode, I can boot on linux and windows images.
If I build the key from Windows and then I boot the key in BIOS LEGACY mode, I can only boot linux images. I'm unable to do more test from windows because 8.9.0 craches. I opened an other issue for this.

[nerijus]

I get (proc) too.

[ghost]

Same issue using 8.9.0 on Windows 10.
The uput of ls is:
(ahci1) (ahci1,gpt3) (ahci1,gpt2) (ahci1,gpt1) (ahci0) (ahci0,gpt3) (ahci0,gpt2) (ahci0,gpt1) (ahci2) (proc)

the (proc) appears after a few seconds and the promt seems to hang.

[mbusb]

Is your USB gpt?

…

On 04-Dec-2017 4:04 AM, "rsprooten" ***@***.***> wrote: Same issue using 8.9.0 on Windows 10. The uput of ls is: (ahci1) (ahci1,gpt3) (ahci1,gpt2) (ahci1,gpt1) (ahci0) (ahci0,gpt3) (ahci0,gpt2) (ahci0,gpt1) (ahci2) (proc) the (proc) appears after a few seconds and the promt seems to hang. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#209 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEC34EiF2x9h1op-XpAso0OEYCc5Buafks5s8yAhgaJpZM4Pt32A> .

[mbusb]

Made new release with latest efi binary. Please check and report if same issue persist.

[mbusb]

No one reported the same bug for a long time since last comment. Also, there has been many release with UEFI enhancement. Therefore I assume that the issue is solved.