Boot Loader Fails to Set ESP after Windows and BIOS Update

DotSpy · September 22, 2024, 1:17pm

Hi everyone,

I recently encountered an issue where my boot loader seems to be overwrittenafter Windows and BIOS Update and I tried to restore it.
I did arch-chroot bootctl install && reinstall-kernels
but bootctl status returning:

System:
      Firmware: UEFI 2.80 (American Megatrends 5.27)
 Firmware Arch: x64
   Secure Boot: enabled (user)
  TPM2 Support: yes
  Measured UKI: no
  Boot into FW: supported

Current Boot Loader:
      Product: systemd-boot 256.1-1-arch-g34ba18b^
     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
               ✗ Boot loader sets ESP information
          ESP: n/a
         File: └─/EFI/BOOT/BOOTX64.EFI

Random Seed:
 System Token: set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /efi (/dev/disk/by-partuuid/99f7332f-9ddd-422b-a6ec-98cb73ae5a13)
         File: ├─/EFI/systemd/systemd-bootx64.efi (systemd-boot 256.6-1-arch)
               └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 256.6-1-arch)

Boot Loaders Listed in EFI Variables:
        Title: Windows Boot Manager
           ID: 0x0002
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/99f7332f-9ddd-422b-a6ec-98cb73ae5a13
         File: └─/EFI/Microsoft/Boot/bootmgfw.efi

        Title: Windows Boot Manager
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/ae62faf3-f273-4a66-b1c8-f0320f93871a
         File: └─/EFI/Microsoft/Boot/bootmgfw.efi

        Title: Linux Boot Manager
           ID: 0x0001
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/99f7332f-9ddd-422b-a6ec-98cb73ae5a13
         File: └─/EFI/systemd/systemd-bootx64.efi

Boot Loader Entries:
        $BOOT: /efi (/dev/disk/by-partuuid/99f7332f-9ddd-422b-a6ec-98cb73ae5a13)
        token: endeavouros

Default Boot Loader Entry:
         type: Boot Loader Specification Type #1 (.conf)
        title: EndeavourOS (6.10.10-arch1-1)
           id: f726af7fc73949069f13e16438f63b3b-6.10.10-arch1-1.conf
       source: /efi//loader/entries/f726af7fc73949069f13e16438f63b3b-6.10.10-arch1-1.conf
     sort-key: endeavouros-6.10.10-arch1-1
      version: 6.10.10-arch1-1
   machine-id: f726af7fc73949069f13e16438f63b3b
        linux: /efi//f726af7fc73949069f13e16438f63b3b/6.10.10-arch1-1/linux
       initrd: /efi//f726af7fc73949069f13e16438f63b3b/6.10.10-arch1-1/initrd
      options: nvme_load=YES nowatchdog rw root=UUID=23de90e5-0ca5-4a1d-b4a7-f84d90a43b11 resume=UUID=edd0abe5-b042-41d6-9f8b-4b439371f471 split_lock_detec>

mounting seems also correct:
sudo lsblk -f

NAME   FSTYPE   FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0  squashfs 4.0                                                         0   100% /run/archiso/airootfs
sda                                                                                  
├─sda1 vfat     FAT32            EC72-EA75                                           
├─sda2                                                                               
├─sda3 ntfs                      D622737D22736203                                    
└─sda4 ntfs                      1CD45847D4582574                                    
sdb                                                                                  
├─sdb1                                                                               
├─sdb2 swap     1                edd0abe5-b042-41d6-9f8b-4b439371f471                
├─sdb3 vfat     FAT32            20E9-12EC                             378.6M    24% /mnt/efi
└─sdb4 ext4     1.0              23de90e5-0ca5-4a1d-b4a7-f84d90a43b11  787.2G     7% /mnt

petsam · September 22, 2024, 6:10pm

Disable Secure Boot. It seems it is enabled.

DotSpy · September 22, 2024, 8:09pm

Thank you, I disabled secure boot but still getting:

System:
      Firmware: UEFI 2.80 (American Megatrends 5.27)
 Firmware Arch: x64
   Secure Boot: disabled
  TPM2 Support: yes
  Measured UKI: no
  Boot into FW: supported

Current Boot Loader:
      Product: systemd-boot 256.1-1-arch-g34ba18b^
     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
               ✗ Boot loader sets ESP information
          ESP: n/a
         File: └─/EFI/BOOT/BOOTX64.EFI

petsam · September 23, 2024, 2:58pm

What is the actual difficulty? Can your system boot or not?

The issue you claim to have is an information message about status, not an error.
If your system has some deficiency, please, describe it better, as I cannot understand the problem .

DotSpy · September 23, 2024, 3:28pm

Sorry,
I can not boot in and thought that it was initial problem.
After some additional investigation seems that BIOS messing with boot order. it getting overwritten every time I’m rebooting to:

[root@EndeavourOS /]# sudo efibootmgr
sudo: unable to find terminal name for device 136, 1
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0002,0000,0001
Boot0000* Windows Boot Manager  HD(1,GPT,ae62faf3-f273-4a66-b1c8-f0320f93871a,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000061000100000010000000040000007fff0400
Boot0001* Linux Boot Manager    HD(3,GPT,99f7332f-9ddd-422b-a6ec-98cb73ae5a13,0x1f48000,0xfa000)/\EFI\systemd\systemd-bootx64.efi
Boot0002* Windows Boot Manager  HD(3,GPT,99f7332f-9ddd-422b-a6ec-98cb73ae5a13,0x1f48000,0xfa000)/\EFI\Microsoft\Boot\bootmgfw.efi0000424f
Boot0003* UEFI:  USB, Partition 1       PciRoot(0x0)/Pci(0x14,0x0)/USB(5,0)/HD(1,MBR,0x3710a,0x800,0x1ca37c0)0000424f

even after I changing it via efibootmgr --bootorder 1,3,2,0000

petsam · September 23, 2024, 3:37pm

Use the BIOS Quick Boot Menu to choose your Linux system to boot into.
If it fails, post any error messages (even as an image). Then boot to USB installer and post more info from your installed system.

your /etc/fstab
PARTUUID of both ESP partitions
other

DotSpy · September 23, 2024, 4:11pm

Thanks for you reply,
After some digging into BIOS settings, I found root cause it was under /Settings/Boot/UEFI Hard Disk Drive BBS Priorities
Put Linux Boot Manager back into first place and now it works!
Seems that BIOS+Windows update introduced one more entry and placed it on the top.

system · September 25, 2024, 4:12pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.