My config is basically the same as posted by @petsam. When I boot, systemd starts services, then I get “Failed to Switch Root” on initrd-switch-root.service. I guess when it goes to unify the in-memory file-system with a mount from disk.
In the posted mbusb config (from OP and from hackerncoder/multibootusb’s example garuda config), I’m not sure where $imgdevpath is defined in the other mbusb grub config files. The project uses the same variable in the basic archlinux boot.
I can’t quite get some systems and linux distributions to boot from Grub via loopback (Guix, Garuda, OPNsense). I don’t need help with the others, only Garuda.
I’ve based my Multiboot USB on the original aguslr/multibootusb and i’ve had some success with VyOS, Fedora, Centos Stream, etc. I run into issues with the (loop) device for reasons unrelated to my issue at hand (some vars get mapped twice by agulsr/multibootusb)
The Guix issue is basically the same: the system begins to init, but can’t find the $cd_label device
The FreeBSD (OPNsense) issues are that it’s just weird (PF Sense boots afaik) and I don’t understand how it inits at all.
I do not really understand your questions and problem, sorry,
but just use ventoy.net, copy a live ISO and paste the live ISO on it, boot live ISO, install Garuda!
or repair existing Garuda, in welcome app use chroot, chroot to Garuda Linux, install-grub, update-grub, exit chroot, reboot your PC.
Or, booting multiple OS with custom.cfg.
Again, IDK what you want about aguslr/multibootusb
Maybe you can post garuda-inxi from live ISO and lsblk -f?
If you install as last OS Garuda, it shows and start other OS from grub.
That’s just how I’ve been doing it. I want to learn more about Boot processes & options, generally. Using aguslr/multibootusb helped to learn:
more about grub
that there are very different kernel boot options depending on the family of distributions
a bit about FreeBSD initialization
specific initialization styles (from Grub anyways): isolinux, loopback, chainloading, etc
Thanks for the suggestion to use Ventoy. I saw this, but I haven’t tried it yet. Maybe I can reverse eng. what Ventoy assembles.
If I start another image from Grub, this works where I’ve installed an image previously.
Another reason: I occasionally run into situations where I need to extract some information from /sys or /proc on a PC/Server (e.g. on FreeBSD) or where I just need a set of tools to do xyz. I manage my GPG/x509 on an airgapped USB image and I had to jump out to another distro to have access to commands to reset the hardware clock.
I guess Ventoy could do that, but I really want to be sure that only what I intended to run is what’s running (I guess I shouldn’t share that GPG USB image with other ISOs… lol).
