Open zoof opened 4 years ago
It was recognized as memdisk which is wrong, it cannot find several files it needed.
I verified the file of the distro by https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu, it's ok. And I downloaded it via torrent, where is additional checksum.
Also, with "Startup Disk Creator" I made a bootable USB. But then I got many errors on installs of this version, couple times was message that are several corrupted files libnvidia*
there (Nvidia now included in Ubuntu's installer). Also, I tryed installs as minimal package, and as full case with the download updates... anyway errors.
Also I tryed updating from 19.04.
I did installs about dozen times, because also there breaks bootloader of my ssd.
There using Linux kernel 5.3, but it's no in Ubuntu repository yet (last 5.0 there), because It's raw.
So, IMHO I recommend to wait for fixes, it's too raw. At least the appearance of the kernel 5.3 in the Ubuntu repo. (Sorry, if I somewhere confused.)
If you're trying to boot on a UEFI system then by default you'll end up booting into Grub not Syslinux see here: http://multibootusb.org/page_faq/#does-multibootusb-support-efi-or-uefi-booting
Also mentioned in there point 3 "Some menu options specially available for syslinux does not have support under GRUB2". And this is the case, for me with 19.10, the Grub menu item translated from the Syslinux one doesn't work as it's trying to use the loopback from an uncompressed image of Ubuntu that MultiBootUSB should've done but didn't because it detected as "memdisk_iso".
To solve the problem for the time being you can just drop the Ubuntu ISOs into the directory "\multibootusb\iso". Then when you boot into Grub and select the "Scan iso directory" you'll get menu options for running those Ubuntu ISOs
And alternative would be to disable UEFI boot and return to using Legacy boot which should then boot into Syslinux instead which then runs the ISOs using a loopback and using the loopback configuration in the ISO.
If you're not going with the Legacy boot option then you might as well uninstall those Ubuntu images from the standard MultiBootUSB menu as they will be sitting around taking up extra space on the USB drive.
Thank you @conceptrat, copying the ISO to \multibootusb\iso and booting into grub worked for me!
Same problem with Kubuntu 19.10 iso file. Also http://liveusb.info/dotclear/ have similar problem, when try to install - I got the error, that this ISO image is not supported.
Which files are multibootusb check for understand, that this is not ramdisk?
@MurzNN I think this is the same matching issue of hash, ISO name and/or files inside the ISO.
I should also point out that booting from an ISO in the "multibootusb/iso" directory doesn't allow for having a "persistent" option. So my temporary solution is only good for testing out a "Live" distribution or installation as no changes (creation of files, updates of repositories, etc) will be there when you boot into it again.
I have the same issue with Kubuntu 19.10, seems like this application didn't get any updates for a while. Is there any good alternatives for this application, because all good alternatives works only on Windows.
Also broken for Debian Buster based live systems. Has multibootusb been abandoned?
After a second go with this software, I got the distros to install - but get errrors when trying to boot. One says file not found, the other says /dev/sr0 is empty. Copying the iso's to the iso folder does not help. They are not available from the boot menu.
Just copied the iso's to the iso folder and selected 'scan drive for isos" like the @conceptrat said, booted first time using Ubuntu 19.10 - no issues.
I tried that as well with a Zorin iso and a POP! iso. Can't remember the errors but didn't work.
I was able to edit the program to actually detect Ubuntu correctly and install correctly, but now it won't boot completely. I have not made a pull request yet as I am still trying to fix the bugs not allowing it to boot. If anyone wants to take a look and try to help me solve this you are more than welcome. The changes I have made are pushed to my fork of the project. Any help is greatly appreciated. Thanks! https://github.com/JTruj1ll0923/multibootusb
To everyone, perhaps @dcrobertson01 and @JTruj1ll0923, who is having issues after installing a distro from MultiBootUSB. I found, in my case installing Linux Mint 19.3 (Ubuntu 18.04), that installing after booting into the "live" portion of the distro and then installing resulted in the Grub boot configuration being incorrect resulting in a failure at boot because "file not found". After doing some searching in the Grub boot configuration in "/boot/grub/grub.cfg", I found that the installation had placed the "live" USB root UUID reference into the variable "GRUB_CMDLINE_LINUX=" in the default configuration for Grub in "/etc/default/grub" resulting in two definitions of "root=" and the incorrect one was last and therefore took precedence. This happens because when the Grub boot configuration "/boot/grub/grub.cfg" is built, it appends the correct reference to the root partition from the Grub variable "GRUB_CMDLINE_LINUX_DEFAULT" but then appends the incorrect reference to the "live" USB root in "GRUB_CMDLINE_LINUX" after that. I not 100% sure if this is an Ubuntu 18.04/Mint 19.3 "live" issue only as I haven't tried the later version of these yet. Or perhaps an issue with the version of Grub in use. The latter likely to mean that this could be an issue with any "live" distro install using that version of Grub.
To get this to boot temporarily you need to interupt the boot process by pressing either "Esc" or "Shift" immediately after the system reboots. This should show the Grub boot menu at which point you should be on the default menu option and press "e" to edit this menu options configuration. You can read about this for Ubuntu/Mint here [https://wiki.ubuntu.com/Kernel/KernelBootParameters].
Now when you get this edit screen look for the line starting with "linux /boot/vmlinuz-..." and on that line lok for "root=UUID=...". In my case there were two of these. Remove the second one of these completely.
So say the line looks like this:
linux /boot/vmlinuz-5.3.0-42-generic root=UUID=c1099117-2219-4f3d-af39-ba62fa5975b7 ro floppy.allowed_drive_mask=0 quiet splash **root=UUID=8b6d-ad21** $vt_handoff
then you'd remove the second one, in bold above, and it would look like this:
linux /boot/vmlinuz-5.3.0-42-generic root=UUID=c1099117-2219-4f3d-af39-ba62fa5975b7 ro floppy.allowed_drive_mask=0 quiet splash $vt_handoff
Then press Ctrl+X to boot with this change. If this boots correctly then follow the instructions at the bottom of the page "Permanently Add a Kernel Boot Parameter" in the link again [https://wiki.ubuntu.com/Kernel/KernelBootParameters]. Doing the same as above removing the extra "root=" from the Grub variable "GRUB_CMDLINE_LINUX".
Using the example from above:
GRUB_CMDLINE_LINUX="floppy.allowed_drive_mask=0 root=UUID=8b6d-ad21"
would become
GRUB_CMDLINE_LINUX="floppy.allowed_drive_mask=0"
Hope this helps. Apologies for the long post but I wanted to explain my other issue fully.
Hey @conceptrat thanks for that! I have not tried this yet, but I will look into it more later after work today. I was curious if you could take a look at installing 20.04 with my version and seeing if the same applies. If you can't I will get around to it soon, but that would help. Then it is just a matter of figuring out where to edit the install script.
20.04 still doesn't install on Multibootusb 9.2. distribution not supported.
multibootusb does not work for Ubuntu 19.10 and variants. For lubuntu 19.10, multibootusb warns that the ISO is not compatible. For Ubuntu 19.10, there is no warning but after installation, distro will not boot.