I would like to be able to choose between an encrypted Arch and a clear Arch at boot.
Encrypted Arch’s /boot is on sda2
Clear Arch’s /boot is on sda4
I installed EOS Gnome on my laptop with this partitioning and it works great.
I tried to do the same on two intel NUC (replacing EOS Gnome by EOS Qtile due to hardware limitations).
On NUC A, the installation fails at the end during grub install (I opened a topic)
On NUC B, the installation doesn’t fail but grub only shows the clear EOS kernel (I uncommented #GRUB_DISABLE_OS_PROBER=false and did sudo grub-mkconfig -o /boot/grub/grub.cfg but it doesn’t solve the problem).
As far as I understand it, both EOS (clear and encrypted) are installed on both NUCs. So I would like to repair or reinstall grub (never tried to repair a grub before…).
I read that I should use grub-install, but I cannot find tutorials that apply to my specific partitioning (ie having a /boot partition apart from a / luks partition.
[guest@guest-NUC-107 ~]$ LANG=C sudo grub-mkconfig -o /boot/grub/grub.cfg
[sudo] password for guest:
Generating grub configuration file ...
Found background: /usr/share/endeavouros/splash.png
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-lts-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
done
[guest@guest-NUC-107 ~]$ LANG=C sudo grub-mkconfig -o /run/media/guest/f7ff9904-f5c8-4b57-80aa-294679f64e74/grub/grub.cfg
Generating grub configuration file ...
Found background: /usr/share/endeavouros/splash.png
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-lts-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
done
From NUC A I can only boot from Live USB. Shall I also run the command?
Are you running these from the encrypted or unencrypted install?
Is this the grub from the other install? You shouldn’t do this. You are overwriting the grub config for that install with the grub config for this install. This will basically break that install. You probably will need to chroot in and fix that.
No, there isn’t much to be done about NUC A until you resolve the firmware issue.
Also, you didn’t share the output of sudo efibootmgr
Firstly, even if I fully believe you when you say it is a serious issue, my GNU/Linux is too limited to understand why it is an issue.
Secondly I have no idea of how to solve this issue since I don’t understand it.
I entered the BIOS and tried to update it, but it didn’t work. There is an update option in the bios, but it needs the NUC to be connected. Yet when I try to connect the NUC through ethernet it doesn’t work (only WiFi works, and WiFi can’t be used at bios level)…
That’s something you have to point to your vendor’s documentation/support for help.
By experience, I would try to reset the BIOS, either following the user manual, or by removing power for a significant time.