# Cannot Update Linux or Linux Headers, causes boot failure **URL:** \ **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:** 20\ **Page:** 1
**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, 11:22am UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/1 "2025-04-22T11:22:04Z")
I will provide any logs for those interested. If I update linux or linux-headers from pacman, I am put into recovery mode and the efi partition fails to mount. As soon as a downgrade back to my cached version that correctly booted, everything works fine. Please point me in the right direction. I have been researching and trying fixes for this problem for several months now. ---
**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, 11:34am UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/2 "2025-04-22T11:34:06Z")
Welcome to the forum :enos_flag: :enos: Do you get into the recovery mode during the update or does it finish before getting into recovery mode ? In the case of a partly update you will probably break the system. Because you are probably months behind on updates, think your best bet would be to backup all your important data, and do a fresh install if at all possible. ---
**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, 11:40am UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/3 "2025-04-22T11:40:18Z")
The update does complete and then I enter recovery mode on reboot. ---
**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, 11:48am UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/4 "2025-04-22T11:48:24Z")
Not saying I can help you here but by giving a bit more information about your system could make it possible for someone to help you out. Please put the output of the following command in the forum. ```auto sudo inxi -SMCGDmsxx --za ``` ---
**Author:** ![xircon](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/xircon/32/9124_2.png) [@xircon](https://forum.endeavouros.com/u/xircon)\ **Post date:** [April 22, 2025, 12:46pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/5 "2025-04-22T12:46:46Z")
How big is your EFI partition? ---
**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, 2:07pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/6 "2025-04-22T14:07:23Z")
> System: > Kernel: 6.13.6-arch1-1 arch: x86\_64 bits: 64 compiler: gcc v: 14.2.1 > Desktop: i3 v: 4.24 dm: LightDM Distro: EndeavourOS base: Arch Linux > Machine: > Type: Desktop Mobo: Gigabyte model: B650M GAMING PLUS WIFI v: x.x > serial: N/A UEFI: American Megatrends LLC. v: F33b date: 02/21/2025 > Memory: > System RAM: total: 64 GiB available: 61.92 GiB used: 9.17 GiB (14.8%) > Array-1: capacity: 128 GiB slots: 4 modules: 4 EC: None > max-module-size: 32 GiB note: est. > Device-1: Channel-A DIMM 0 type: DDR5 size: 16 GiB speed: 3600 MT/s > volts: 1.1 manufacturer: Micron part-no: CP16G60C36U5W.M8D1 > Device-2: Channel-A DIMM 1 type: DDR5 size: 16 GiB speed: 3600 MT/s > volts: 1.1 manufacturer: Crucial part-no: CP16G60C36U5W.M8D1 > Device-3: Channel-B DIMM 0 type: DDR5 size: 16 GiB speed: 3600 MT/s > volts: 1.1 manufacturer: Micron part-no: CP16G60C36U5W.M8D1 > Device-4: Channel-B DIMM 1 type: DDR5 size: 16 GiB speed: 3600 MT/s > volts: 1.1 manufacturer: Crucial part-no: CP16G60C36U5W.M8D1 > CPU: > Info: 8-core model: AMD Ryzen 7 7700X bits: 64 type: MT MCP arch: Zen 4 > rev: 2 cache: L1: 512 KiB L2: 8 MiB L3: 32 MiB > Speed (MHz): avg: 4790 min/max: 545/5573 boost: enabled cores: 1: 4790 > 2: 4790 3: 4790 4: 4790 5: 4790 6: 4790 7: 4790 8: 4790 9: 4790 10: 4790 > 11: 4790 12: 4790 13: 4790 14: 4790 15: 4790 16: 4790 bogomips: 143721 > Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4\_1 sse4\_2 sse4a ssse3 svm > Graphics: > Device-1: Advanced Micro Devices [AMD/ATI] Navi 48 [RX 9070/9070 XT] > vendor: ASUSTeK driver: amdgpu v: kernel pcie: speed: 32 GT/s lanes: 16 > ports: active: DP-3,HDMI-A-1 empty: DP-1,DP-2,Writeback-1 > bus-ID: 03:00.0 chip-ID: 1002:7550 > Device-2: Advanced Micro Devices [AMD/ATI] Raphael vendor: Gigabyte > driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 > ports: active: none empty: DP-4, DP-5, DP-6, HDMI-A-2, Writeback-2 > bus-ID: 12:00.0 chip-ID: 1002:164e temp: 33.0 C > Display: x11 server: [X.Org](http://X.Org) v: 21.1.16 compositor: Picom v: 12.5 driver: > X: loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa > dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 > Screen-1: 0 s-res: 5760x2160 s-dpi: 96 > Monitor-1: DP-3 mapped: DisplayPort-2 pos: bottom-r model: Acer KG273 X1 > res: N/A dpi: 82 diag: 686mm (27") > Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: primary,top-left > model: LG (GoldStar) HDR 4K res: 3840x2160 hz: 60 dpi: 163 > diag: 690mm (27.2") > API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 > drv: radeonsi device: 2 drv: swrast gbm: drv: radeonsi surfaceless: > drv: radeonsi x11: drv: radeonsi inactive: wayland > API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.0.4-arch1.1 > glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi > gfx1201 ACO DRM 3.61 6.13.6-arch1-1) device-ID: 1002:7550 > Info: Tools: api: eglinfo,glxinfo x11: xdpyinfo, xprop, xrandr > Drives: > Local Storage: total: 3.01 TiB used: 990.29 GiB (32.1%) > ID-1: /dev/nvme0n1 vendor: SanDisk model: SSD Plus 250GB A3N > size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 serial: temp: 45.9 C > ID-2: /dev/nvme1n1 vendor: Crucial model: CT1000P310SSD8 > size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 serial: temp: 44.9 C > ID-3: /dev/sda vendor: Inland model: SATA SSD size: 1.86 TiB > speed: 6.0 Gb/s serial: > ID-4: /dev/sdb vendor: SanDisk model: USB 3.2Gen1 size: 14.32 GiB > type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 serial: > Sensors: > System Temperatures: cpu: 36.8 C mobo: 31.0 C > Fan Speeds (rpm): N/A > GPU: device: amdgpu temp: 34.0 C device: amdgpu temp: 59.0 C mem: 76.0 C ---
**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, 2:08pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/7 "2025-04-22T14:08:00Z")
1 GiB ---
**Author:** ![xircon](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/xircon/32/9124_2.png) [@xircon](https://forum.endeavouros.com/u/xircon)\ **Post date:** [April 22, 2025, 2:12pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/8 "2025-04-22T14:12:48Z")
Apologies, I meant free space. ---
**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, 2:14pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/9 "2025-04-22T14:14:03Z")
960.5 MiB ![image](https://forum.endeavouros.com/uploads/default/original/3X/7/1/713b79a72a9793987c4a7603401da36fd9da998d.png) ---
**Author:** ![xircon](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/xircon/32/9124_2.png) [@xircon](https://forum.endeavouros.com/u/xircon)\ **Post date:** [April 22, 2025, 2:15pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/10 "2025-04-22T14:15:37Z")
So it is not an issue. ---
**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, 2:17pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/11 "2025-04-22T14:17:11Z")
I will throw this in here too: > System: > Firmware: n/a (n/a) > Firmware Arch: x64 > Secure Boot: disabled (setup) > TPM2 Support: yes > Measured UKI: no > Boot into FW: supported > > Current Boot Loader: > Product: GRUB 2.13 > Features: ✗ Boot counting > ✗ Menu timeout control > ✗ One-shot menu timeout control > ✗ Default entry control > ✗ One-shot entry control > ✗ Support for XBOOTLDR partition > ✗ Support for passing random seed to OS > ✗ Load drop-in drivers > ✗ Support Type #1 sort-key field > ✗ Support @saved pseudo-entry > ✗ Support Type #1 devicetree field > ✗ Enroll SecureBoot keys > ✗ Retain SHIM protocols > ✗ Menu can be disabled > ✗ Multi-Profile UKIs are supported > ✓ Boot loader set partition information > Partition: /dev/disk/by-partuuid/6ba4da0c-7a4f-4d09-9bb8-c3b3892531db > > Random Seed: > System Token: not set > Exists: no > > Available Boot Loaders on ESP: > ESP: /boot/efi (/dev/disk/by-partuuid/6ba4da0c-7a4f-4d09-9bb8-c3b3892531db) > File: └─/EFI/BOOT/bootx64.efi > > Boot Loaders Listed in EFI Variables: > Title: UEFI OS > ID: 0x0002 > Status: active, boot-order > Partition: /dev/disk/by-partuuid/6ba4da0c-7a4f-4d09-9bb8-c3b3892531db > File: └─/EFI/BOOT/BOOTX64.EFI > > ``` > Title: Windows Boot Manager > ID: 0x0000 > Status: active, boot-order > Partition: /dev/disk/by-partuuid/6ba4da0c-7a4f-4d09-9bb8-c3b3892531db > File: └─/EFI/Microsoft/Boot/bootmgfw.efi > > ``` > > Boot Loader Entries: > $BOOT: /boot/efi (/dev/disk/by-partuuid/6ba4da0c-7a4f-4d09-9bb8-c3b3892531db) > token: endeavouros > > 0 entries, no entry could be determined as default. ---
**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, 2:18pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/12 "2025-04-22T14:18:17Z")
I’ve also gone through this after updating to no avail: > sudo dracut --force --regenerate-all > sudo grub-mkconfig -o /boot/grub/grub.cfg ---
**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, 2:24pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/13 "2025-04-22T14:24:22Z")
Can you also post the contents of ```auto efibootmgr ``` ---
**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, 2:27pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/14 "2025-04-22T14:27:40Z")
> BootCurrent: 0002 > Timeout: 1 seconds > BootOrder: 0002,0000,0003 > Boot0000\* Windows Boot Manager HD(1,GPT,6ba4da0c-7a4f-4d09-9bb8-c3b3892531db,0x1000,0x200000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400 > Boot0002\* UEFI OS HD(1,GPT,6ba4da0c-7a4f-4d09-9bb8-c3b3892531db,0x1000,0x200000)/\EFI\BOOT\BOOTX64.EFI0000424f > Boot0003\* UEFI: USB SanDisk 3.2Gen11.00, Partition 1 PciRoot(0x0)/Pci(0x2,0x1)/Pci(0x0,0x0)/Pci(0xc,0x0)/Pci(0x0,0x0)/USB(8,0)/HD(1,GPT,34bf027a-8001-4b93-8243-1f9d3dce7de7,0x800,0x2f5000)0000424f ---
**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, 2:44pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/15 "2025-04-22T14:44:24Z")
Did you update Windows just before this all happened (if you still can remember this) , because there have been a number of users inhere that got there linux EFI bootloader whiped out by Windows. ---
**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, 2:46pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/16 "2025-04-22T14:46:51Z")
I’ve also seen a lot of BIOS updates as culprits too this last week. ---
**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, 2:51pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/17 "2025-04-22T14:51:37Z")
```auto sudo parted -l sudo blkid cat /etc/fstab ``` Use **```** before and after the text you post to format. ---
**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, 2:54pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/18 "2025-04-22T14:54:03Z")
I did not. The windows install is on a separate drive and it was created well after the issues started. ---
**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, 2:55pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/19 "2025-04-22T14:55:34Z")
No BIOS updates since I got the system. ---
**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, 2:57pm UTC](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532/20 "2025-04-22T14:57:44Z")
sudo parted -l ```auto Model: ATA Inland SATA SSD (scsi) Disk /dev/sda: 2048GB Sector size (logical/physical): 512B/512B Partition Table: loop Disk Flags: Number Start End Size File system Flags 1 0.00B 2048GB 2048GB ext4 Model: USB SanDisk 3.2Gen1 (scsi) Disk /dev/sdb: 15.4GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 1589MB 1588MB fat32 Tails boot, hidden, legacy_boot, esp, no_automount Model: SanDisk SSD Plus 250GB A3N (nvme) Disk /dev/nvme0n1: 250GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 2097kB 1076MB 1074MB fat32 EFI boot, esp 2 1076MB 241GB 240GB ext4 endeavouros 3 241GB 250GB 9449MB linux-swap(v1) swap Model: CT1000P310SSD8 (nvme) Disk /dev/nvme1n1: 1000GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 17.8MB 16.8MB Microsoft reserved partition msftres, no_automount 2 17.8MB 1000GB 1000GB ntfs Basic data partition msftdata, no_automount 3 1000GB 1000GB 673MB ntfs hidden, diag, no_automount ``` sudo blkid ```auto /dev/nvme0n1p1: UUID="4B97-6925" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI" PARTUUID="6ba4da0c-7a4f-4d09-9bb8-c3b3892531db" /dev/nvme0n1p2: LABEL="endeavouros" UUID="db2e2257-5270-45c0-b29e-d7071bafe0d6" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="endeavouros" PARTUUID="c4b405d8-a5c9-4b27-99e0-86cc36410f9c" /dev/nvme0n1p3: LABEL="swap" UUID="e84fc287-8913-4879-b566-3af13cdca73a" TYPE="swap" PARTUUID="f55ada40-a28e-4f41-badd-c40af9fcf6fb" /dev/nvme1n1p2: BLOCK_SIZE="512" UUID="42A07459A07454FF" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="218bc0f5-e7ca-447e-81f2-76acc2d510e1" /dev/nvme1n1p3: BLOCK_SIZE="512" UUID="6268619668616A2D" TYPE="ntfs" PARTUUID="0ec22727-5247-4f13-a7d9-d8ddea6fec5f" /dev/sda: UUID="59010661-a9de-45e0-a749-54a1845645ec" BLOCK_SIZE="4096" TYPE="ext4" /dev/sdb1: LABEL_FATBOOT="Tails" LABEL="TAILS" UUID="A690-20D2" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Tails" PARTUUID="34bf027a-8001-4b93-8243-1f9d3dce7de7" /dev/nvme1n1p1: PARTLABEL="Microsoft reserved partition" PARTUUID="137742c6-917a-4f8c-98f0-03d7c68ca8a5" ``` cat /etc/fstab ```auto # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a device; this may # be used with UUID= as a more robust way to name devices that works even if # disks are added and removed. See fstab(5). # # UUID=4B97-6925 /boot/efi vfat fmask=0137,dmask=0027 0 2 UUID=db2e2257-5270-45c0-b29e-d7071bafe0d6 / ext4 noatime 0 1 UUID=e84fc287-8913-4879-b566-3af13cdca73a swap swap defaults 0 0 tmpfs /tmp tmpfs noatime,mode=1777 0 0 UUID=59010661-a9de-45e0-a749-54a1845645ec /mnt/storage ext4 defaults,noatime,errors=remount-ro,nofail,rw,users,exec 0 0 ``` [Next page](https://forum.endeavouros.com/t/cannot-update-linux-or-linux-headers-causes-boot-failure/70532.md?page=2)