Multiboot USB boots to GRUB CLI only, no menu #242
Comments
|
Here is yet another case, where we run into the problem that the GRUB cli is booted without displaying the menu:
With a little playing around (
Therefore, it seems like that grub can't find the USB pen, on which grub is installed (and thus cannot load its configuration files). The pen is a 123GB Verbatim USB 3.0 stick, formatted with msdos partition table and one FAT32 as a whole disk: Booting was performed using "F12" (temporary change of boot sequence). Booting the stick via legacy boot and jumping from syslinux to grub2 works fine (but does not imply that it the stick was booted using EFI, which is a problem in my case, as I want to able to install Win10 in UEFI mode). Ideas and suggestions welcome! |
|
On the very same machine, there is an Debian 8 installed, which runs on With a little of testing, I again come to the conlusion that
|
|
Yet another interesting aspect perhaps: Booting the USB stick again, I issued Moreover, |
|
And yet another observation.
|
|
@openprivacy also reports in #209 that he can got his issue with an USB 3.0 stick. |
|
I have created an overview wiki page for this entire topic, as apparently the issue is quite widespread. |
|
yes, for me it was usb3.0 both port and stick |
Thanks for the update - I have adjusted the overview wiki page accordingly. |
|
Hello, Similar problem here, but not exactly: I can boot normally on UEFI system if I run it on a USB 2.0 port, but I enter inside the menu if I run it from a USB 3.0 port. If I run it from the Usb 2.0, it hangs during something like 1mn, and then I can read: If I try "ls", in the Usb 3.0 case I've (after 1mn of hanging): So no idea why the usb key does not appear in the list for 3.0... Especially because when I installed grub by myself on my key before that it worked like a charm. |
|
@eaglerainbow issue occasionally self-fixed without any effort from my side. Graphical menu appears on boot, no CLI. All os images on pendrive (10+ images) seem to be working. Still using same pendrive with no changes since issue was occuring (no-name aliexpress usb2.0 chinese pendrive). And still not changed nor updated parrot os x64 (3.9 release) on lenovo netbook, same USB socket (it looks like 2.0 socket, not 3.0). Same pendrive being plugged in in another socket is not recognised as bootable media. |
|
@martinedelbrock Because I am suspecting the USB port, in which you boot the USB stick, just to be sure that I got it right what you said:
Are you sure that you booted via (U)EFI and not via MBR? |
|
To make things clear, if the grub2 drops you to shell then it means that it is unable to find the configuration file located at (usb0,gpt1)/multibootusb/grub.cfg. That is how the efi binary is compiled for UEFI booting. I am looking for the solution to load the configuration file by scanning all devices by enbedding configuration file in to grub2 binary. The link would be helpful for some on how to do it https://www.gnu.org/software/grub/manual/grub/html_node/Embedded-configuration.html. This require some time for me to test and pushing it back to repo. @eaglerainbow Thanks for the wiki. This will remind me of things to consider for the next commit. The possible workaround:- |
|
@mbusb Thought so already that the config file could not be loaded. In various locations, however, there are indications that the root cause for not being able to load the file seems to be that the entire drive (here: USB stick) cannot be found at all. So for my case, I manually checked all devices listed by @ALL users affected (esp. those mentioned on the wiki page): Please report back in which combination (USB2.0/USB3.0) of port and type of stick you are experiencing that issue. Please ensure that you are really using UEFI and do not boot using MBR/legacy booting. |
|
I'd like to add some more details on the "research", which I did on the hardware (mainly stuff, which I currently just have around me by chance):
Here are my test result:
NB: I did not investigate on the boot problems of the images - that seems to be yet another topic, which I expect is unrelated to the current discussion here. Here is what I make out of it:
@mbusb I would expect that your efforts you are proposing to take in #242 (comment) will solve my issue no. 3, but will leave my issue no. 2 unresolved. HTH! |
|
I have made a latest commit to devel to solve this issue. Tested by a user and it works fine. Can some one test and report back, so that I can prepare for new release. |
|
Will try to as soon as possible and provide feedback via this ticket here. |
|
If you confirm then I will release it by tomorrow.
…On 30-Dec-2017 1:19 AM, "eaglerainbow" ***@***.***> wrote:
Will try to as soon as possible and provide feedback via this ticket here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#242 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEC34PPz-TKNJ7mZTPhbprKWMXSFVHXPks5tFUJKgaJpZM4Q1LmB>
.
|
|
I am on it right now... However, I have to first create me a proper environment - otherwise the test will be for the toss 🤔 |
|
I currently struggle with when running some non-trivial variant like [Sorry for that noob-ish comment, but I am not familar with python at all] Update: Found #238. Trying to understand it, but it does not match to what i see... Python is 3.5.2 running on ubuntu:16.04.3 LTS |
|
Tossed now my initial environment and changed to the machine where I initially had installed multibootusb. I did a there. Afterwards I cloned your repository as of state 67f57a8, branch
Switching over to my Asus M5A97 LE, I plugged it into an USB 2.0 port:
In short: nope. Though it did not break anything major, it also did not solve neither issue 2 nor issue 3 for me. |
|
Humpf... Just saw that you were asking for a test on branch |
|
I wanted you to test devel branch not master.
…On 30-Dec-2017 2:42 AM, "eaglerainbow" ***@***.***> wrote:
Tossed now my initial environment and changed to the machine where I
initially had installed multibootusb. I did a
dpkg -r python3-multibootusb
there. Afterwards I cloned your repository as of state 67f57a8
<67f57a8>,
branch master and created a fresh USB3.0 installation using a single iso
image, plugging the stick into the USB3.0 port of the Lenovo L560:
- Grub again fell into shell mode
- ls <tab> still does not list the USB device
- Grub still is the old version 2.02~rc1
Switching over to my Asus M5A97 LE, I plugged it into an USB 2.0 port:
- Grub again fell into shell mode
- ls <tab> lists again that (usb1,gpt1) is there and there I can also
find the grub.cfg file at the place where I would expect it to be.
In short: nope. Though it did not break anything major, it also did not
solve neither issue 2 nor issue 3 for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#242 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEC34Iq8JRptO9BpB5gAoWChJOmWMmOXks5tFVXYgaJpZM4Q1LmB>
.
|
|
Status as of branch
Summary:
Based on that I am in favor of releasing the new version. |
|
@martinedelbrock You are the initial reported of this issue (I only "hijacked" it with the intention of contribution 😛 ). Version 9.0.0 is out. |
|
Is it somehow possible to upgrade the bootloader binaries on an existing stick? Or do I need to completely wipe it an start from the beginning? |
|
It is better to rename multibootusb and efi directory.
…On 04-Jan-2018 1:13 AM, "JanSchnacki" ***@***.***> wrote:
Is it somehow possible to upgrade the bootloader binaries on an existing
stick? Or do I need to completely wipe it an start from the beginning?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#242 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEC34IoRrKt9rVD6ZQ_wzByDZnBR--6Lks5tG9dygaJpZM4Q1LmB>
.
|
|
I have had the exact same problem, and just tried with the current devel branch, and it worked great. NOTE: For anyone else experiencing troubles even with lates devel branch, make sure you run it in a chroot or similar, or uninstalls the currently installed version of MultibootUSB. I couldn't understand why I would still get booted into GRUB 2.02~rc1 before I realized the downloaded devel branch would not use it's own mbr.bin, but rather use the one in /usr/share/multibootusb from the currently installed version. Suggestion for an easy way to help others not make the same mistake: make this clear in a warning message when running the version in devel branch. Although I am open for the idea that people more used to debugging things straight from git just assumes things like this happens if you have the same software already installed. |
|
The new version (9.1.0) fixed this issue. If anyone experience issue of similar sort may open new issue as it would allow me to narrow down to the latest version. |
OS: 4.13.0-kali1-amd64 #1 SMP Debian 4.13.13-1kali1 (2017-11-17) x86_64 GNU/Linux
MultiBootUsb linux version 8.9.0
64 gb alcor flash drive, prevously low-level formatted, checked for errors and formatted to fat32 single primary partition with boot flag
Issue: boots to GRUB command line, no menu
When checking inside program all works ok - menu shows up, but not working in real boot from usb
ls output:
(ahci0) (ahci0,gpt3) (ahci0,gpt2) (ahci0,gpt1) (proc)
syslinux.cfg:
The text was updated successfully, but these errors were encountered: