Latest grub bricked my system (grub_is_shim_lock_enabled not found)

from endeavourOS discovery guide

2 Likes

Seems you are correct that what I ran is the default when running ā€œgrub-installā€ Thanks for that link!
Because of running an Arch-based distribution, Iā€™m still used to looking it up in the Achwiki just to be sure :slight_smile:

Just curious, why Grub?!

I was on Grub for a while after the Grub problem happened for some time.
I believe that with the help and guidance of our friends here, I could make a ā€œhookā€ to automatically update/install Grub if there are any updates to be sure it wonā€™t ever break.

Here is the hook that fixes the issue (I called it grub_update.hook):

[Trigger]
Operation = Install
Operation = Upgrade

Type = Package
Target = grub

[Action]
Description = Re-generate Grub if Updated
When = PostTransaction
Depends = grub
Exec = /bin/sh -c "/usr/bin/grub-install && /usr/bin/grub-mkconfig -o /boot/grub/grub.cfg"

But I finally decided to convert to systemd-boot, and when I had a new fresh install on a new laptop I got a few months ago, EndeavourOS developers have decided to make the default systemd-boot, so I just followed the default.

I hope this helps.

Because systemd doesnā€™t have to do everything on my system :wink: But what advantage does systemd-boot give?

because iā€™m using btrfs with snapper and grub supports snapshots and is the recommended way to do it in the arch wiki and endeavour install (for btrfs)

1 Like

so i just updated grub again and passed the commands to try

grub-install --efi-directory=/boot/efi
grub-mkconfig -o /boot/grub/grub.cfg

the problem represented itself so this wonā€™t solve it at least for me

edit: downgraded grub again

Not sure then what it is.
It seemed to have done it on my end. At least after running that command the problem was gone.
We should wait and see if more reports on this will be coming in.

I forgot about this, thanks for reminding me that I have to install it.

Well, I have to admit it it that Grub seems to me to be more advanced and feature rich as compared to systemd-boot. Especially that you can boot from a previously working snapshot.

But why I chose systemd-boot despite this are a few reasons:
1- Grub, having this Grub update issue (as a matter of principle is not acceptable for me)
2- systemd-boot is just simpler, not affected by updates/upgrades to the system or sytemd-boot itself.
3- it boots much faster.
4- I didnā€™t even need to boot to a previous snapshot (my latest install on the new laptop like almost a year ago)

For me, it is simpler to manage, I donā€™t really care that any update might break the system.
It just works, and I feel much safer.

2 Likes

yeah i understand you. initially i wanted systemd for those reasons too.

1 Like

I looked if I could switch my system to systemd-boot but it seems you need a larger efi partition when using systemd-boot and I donā€™t really want to have to reinstall my whole system again after having setup everything just about a week ago.

I booted from a flash drive and used gparted to enlarge the efi partition.

1 Like

Did you have space left on your disk to grow your efi partition or was all the space used by other partitions?

Had to shrink my / partition but everything workedout fine.

Will give it i go then and see what happens.

2 Likes

Thatā€™s the spirit!

1 Like

If you see what I said is convincing I believe it is worth it to have a system that just works and just boots. (especially if you have only one OS).

This might be the answer to you issue.

If I were in your place, and found out how ā€œsafeā€ is systemd-boot I wont hesitate to make a fresh install. There is a thread here in the forum that explains how to convert from Grub to systemd-boot without the need to reinstall.

UPDATE: Here is the thread that the grand expert @dalto did some time ago. I used it myself and was amazing. [Tutorial] Convert to systemd-boot

this one?

1 Like

I havenā€™t had any issues with Grub ever, before I switched to EndeavourOS I was running Fedora. This last grub update didnā€™t even cause me trouble. Iā€™m willing to try something new :slight_smile:

Whatā€™s the recommended size for efi when using systemd-boot, I canā€™t find it anywhere. I remember it was something like 500M or better to make it 1G?

1 Like

Make it 1GB especially when you have a Nvidia card

2 Likes