Qubes-OS in one SSD, and Linux in another SSD. Any problem?

[Eli]

I think I narrowed down the issue that we discussed earlier (I linked to the other posts below).

I installed Qubes-OS again on a separate NVMe. Once the installation was complete, I updated the Qubes. I restarted a few times, worked in it a bit, to make sure that it works (one issue: when I restarted, the white progress bar went to the end, but then a blank black screen showed up, it didn’t actually restart and the laptop had to be turned off by pressing the power button in each restart. But that might be a separate issue).

Then I entered the BIOS settings, changed the order of boot, and booted the other operating system, Linux. Once I restarted again, I couldn’t boot Qubes anymore. It ended up in the grub shell that I mentioned, in exactly the same state. Basically, any changes to the BIOS settings and saving them would make Qubes unbootable.

Any idea what might be the problem, and how to fix it?

Qubes 4.2-rc5 update did not generate the initramfs images in the system partition /EFI/qubes. Broken installation, I can’t boot anymore

It’s possible to restore the /boot partition but it’s not easy as you’ll need to format the /boot partition to ext4 again, mount all Qubes OS partitions for chroot, download the kernel package from Qubes OS repository, copy it to your Qubes OS root partition, chroot into it, change UUID of /boot partition in grub.conf in EFI partition, in fstab and maybe somewhere else and then reinstall the kernel package (it should install vmlinuz and regenerate initramfs with dracut and regenerate grub confi…

BIOS settings

I have used the Qubes installer with the default settings, and the partitions were created automatically. It looks like that the Qubes update did not generate initramfs images. As the problem has been better clarified and is not a Bios issue, I created a new post clarifying this issue here. Other users encountering this problem can better find it: