# Cannot Update Linux or Linux Headers, causes boot failure

**URL:** <https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532>\
**Category:** Kernel, boot, graphics & hardware\
**Created:** [April 22, 2025, 11:22am UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532 "2025-04-22T11:22:03Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![cactux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/cactux/32/134907_2.png) [@cactux](https://forum.endeavouros.com/u/cactux)\
**Post date:** [April 22, 2025, 3:08pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/21 "2025-04-22T15:08:52Z")

</div>

Use your live usb to chroot:

```auto
sudo mount /dev/nvme0n1p2 /mnt
sudo mount /dev/nvme0n1p1 /mnt/boot/efi
sudo arch-chroot /mnt

```

Inside chroot:

`pacman -Syu`

`grub-install --efi-directory=/boot/efi bootloader-id=endeavouros`

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

Reboot.

---

<div class="post-metadata">

**Author:** ![limemile](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/l/5f8ce5/32.png) [@limemile](https://forum.endeavouros.com/u/limemile)\
**Post date:** [April 22, 2025, 3:44pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/22 "2025-04-22T15:44:49Z")

</div>

I have tried something similar. I will give this another shot after work today.

---

<div class="post-metadata">

**Author:** ![cactux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/cactux/32/134907_2.png) [@cactux](https://forum.endeavouros.com/u/cactux)\
**Post date:** [April 22, 2025, 3:58pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/23 "2025-04-22T15:58:20Z")

</div>

> [@limemile](#):
>
> sudo dracut --force --regenerate-all

Also, note, if you are using Grub and dracut and when you need to rebuild your initrds you could use:`sudo dracut-rebuild`

---

<div class="post-metadata">

**Author:** ![keescase](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/keescase/32/114900_2.png) [@keescase](https://forum.endeavouros.com/u/keescase)\
**Post date:** [April 22, 2025, 4:28pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/24 "2025-04-22T16:28:21Z")

</div>

What I am curious about the way grub was updated , I thought you should always run

```auto
sudo grub-install 
sudo grub-mkconfig -o /boot/grub/grub.cfg

```

Now I saw that only the last command was used by the OP , could that have messed up the grub bootloader ?

---

<div class="post-metadata">

**Author:** ![dbarronoss](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/d/f4b2a3/32.png) [@dbarronoss](https://forum.endeavouros.com/u/dbarronoss)\
**Post date:** [April 22, 2025, 4:30pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/25 "2025-04-22T16:30:47Z")

</div>

As I understand it, unless first install or a new version of grub is published, you only need the 2nd.  
However, it doesn’t hurt to over write the bootloader unnecessarily.

---

<div class="post-metadata">

**Author:** ![cactux](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/cactux/32/134907_2.png) [@cactux](https://forum.endeavouros.com/u/cactux)\
**Post date:** [April 22, 2025, 4:50pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/26 "2025-04-22T16:50:48Z")

</div>

This may have to do or not with OP’s issue but at any rates the output of the` efibootmgr` shows that they lack the _default_ bootpath to bootloader’s efi binary

`\EFI\endeavouros\grubx64.efi`

They only have the _fallback_ bootpath (Boot0002)

`\EFI\BOOT\BOOTX64.EFI0000424f`

So as already mentioned, this may not be the issue but creating the default bootpath, trying to boot from that and if the issue still persists, this will help to eliminate the Grub’s bootloader as a potential issue.

---

<div class="post-metadata">

**Author:** ![keescase](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/keescase/32/114900_2.png) [@keescase](https://forum.endeavouros.com/u/keescase)\
**Post date:** [April 22, 2025, 5:00pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/27 "2025-04-22T17:00:12Z")

</div>

That is interesting if I would have adviced refind as bootloader no grub was needed right ?

[Previous page](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532.md?page=1)
