I’m in a similar situation. If I understand @mladen’s suggestion correctly, running grub-install on the secondary disk will install a MBR/GPT grub boot image there, which will point straight back at the primary disk.
So, the problem is SeaBIOS is limited and wants to boot only /dev/sdx, but the OS and boot sector is all on /dev/sdy. If you run grub-install
sudo grub-install /dev/sdx (the new/secondary disk), then grub will configure a shim boot sector that points back at the /boot partition on /dev/sdy.
Is that right? Or was @mladen suggesting a full reinstall, to put the OS directly on whatever disk SeaBIOS expects?
I’m reluctant to run @mladen’s commands for a couple reasons:
- I’m using LUKS full disk encryption
- I’m using Qubes OS
The Qubes dom0 is LUKS, and so is the secondary drive. The secondary drive is mounted in the Librem’s internal SATA slot, but I essentially use it as an external “USB” drive. So it’s just one giant LUKS partition, literally nothing else on it.
So, I’m worried grub-install might overwrite my LUKS header. And/or, that Qubes dom0 needs grub-install to be run in a special/different way because it’s not running directly on the hardware (it’s running inside Xen hypervisor).
Anyone have answers to these questions?