Hi @barbour ,
Really no BIOS message? Or maybe, no UEFI boot entry for Qubes OS? Do you use UEFI? What is in your BIOS settings for the boot section?
If you got the “No bootable device” (or similar) BIOS message, look step #4 of this guide , with efibootmgr. Before using this command, please read its documentation, understand it and adjust the arguments to your case.
My use case: I cloned my SSD with clonezilla, changed it with the new clone, and got the unbootable message, the efibootmgr solved the issue.
Other related topics:
Yesterday, I had the same problem, except that the solution presented in the link here above (efibootmgr -v -c -L Qubes -l /EFI/qubes/xen.efi -d /dev/nvme0n1p1) did NOT work for me.
Instead, I got something like:
************************************************** ****
Warning! This MBR disk does not have a unique signature.
If this is not the first disk found by EFI, you may not be able
to boot from it without a unique signature.
Run efibootmgr with the -w flag to write a unique signature …
So during a troubleshoot of kernel and crashes I ran a 2nd Qubes innstalation to a USB disk.
After some testing I wanted to boot back to my main Qubes just to discover the boot entry was gone.
Did some searches and found that this should resolve it for me:
efibootmgr -v -c -L Qubes -l /EFI/qubes/xen.efi -d /dev/nvme0n1p1 (yup correct disk).
That indeed gives me the entry, but if I choose it Im thrown right in to bios.
Maybe the entry isnt correct for a 4.1 innstalation?
Hi everyone, need any help, because I am stuck.
Today I got my External SSD and I installed the 2-nd Qubes OS on this Drive (the first one was been installed on my internal Laptop drive.
But to my surprise, when I tried to load my first Qubes OS, I couldn’t. In BIOS my drive is visible like working device, but in Boot Menu it does not exist anymore.
So like in Manual - https://www.qubes-os.org/doc/uefi-troubleshooting/#accessing-installer-rescue-mode-on-uefi
I tried to go into the Rescue mod…
1 Like