I’m getting ERROR: device 'UUID=' not found. Skipping fsck. when trying to boot onto bare metal from a USB drive installation of manjaro.
The drive is a persistent USB install created with alma-git from within a VM. It’s a bit of a long story but the tl;dr is that at the moment using a linux VM is the only way I’ve been able to create the USB installer.
I’m guessing the issue could be related to the VM using a different UUID for the volume: the UUID that the error refers to while attempting to boot to bare metal doesn’t match the actual UUID of the USB volume, according to the output of diskpart run on bare-metal windows 10. The usb-install boots properly when run from within a VM.
I’ve tried editing /etc/fstab to properly reflect the UUID of the USB volume that diskpart lists but I’m still seeing the error mentioning a different UUID when booting onto bare metal.
Bit of a mess, I know.
Any help greatly appreciated. Thanks in advance.
Thanks for your suggestion!
I added the correct UUID to grub.cfg, however now the same error appears but with what seems to be the correct UUID
The first image is the output of diskutil list, and the second image is of the machine attempting to boot from the USB drive. The UUID looks correct to me?
ALMA is not a known-working image writer for manjaro.
(or ‘persistent-usb-creator’ or whatever you might call it)
Please use any other method from ventoy to dd to verify.
I installed ventoy on the USB alongside the manjaro iso and booted it: I could get as far as grub but when I selected boot with open source / proprietary drivers the machine stuck on a black screen.
I also wrote the image to usb using DD and got to grub but again received the error about disk by-label not showing up after 30 seconds.
I have verified the SHA of the iso. I’m not sure how to verify with DD, if you could suggest a full command, or link to an explanation I would be happy to give it a shot. Unfortunately I was not able to find this information myself.