LinuxQuestions.org - Grub error: symbol ‘grub_is

- Manjaro (https://www.linuxquestions.org/questions/manjaro-119/)

- - Grub error: symbol ‘grub_is_lockdown’ after update (https://www.linuxquestions.org/questions/manjaro-119/grub-error-symbol-%91grub_is_lockdown%92-after-update-4175692341/)

Grub error: symbol ‘grub_is_lockdown’ after update

Hi there,

I hope I'm posting in the right section.

when booting my system goes into grub rescue mode with the message

Code:

error: symbol ‘grub_is_lockdown’ not found

What happened:
Recently I updated grub after reading this article: https://forum.manjaro.org/t/grub2-se...ommended/57280.
I’m using an EFI system so I followed the instructions in the corresponding section. No errors occurred so I went on to activate the os-prober because I have a dual boot system (Manjaro and Windows).

Now grub rescue mode shows up with the error message I mentioned above. I found this tutorial:
https://www.youtube.com/watch?v=QHe3-hF-Rdk

which I followed closely but when I enter

Code:

insmod normal

it only shows the same message:

Code:

normal error: symbol ‘grub_is_lockdown’ not found

I then tried the whole process of restoring grub (https://wiki.manjaro.org/index.php/G...Reinstall_GRUB). I don’t get any error messages and all seems fine but on reboot grub again goes into rescue mode with the same error message

Code:

error: symbol ‘grub_is_lockdown’ not found

I’m using manjaro on stable branch with the newest kernel. Both OSes are installed on the same drive (NVME-SSD). Can you help me? Is there any info I can provide you with to help troubleshooting?

Hi there,

seems like this issue doesn’t occur that often. I guess I’m in bad luck? Anyway, I managed some progress:

Using the newest live ISO I’m able to boot into my manjaro installation again. Now, when I

Code:

grub-mkconfig -o /boot/grub/grub.cfg

the output contains some images which wasn’t the case before:

Code:

Generating grub configuration file ...

Found theme: /usr/share/grub/themes/manjaro/theme.txt

Found linux image: /boot/vmlinuz-5.11-x86_64

Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.11-x86_64.img

Found initrd fallback image: /boot/initramfs-5.11-x86_64-fallback.img

Found linux image: /boot/vmlinuz-5.10-x86_64

Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img

Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img

Found linux image: /boot/vmlinuz-5.4-x86_64

Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.4-x86_64.img

Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img

Warning: os-prober will be executed to detect other bootable partitions.

It's output will be used to detect bootable binaries on them and create new boot entries.

Found Windows Boot Manager on /dev/nvme0n1p4@/efi/Microsoft/Boot/bootmgfw.efi

Adding boot menu entry for UEFI Firmware Settings ...

Found memtest86+ image: /boot/memtest86+/memtest.bin

/usr/bin/grub-probe: Warnung: Unbekannter Gerätetyp nvme0n1.

done

But at the end there is new warning:

Code:

/usr/bin/grub-probe: Warning: unknown device type nvme0n1.

(translated from German).

Now, when I try to boot manjaro from the disk I get the following output:

Code:

[FAILED] Failed to start Load Kernel Modules.

[FAILED] Failed to mount /boot/efi.

[DEPEND] Dependency failed for Local File Systems.

[FAILED] Failed to mount /mnt/Daten

The output of journalctl -xb is very long. If it really helps solving the issue I’ll happily post it.

“Daten” is a mount point where I mounted a partition from another drive where I simply store lots of data. When booting via live-ISO, it just mounts trouble-free. But the othere 3 messages make me feel like I srewed up even more :frowning: Any help would be greatly appreciated!

I also can tell again which kernel I’m on: it’s 5.11.6-1. Changing the kernel in grub doesn't change anything.