"Linux boot manager failed" after full system update. Cant even access BIOS

davidbegr · August 24, 2024, 9:29am

Hi, I tried looking through this forum but nothing was the exact same case as mine.
I am using dual boot with WIN10 and EndeavourOS, both at separate SSD drives.

As title says I updated my system (fair enough it was over a month since last update). Everything went fine. All packages installed and checked, nvidia drivers also, install kernel all good. It asked to be rebooted and after reboot I just saw error message from BIOS “Linux Boot Manager Failed” with only option “OK”. Then Windows 10 booted.

I didn’t yet tried arch-chroot because I was afraid something might go wrong. But I have the lsblk -f output which says it sees both my SSDs and flash drive. I also checked efibootmgr output here:

sudo efibootmgr
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0003,0005,2003,2002,2001
Boot0000* EFI PXE 0 for IPv4 (84-A9-38-A6-33-30)        PciRoot(0x0)/Pci(0x1d,0x6)/Pci(0x0,0x0)/)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0001* EFI PXE 0 for IPv6 (84-A9-38-A6-33-30)        PciRoot(0x0)/Pci(0x1d,0x6)/Pci(0x0,0x0))/IPv6([::]:<->[::]:,0,0)RC
Boot0002* EFI USB Device (USB)  UsbWwid(781,5595,0,0000230903302201101)/CDROM(1,0x4d5940,0x4ea98)RC
Boot0003* Windows Boot Manager  HD(1,GPT,75a5a2b2-e5af-4a12-a5b1-83a9b32367f4,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000061000100000010000000040000007fff0400
Boot0005* Windows Boot Manager  HD(1,GPT,659106a5-61b4-42b4-96a6-a00997e503dd,0x1000,0x1f4000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC

as i understand I dont currently have bootmanager for EOS? Systemd was always my default boot manager, but I dont see it here. Is there any solution?

Zesko · August 24, 2024, 1:17pm

It seems like the systemd boot manager was either removed or overwritten by the Windows Boot Manager, as you now have two Windows Boot Managers installed on two different partitions:

davidbegr:

Boot0003* Windows Boot Manager  HD(1,GPT,75a5a2b2-e5af-4a12-a5b1-83a9b32367f4,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)...
Boot0005* Windows Boot Manager  HD(1,GPT,659106a5-61b4-42b4-96a6-a00997e503dd,0x1000,0x1f4000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC

Unfortunately, the only solution is to use arch-chroot to reinstall systemd-boot manually, if you have a USB stick and your EOS system partition is ok.

davidbegr · August 24, 2024, 1:41pm

Okay I was hoping it will be straight-forward. Just follow the EOS Wiki arch-chroot and use bootctl install to reinstall it. BUT I got error bellow when using mount and now i afraid i need to format the drive:

sudo mount /dev/nvme0n1p2 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nvme0n1p2, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.

also so you can see i didn’t mess something up:

lsblk -f
NAME       FSTYPE   FSVER          LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0      squashfs 4.0                                                                   0   100% /run/archiso/airootfs
sda        iso9660  Joliet Extensi EOS_202401  2024-01-25-18-25-14-00                              
├─sda1     iso9660  Joliet Extensi EOS_202401  2024-01-25-18-25-14-00                     0   100% /run/archiso/bootmnt
└─sda2     vfat     FAT16          ARCHISO_EFI 8093-0377                                           
nvme0n1                                                                                            
├─nvme0n1p1
│          vfat     FAT32                      9EFA-648C                                           
├─nvme0n1p2
│                                                                                                  
├─nvme0n1p3
│          ntfs                                88280454280443A2                                    
├─nvme0n1p4
│          ntfs                                AEC4463FC4460A53                                    
└─nvme0n1p5
           ntfs                    MED         B25E82315E81EF03                                    
nvme1n1                                                                                            
├─nvme1n1p1
│          vfat     FAT32                      42C1-6649                                           
├─nvme1n1p2
│          ext4     1.0            endeavouros 0e283bad-35e7-4e3c-8355-47cb2a15481c                
└─nvme1n1p3
           swap     1              swap        9f2c04ec-8859-451e-a2e0-6c11c1d8dd1a

Zesko · August 24, 2024, 2:15pm

I guess you need to fix the partition nvme1n1p1, not nvme0n1p2.

Here are the steps to follow:

Mount your EOS system: sudo mount /dev/nvme1n1p2 /mnt
Mount the EFI system partition: sudo mount /dev/nvme1n1p1 /mnt/efi
sudo arch-chroot /mnt
Share the output of tree /efi. If you don’t have tree installed, you can install it manually.

davidbegr · August 24, 2024, 2:25pm

Sorry for that, I mistyped. I am in /mnt here is tree:

tree /efi
/efi
├── ac3c28d221b941aaad43299a77f1ddf6
│   └── 6.10.6-arch1-1
│       ├── initrd
│       ├── initrd-fallback
│       └── linux
├── EFI
│   ├── BOOT
│   ├── Linux
│   ├── Microsoft
│   │   ├── Boot
│   │   │   ├── BCD
│   │   │   ├── BCD.LOG
│   │   │   ├── BCD.LOG1
│   │   │   ├── BCD.LOG2
│   │   │   ├── bg-BG
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── bootmgfw.efi
│   │   │   ├── bootmgr.efi
│   │   │   ├── BOOTSTAT.DAT
│   │   │   ├── boot.stl
│   │   │   ├── cs-CZ
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── da-DK
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── de-DE
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── el-GR
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── en-GB
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── en-US
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── es-ES
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── es-MX
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── et-EE
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── fi-FI
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── Fonts
│   │   │   │   ├── chs_boot.ttf
│   │   │   │   ├── cht_boot.ttf
│   │   │   │   ├── jpn_boot.ttf
│   │   │   │   ├── kor_boot.ttf
│   │   │   │   ├── malgun_boot.ttf
│   │   │   │   ├── malgunn_boot.ttf
│   │   │   │   ├── meiryo_boot.ttf
│   │   │   │   ├── meiryon_boot.ttf
│   │   │   │   ├── msjh_boot.ttf
│   │   │   │   ├── msjhn_boot.ttf
│   │   │   │   ├── msyh_boot.ttf
│   │   │   │   ├── msyhn_boot.ttf
│   │   │   │   ├── segmono_boot.ttf
│   │   │   │   ├── segoen_slboot.ttf
│   │   │   │   ├── segoe_slboot.ttf
│   │   │   │   └── wgl4_boot.ttf
│   │   │   ├── fr-CA
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── fr-FR
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── hr-HR
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── hu-HU
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── it-IT
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── ja-JP
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── kd_02_10df.dll
│   │   │   ├── kd_02_10ec.dll
│   │   │   ├── kd_02_1137.dll
│   │   │   ├── kd_02_14e4.dll
│   │   │   ├── kd_02_15b3.dll
│   │   │   ├── kd_02_1969.dll
│   │   │   ├── kd_02_19a2.dll
│   │   │   ├── kd_02_1af4.dll
│   │   │   ├── kd_02_8086.dll
│   │   │   ├── kd_07_1415.dll
│   │   │   ├── kd_0C_8086.dll
│   │   │   ├── kdnet_uart16550.dll
│   │   │   ├── kdstub.dll
│   │   │   ├── ko-KR
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── lt-LT
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── lv-LV
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── memtest.efi
│   │   │   ├── nb-NO
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── nl-NL
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── pl-PL
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── pt-BR
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── pt-PT
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── qps-ploc
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── Resources
│   │   │   │   ├── bootres.dll
│   │   │   │   └── cs-CZ
│   │   │   │       └── bootres.dll.mui
│   │   │   ├── ro-RO
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── ru-RU
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── SecureBootRecovery.efi
│   │   │   ├── sk-SK
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── sl-SI
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── sr-Latn-RS
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── sv-SE
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── tr-TR
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   ├── uk-UA
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   └── bootmgr.efi.mui
│   │   │   ├── winsipolicy.p7b
│   │   │   ├── zh-CN
│   │   │   │   ├── bootmgfw.efi.mui
│   │   │   │   ├── bootmgr.efi.mui
│   │   │   │   └── memtest.efi.mui
│   │   │   └── zh-TW
│   │   │       ├── bootmgfw.efi.mui
│   │   │       ├── bootmgr.efi.mui
│   │   │       └── memtest.efi.mui
│   │   └── Recovery
│   │       ├── BCD
│   │       ├── BCD.LOG
│   │       ├── BCD.LOG1
│   │       └── BCD.LOG2
│   └── systemd
├── FOUND.000
│   ├── FILE0000.CHK
│   └── FILE0001.CHK
├── loader
│   ├── entries
│   │   ├── ac3c28d221b941aaad43299a77f1ddf6-6.10.6-arch1-1.conf
│   │   └── ac3c28d221b941aaad43299a77f1ddf6-6.10.6-arch1-1-fallback.conf
│   ├── entries.srel
│   ├── loader.conf
│   └── random-seed
└── System Volume Information

53 directories, 149 files

Should I now simply use bootctl install?

Zesko · August 24, 2024, 2:27pm

Yes, try that, then check efibootmgr

davidbegr · August 24, 2024, 2:36pm

bootctl install
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/BOOT/BOOTX64.EFI".
⚠ Mount point '/efi' which backs the random seed file is world accessible, which is a security hole! ⚠
⚠ Random seed file '/efi/loader/random-seed' is world accessible, which is a security hole! ⚠
Random seed file /efi/loader/random-seed successfully refreshed (32 bytes).
Created EFI boot entry "Linux Boot Manager".
[root@EndeavourOS /]# efibootmgr
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0004,0003,0005,2003,2002,2001
Boot0000* EFI PXE 0 for IPv4 (84-A9-38-A6-33-30)        PciRoot(0x0)/Pci(0x1d,0x6)/Pci(0x0,0x0)/MAC(84a938a63330,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)RC
Boot0001* EFI PXE 0 for IPv6 (84-A9-38-A6-33-30)        PciRoot(0x0)/Pci(0x1d,0x6)/Pci(0x0,0x0)/MAC(84a938a63330,0)/IPv6([::],0,Static,[::],[::],64)RC
Boot0002* EFI USB Device (USB)  UsbWwid(781,5595,0,0000230903302201101)/CDROM(1,0x4d5940,0x4ea98)RC
Boot0003* Windows Boot Manager  HD(1,GPT,75a5a2b2-e5af-4a12-a5b1-83a9b32367f4,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000061000100000010000000040000007fff0400
Boot0004* Linux Boot Manager    HD(1,GPT,659106a5-61b4-42b4-96a6-a00997e503dd,0x1000,0x1f4000)/\EFI\systemd\systemd-bootx64.efi
Boot0005* Windows Boot Manager  HD(1,GPT,659106a5-61b4-42b4-96a6-a00997e503dd,0x1000,0x1f4000)/\EFI\Microsoft\Boot\bootmgfw.efiRC
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC

I would say reboot and done?

Zesko · August 24, 2024, 2:38pm

Yes

davidbegr · August 24, 2024, 2:41pm

You are saviour thank you for your help and time. I saw all of boot options, was able to get to bios, linux boot manager was at top and I am on my old system. Thanks a lot

system · August 26, 2024, 2:42pm

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