"grub_is_Shim_lock_enabled not found"

Support
21

It saddens to hear that. Unfortunately, short of a reinstall (which I would have done long ago, so kudos to you for your patience,) I have NO idea where to go from here.

1 Like
22

This is correct and certainly not a messed system.

Some UEFI firmwares require a bootable file at a known location before they will show UEFI NVRAM boot entries. If this is the case, grub-install will claim efibootmgr has added an entry to boot GRUB, however the entry will not show up in the VisualBIOS boot order selector. The solution is to install GRUB at the default/fallback boot path:
– GRUB - ArchWiki

1 Like
23

@linux-aarhus - thanks a lot - much appreciated! I will check out this section of the Arch Wiki a bit later & give it a go. Manjaro has been so stable on the whole over the last 10 years, that I haven’t learned that much! I will give it a try fixing this one. Thanks again, also for your involvement in the core team. More power to you all…

EDIT: I just tried the command listed in the Arch Wiki & received the following"

grub-install: error: failed to get canonical path of `esp’

Apparently I need to define esp in the grub-install line - I’m not sure how I get there…

Thanks, R

24

Hi again. I’m struggling to carry out the guidance on the Arch Wiki, under the “Default/fallback boot path” section.

It suggests the following 2 commands:

mv esp/EFI/grub esp/EFI/BOOT
mv esp/EFI/BOOT/grubx64.efi esp/EFI/BOOT/BOOTX64.EFI

I don’t think I’m defining the fallback boot path correctly. How do I find this out, for my machine?

I’m hoping I can fix this & avoid re-installing Manjaro. I appreciate any assistance forthcoming.

Thanks, Ruziel

25

Hi @ruziel,

Right at the top of the Wiki page it states:

Note: In the entire article esp denotes the mountpoint of the EFI system partition aka ESP.

The path for the efi parrtition cann be obained using:

grep efi /etc/fstab

Mine, as example:

$ grep efi /etc/fstab
UUID=D563-DAB7  /boot/efi       vfat    noatime,umask=0077      0       2

So, boot/efi is the path.

I daresay this would have been quicker…

26

Hi @Mirdarthos - thanks for your assistance, which I greatly appreciate.

The path on my machine is the same as yours - boot/efi

I am unsure what the full commands with the above path included, would be, for…

mv esp/EFI/grub esp/EFI/BOOT
mv esp/EFI/BOOT/grubx64.efi esp/EFI/BOOT/BOOTX64.EFI

Again, much appreciated! Reinstalling my OS would take several hours, as I have a lot of settings & I hope to avoid this.

Ruziel

PS it seems to be LUKS encryption causing all the issues with GRUB - this is the third breakage that I’ve had after an update. My desktop has been running smoothly for years & doesn’t have full disk encryption

27

The reason for the error is that you skipped that:

29

Hi @megavolt

When I try to chroot into my system, it says it cannot find a GRUB drive - ERROR: no Linux partitions detected.

I know that cannot be the case because I can log into my laptop if I boot using a live USB & select the boot loader from the stick.

Thanks for your help.

Ruziel

30

Hi @ruziel,

Please provide the entire formatted output.

31

Of course because of this:

So… decrypt, mount it manually and then chroot. So like that:

# <device> could be sda1 for example
sudo cryptsetup luksOpen /dev/<device> root # decrypt root partition
sudo mount /dev/mapper/root /mnt # mount decrypted root partition
sudo mount /dev/<device> /mnt/boot/efi/ # mount efi partition
sudo manjaro-chroot /mnt /usr/bin/bash # change root

Edit: Sorry, the whole topic seems to be misleading. So you can actually boot the local system? If so, then just reinstall grub on the booted system. No chroot is needed here, only if you use a live session (Manjaro Installation ISO).

So the efi entry on your UEFI boots bootx64.efi, but not grubx64.efi. I would just create a new efi entry on the booted system.

sudo efibootmgr --create --disk /dev/<device> --part <number> --label "Manjaro GRUB" --loader '\EFI\MANJARO\GRUBX64.EFI'

Example:
<device> → sda (SCSI DISK A)
<number> → 2 (partition number)

1 Like
32

The chroot was suggested by me, because I don’t know how to do it any other way, but you do @megavolt, so your advice is obviously better than mine.

:wink:

33

Thanks everyone, much appreciated. I eventually decided to reinstall without full disk encryption, as this is the third breakage I’ve had due to GRUB updates & LUKS. Hopefully this thread will be useful to others in future.

1 Like