When installing the GRUB version above, I got symbol grub_is_shim_lock_enabled not found
and can’t boot, so I downgraded back to grub-2:2.06.r566.g857af0e17-1-x86_64. I tried --disable-shim-lock
but it didn’t help. I don’t secure boot and don’t use TPM.
Package was pushed just 5 hours ago, anyone by chance ran into the same problem?
EDIT:
Tried again today, worked. Problem was likely caused because I installed GRUB into the “arch” NVRAM entry (esp/EFI/arch) instead of the Fallback which my board only supports (esp/EFI/BOOT). To do this add --removable
to grub-install. The full procedure is:
# grub-install --removable /dev/sdX ## or /dev/nvme0nX
# grub-mkconfig -o /boot/grub/grub.cfg
I find systemd-boot so much easier to use and it’s configuration is much smaller. So maybe consider to switch (if you are on UEFI).
I just upgraded and didn’t have any issues. I’m not experienced in this regard at all. But just to be sure, did you execute the following after the upgrade?
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi sudo grub-mkconfig -o /boot/grub/grub.cfg
Assuming of course your grub setup doesn’t differ from mine. These two commands are all I know about grub troubleshooting…
deleted by creator
Had the problem only on one machine. Do you have, by chance, a MSI motherboard? Can’t myself think of other causes and having the kernel and initrd on btrfs instead of ext4 can’t be the problem?
deleted by creator
Do you have GRUB installed into the ESPs fallback path? (esp/EFI/BOOT/BOOTX64.EFI) I haven’t tried
grub-install --removable
yet, but maybe stuff got confused.No, I only had grub in its default path. I’ve folded now though. Moved to systemd-boot. Works fine and config seems cleaner. Cannot recommend with just a few days of experience of course.