After installing Qubes R4.1.0 on a new disk, the new disk is not recognized as bootable by my system’s BIOS.
troubleshooting guide gives specific instructions, but the files being referenced don’t exist.
The only thing in /boot is initramfs-*.img.
Is the documentation out of date for 4.1 or is this a known issue?
Perhaps these could help:
Hi, I installed Qubes successfully. After clicking the restart button and unplugging the USB drive-- even with the Hard Disk as the first boot option-- the computer only boots into BIOS. What am I doing wrong? I can’t find anything in the knowledge base about this. Please help give me a clue about what’s wrong!
Hardware: MSI - Click Bios 5
Z490-A PRO (MS-7C75)
BIOS Mode UEFI
I read the Installation guide about 3 times all the way through word for word. I have done everythin…
I’ve been trying to make a portable USB OS using Qubes with Whonix.
I’ve created a bootable installer media from the .iso using Rufus which boots and runs great. Following the “Installation Guide” on qubes’ site, I chose my 32 GB usb drive as location. The installer works well finishes the installation. However, when I try to boot from the later USB drive, it doesn’t show up in the bios. I’ve changed UEFI/ Legacy support but still no luck.
In the qube’s site UEFI Troubleshooting s…
Problem: Qubes OS entry disappeared from the boot menu.
I had installed Qubes concurrent with a Windows 10 installation and another Linux and the boot menu listed all 3. Everything worked fine. But one day I took out the drive, put in another and booted from that, and then put the original drive back in. From then on, the boot menu only had Windows and the other Linux, but Qubes OS had mysteriously disappeared. No software was installed during this time.
I was able to follow the ‘Installation …
Mounting the installation media on another system and running
find . | grep xen\.efi returns nothing, so the docs aren’t in alignment with 4.1.
are you using internal / external disk ?
if using internal, have you try recreate uefi entry ?
if external, try moving qubes folder (on efi partition) to boot folder (on efi partition)
This sounds like it would resolve the issue. I’m not very familiar with boot systems, though. Is there any documentation on what exactly I’m looking for and where I should put it?
The UEFI troubleshooting docs don’t align with what I’m seeing on the filesystem when I examine the system using recovery mode.
I’m also not sure what you mean by “internal”. The QubesOS installation I’m having trouble with is on an SSD connected via SATA, freshly installed from a USB that I flashed using
Internal mean, you are connected to your sata port from the motherboard, not usb / pcie.
when you boot from system recovery, and want to change something in the EFI partition, which mentioned in the UEFI troubleshooting, you should mount your /boot and /boot/efi partition first, as example :
$ mount /dev/xxx2 /mnt
$ mount /dev/xxx1 /mnt/efi
before mounting device, you should examine which drive and partition that hold /boot and /efi partition first by running
lsblk, /dev/xxx2 could be /dev/sda2 or /dev/sdb2 or /dev/nvme0n1p2, just make sure sda / sdb / nvme0n1 is the right drive.
maybe try run
efibootmgr -v first, have you found qubes os uefi entry there ?
Using a R4.1 USB in recovery mode, I see two block devices: my SSD and the installation media. The installation media is already mounted at
When I mount the SSD to
/mnt, I see that
/mnt/efi is empty.
/run/install/repo/EFI/BOOT, I see
BOOTX64.EFI, grub config and a directory called fonts.
efibootmgr -v lists the SSD by its device name but I don’t see anything for Qubes.
If you can take a pict, it could be helpful since you still ‘misunderstanding’.
a pict of :
efibootmgr -v and
ok so there’s no qubes entry there. try this :
efibootmgr -v -c -u -L "Qubes OS" -l /EFI/qubes/grubx64.efi -d /dev/sda -p 1
then reboot, see if it’s work.
After running that command and a reboot, the recovery media still boots and
efibootmgr -v lists the same thing as it did before. Is it that the motherboard is overwriting these changes on reboot?