# Latest grub bricked my system (grub\_is\_shim\_lock\_enabled not found)

**URL:** <https://forum.endeavouros.com/t/latest-grub-bricked-my-system-grub-is-shim-lock-enabled-not-found/42879>\
**Category:** Newbie\
**Created:** [July 5, 2023, 8:34am UTC](https://forum.endeavouros.com/t/latest-grub-bricked-my-system-grub-is-shim-lock-enabled-not-found/42879 "2023-07-05T08:34:33Z")\
**Posts on this page:** 1\
**Showing post:** 112

<div class="post-metadata">

**Author:** ![Gamall](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/gamall/32/39459_2.png) [@Gamall](https://forum.endeavouros.com/u/Gamall)\
**Post date:** [July 8, 2023, 2:37pm UTC](https://forum.endeavouros.com/t/latest-grub-bricked-my-system-grub-is-shim-lock-enabled-not-found/42879/112 "2023-07-08T14:37:18Z")

</div>

> [@Kresimir](#):
>
> This was the hook that caused the legendary Grubbening of August 2022. 🤣

That was the one I was referring to; I linked the wrong stuff previously, I wanted the original breakage thread for r322 in august 2022:

> [@Full transparency on the GRUB issue - Updated 2022-08-29](https://forum.endeavouros.com/t/full-transparency-on-the-grub-issue-updated-2022-08-29/30784):
>
> [EOS-2-4K] Since the recent grub issue has impacted a lot of people, we wanted to provide full transparency based on the information we have so far. The situation with this package is still evolving and we will update this post with more information as it becomes available. The issue After updating to grub 2.06.r322 many users reported that their machines could fail to boot or booted directly into the BIOS or another OS. What caused the issue Starting with [this commit](https://git.savannah.gnu.org/cgit/grub.git/commit/?id=26031d3b101648352e4e427f04bf69d320088e77), grub introduced a ca…

> [@Kresimir](#):
>
> hook that ran `grub-mkconfig`

**I think I finally understood something:**

1° you’re talking about a hook that runs only mkconfig, while my own ran both grub-install and mkconfig.

2° The existence and role of that hook in the Great Grubbening of 22 was not mentioned as a cause of the problem in the thread, and so I developed a warped understanding of how grub works: I thought part of the grub package files passively played a role in the later phase of the boot, somehow:

> [@Full transparency on the GRUB issue - Updated 2022-08-29](https://forum.endeavouros.com/t/full-transparency-on-the-grub-issue-updated-2022-08-29/30784/130):
>
> When you update grub and/or call `grub-mkconfig` that updates only the userspace components.

So what was implied was “When you call `grub-mkconfig`, _whether manually or because the hook we set up on kernel update does that for you_, that updates only the userspace components.”  
Pinging @dalto for sanity check.

* * *

One last thing I want to check: are we agreed that there is no reason to run grub-mkconfig on kernel _updates_, only on install/removal of entirely new kernels (eg zen or something like that)? (Or of course upon modification of /etc/default/grub, or after a grub-install)

If that is the case, since I’ve all the kernels I need (vanilla, lts, zen) already, and I’m happy with my grub config and unlikely to tinker with it anymore, now that I’ve removed my -install + -mkconfig hook, I can basically ignore updates to the grub package entirely (until I want to tinker again, of course).

---

_[View the full topic](https://forum.endeavouros.com/t/latest-grub-bricked-my-system-grub-is-shim-lock-enabled-not-found/42879)._