Dual Boot went south (no more eOS šŸ˜­)

Hey

btrfs, luks, systemd-boot, dracutā€¦ dual-boot eOS/zindoz (well, I know, rightā€¦)

Following some shenanigans, I think windows kind of rebuilt the efi partition or something, well, anyway, I donā€™t have the multiboot option anymore, and cannot boot into eOS as it goes straight to zindoz.

So,

live iso

decrypt partition

then:

[liveuser@eos-2025.02.08 ~]$ sudo mount -o subvol=@ /dev/mapper/nvme0n1p5_crypt /mnt
[liveuser@eos-2025.02.08 ~]$ sudo mount /dev/nvme0n1p1 /mnt/efi
[liveuser@eos-2025.02.08 ~]$ sudo arch-chroot /mnt
[root@EndeavourOS /]# 

and

[root@EndeavourOS /]# 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).

but :

[root@EndeavourOS /]# cat /etc/fstab
# /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).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=3E8F-28DC                            /efi           vfat    fmask=0137,dmask=0027 0 2
/dev/mapper/luks-ca4c4be1-37fe-468a-9061-520dee85a95a /              btrfs   subvol=/@,noatime,compress=zstd 0 0
/dev/mapper/luks-ca4c4be1-37fe-468a-9061-520dee85a95a /home          btrfs   subvol=/@home,noatime,compress=zstd 0 0
/dev/mapper/luks-ca4c4be1-37fe-468a-9061-520dee85a95a /var/cache     btrfs   subvol=/@cache,noatime,compress=zstd 0 0
/dev/mapper/luks-ca4c4be1-37fe-468a-9061-520dee85a95a /var/log       btrfs   subvol=/@log,noatime,compress=zstd 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

fstab is ok no?
so I unmounted and remounted efi, with the permissions (shall I have done that?):

[root@EndeavourOS /]# umount /dev/nvme0n1p1
[root@EndeavourOS /]# mount -o fmask=0137,dmask=0027 /dev/nvme0n1p1 /efi
[root@EndeavourOS /]# 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".
Random seed file /efi/loader/random-seed successfully refreshed (32 bytes).

But no, that doesnā€™t change anything, still no boot menu or anything straight to zindoz, checked the bios, no way to make it boot on anything else, nothing shows-up but the windows boot manager on the nvme.

So, I did it again and reinstalled kernels (and rebuilt the initramfs if my understanding is correct) too, with:

[root@EndeavourOS /]# reinstall-kernels

but still no luckā€¦

What do I miss ?

This is normal. It is just related to how you mounted the EFI partition when building the chroot.

It is a warning, it doesnā€™t hurt anything.

Looks fine

What does efibootmgr show?

Perhaps the EFI order is wrong?

2 Likes
[liveuser@eos-2025.02.08 ~]$ efibootmgr
BootCurrent: 0018
Timeout: 1 seconds
BootOrder: 0016,0018,000D,000A,0017,000B
Boot000A  CD/DVD Drive  BBS(CDROM,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0300)0000474f00004e4fc300000008000000850048004c002d00440054002d00530054002000440056004400520041004d00200047005500440030004e000000050109000300000000010416008b12e85cec2cf040837280640e3dc85803007fff040002010c00d041030a0000000001010600001703120a000200ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce65a004b0048003100370043003300320033003200200039002000200020002000200020002000200000007fff04000000424f
Boot000B  Hard Drive    BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)0000474f00004e4fcd00000008000000910050004e005900200043005300330030003300300020003500300030004700420020005300530044000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001b01010600000003171000010000006479a749d05001597fff040001043e00ef47642dc93ba041ac194d51d01b4ce650004e0059003200310031003000320031003000330030003400300031003000350039004200310000007fff04000000424f
Boot000D  UEFI: Built-in EFI Shell      VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
Boot0016* Windows Boot Manager  HD(1,GPT,102bf430-dbb6-4f07-9ec9-4c46b3b6f51f,0x800,0x1f4000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI0000424f
Boot0017  USB KEY       BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0b00)0000474f00004e4fb500000008000000730053006f006e0079002000530074006f00720061006700650020004d006500640069006100200030003100300030000000050109000200000000010416008b12e85cec2cf040837280640e3dc8580b007fff040002010c00d041030a000000000101060000140305060003007fff040001043000ef47642dc93ba041ac194d51d01b4ce6350041003000390031003200320031003100370033003100310000007fff04000000424f
Boot0018* UEFI: Sony Storage Media 0100 PciRoot(0x0)/Pci(0x14,0x0)/USB(3,0)/CDROM(1,0x593ce0,0x16210)0000424f

What happens if you enter your BIOS boot menu and select ā€œHard Driveā€?

Remove the USB first.

1 Like

I did, in the bios I removed everything but the SSD, same, then I even physically removed the HDDs and everything that were there, andā€¦ sameā€¦

what if I erase whatā€™s inside efi and redo bootctl install and reinstall-kernels, I assume I wonā€™t be able to boot zindoz, for sure, but will it put eOS back on tracks?
(i dunno is it possible thereā€™s something in there from windoz that takes precedence over linux?)

does it look like it should ?

ls -alR /efi
[root@EndeavourOS /]# ls -alR /efi
/efi:
total 16
drwxr-x--- 5 root root 4096 Jan  1  1970 .
drwxr-xr-x 1 root root  128 Jan  5 17:26 ..
drwxr-x--- 4 root root 4096 Feb 20 12:09 83b590f185f2405ca239032d249de10c
drwxr-x--- 6 root root 4096 May 20  2024 EFI
drwxr-x--- 4 root root 4096 Feb 21 16:04 loader

/efi/83b590f185f2405ca239032d249de10c:
total 16
drwxr-x--- 4 root root 4096 Feb 20 12:09 .
drwxr-x--- 5 root root 4096 Jan  1  1970 ..
drwxr-x--- 2 root root 4096 Feb 21 16:04 6.12.15-1-lts
drwxr-x--- 2 root root 4096 Feb 21 16:04 6.13.3-arch1-1

/efi/83b590f185f2405ca239032d249de10c/6.12.15-1-lts:
total 93816
drwxr-x--- 2 root root     4096 Feb 21 16:04 .
drwxr-x--- 4 root root     4096 Feb 20 12:09 ..
-rw-r----- 1 root root 19057497 Feb 21 16:04 initrd
-rw-r----- 1 root root 63200816 Feb 21 16:04 initrd-fallback
-rw-r----- 1 root root 13795840 Feb 21 16:04 linux

/efi/83b590f185f2405ca239032d249de10c/6.13.3-arch1-1:
total 93772
drwxr-x--- 2 root root     4096 Feb 21 16:04 .
drwxr-x--- 4 root root     4096 Feb 20 12:09 ..
-rw-r----- 1 root root 19089078 Feb 21 16:04 initrd
-rw-r----- 1 root root 63041968 Feb 21 16:04 initrd-fallback
-rw-r----- 1 root root 13873664 Feb 21 16:04 linux

/efi/EFI:
total 24
drwxr-x--- 6 root root 4096 May 20  2024 .
drwxr-x--- 5 root root 4096 Jan  1  1970 ..
drwxr-x--- 2 root root 4096 Feb 21 16:04 BOOT
drwxr-x--- 2 root root 4096 May 20  2024 Linux
drwxr-x--- 4 root root 4096 May 20  2024 Microsoft
drwxr-x--- 2 root root 4096 Feb 21 16:04 systemd

/efi/EFI/BOOT:
total 132
drwxr-x--- 2 root root   4096 Feb 21 16:04 .
drwxr-x--- 6 root root   4096 May 20  2024 ..
-rw-r----- 1 root root 123904 Feb 13 20:09 BOOTX64.EFI

/efi/EFI/Linux:
total 8
drwxr-x--- 2 root root 4096 May 20  2024 .
drwxr-x--- 6 root root 4096 May 20  2024 ..

/efi/EFI/Microsoft:
total 20
drwxr-x---  4 root root 4096 May 20  2024 .
drwxr-x---  6 root root 4096 May 20  2024 ..
drwxr-x--- 38 root root 8192 May 20  2024 Boot
drwxr-x---  2 root root 4096 Jun 27  2024 Recovery

/efi/EFI/Microsoft/Boot:
total 6112
drwxr-x--- 38 root root    8192 May 20  2024 .
drwxr-x---  4 root root    4096 May 20  2024 ..
-rw-r-----  1 root root    8192 Feb 21 15:28 BCD
-rw-r-----  1 root root    8192 May 20  2024 BCD.LOG
drwxr-x---  2 root root    4096 May 19  2024 bg-BG
-rw-r-----  1 root root 1598968 Jan 28 13:15 bootmgfw.efi
-rw-r-----  1 root root 1582576 Jan 28 13:15 bootmgr.efi
-rw-r-----  1 root root   65536 Jan 28 14:26 BOOTSTAT.DAT
-rw-r-----  1 root root   11030 May 19  2024 boot.stl
drwxr-x---  2 root root    4096 May 19  2024 cs-CZ
drwxr-x---  2 root root    4096 May 19  2024 da-DK
drwxr-x---  2 root root    4096 May 19  2024 de-DE
drwxr-x---  2 root root    4096 May 19  2024 el-GR
drwxr-x---  2 root root    4096 May 19  2024 en-GB
drwxr-x---  2 root root    4096 May 19  2024 en-US
drwxr-x---  2 root root    4096 May 19  2024 es-ES
drwxr-x---  2 root root    4096 May 19  2024 es-MX
drwxr-x---  2 root root    4096 May 19  2024 et-EE
drwxr-x---  2 root root    4096 May 19  2024 fi-FI
drwxr-x---  2 root root    4096 May 19  2024 fr-CA
drwxr-x---  2 root root    4096 May 19  2024 fr-FR
drwxr-x---  2 root root    4096 May 19  2024 hr-HR
drwxr-x---  2 root root    4096 May 19  2024 hu-HU
drwxr-x---  2 root root    4096 May 19  2024 it-IT
drwxr-x---  2 root root    4096 May 19  2024 ja-JP
-rw-r-----  1 root root   32744 Nov 15  2023 kd_02_10df.dll
-rw-r-----  1 root root  380376 Nov 15  2023 kd_02_10ec.dll
-rw-r-----  1 root root   27624 Nov 15  2023 kd_02_1137.dll
-rw-r-----  1 root root  241112 Nov 15  2023 kd_02_14e4.dll
-rw-r-----  1 root root   45552 Nov 15  2023 kd_02_15b3.dll
-rw-r-----  1 root root   45544 Nov 15  2023 kd_02_1969.dll
-rw-r-----  1 root root   32728 Nov 15  2023 kd_02_19a2.dll
-rw-r-----  1 root root   21480 Nov 15  2023 kd_02_1af4.dll
-rw-r-----  1 root root  299496 Nov 15  2023 kd_02_8086.dll
-rw-r-----  1 root root   19936 Nov 15  2023 kd_07_1415.dll
-rw-r-----  1 root root   50144 Nov 15  2023 kd_0C_8086.dll
-rw-r-----  1 root root   18920 Nov 15  2023 kdnet_uart16550.dll
-rw-r-----  1 root root   28648 Nov 15  2023 kdstub.dll
drwxr-x---  2 root root    4096 May 19  2024 ko-KR
drwxr-x---  2 root root    4096 May 19  2024 lt-LT
drwxr-x---  2 root root    4096 May 19  2024 lv-LV
-rw-r-----  1 root root 1376240 Jan 28 13:15 memtest.efi
drwxr-x---  2 root root    4096 May 19  2024 nb-NO
drwxr-x---  2 root root    4096 May 19  2024 nl-NL
drwxr-x---  2 root root    4096 May 19  2024 pl-PL
drwxr-x---  2 root root    4096 May 19  2024 pt-BR
drwxr-x---  2 root root    4096 May 19  2024 pt-PT
drwxr-x---  2 root root    4096 Dec  7  2019 qps-ploc
drwxr-x---  2 root root    4096 May 19  2024 ro-RO
drwxr-x---  2 root root    4096 May 19  2024 ru-RU
-rw-r-----  1 root root  162192 Jan 28 13:15 SecureBootRecovery.efi
drwxr-x---  2 root root    4096 May 19  2024 sk-SK
drwxr-x---  2 root root    4096 May 19  2024 sl-SI
drwxr-x---  2 root root    4096 May 19  2024 sr-Latn-RS
drwxr-x---  2 root root    4096 May 19  2024 sv-SE
drwxr-x---  2 root root    4096 May 19  2024 tr-TR
drwxr-x---  2 root root    4096 May 19  2024 uk-UA
-rw-r-----  1 root root    9796 Dec  7  2019 winsipolicy.p7b
drwxr-x---  2 root root    4096 May 19  2024 zh-CN
drwxr-x---  2 root root    4096 May 19  2024 zh-TW

/efi/EFI/Microsoft/Boot/bg-BG:
total 180
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 82312 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 82304 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/cs-CZ:
total 220
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 81264 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 81392 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 45576 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/da-DK:
total 220
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 80240 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 80352 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 45584 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/de-DE:
total 228
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 84464 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 84464 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 46120 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/el-GR:
total 228
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 85368 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 85376 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 46600 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/en-GB:
total 172
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 78320 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 78304 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/en-US:
total 220
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 78320 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 78192 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 45072 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/es-ES:
total 228
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 82400 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 82304 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 45880 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/es-MX:
total 180
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 82296 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 82304 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/et-EE:
total 172
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 79232 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 79328 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/fi-FI:
total 220
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 81280 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 81280 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 45584 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/fr-CA:
total 180
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 83840 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 83952 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/fr-FR:
total 228
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 84352 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 84464 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 46096 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/hr-HR:
total 172
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 81272 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 81280 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/hu-HU:
total 228
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 84464 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 84448 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 46096 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/it-IT:
total 220
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 81800 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 81888 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 45584 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/ja-JP:
total 200
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 70512 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 70536 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 43016 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/ko-KR:
total 200
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 70008 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 70000 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 43024 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/lt-LT:
total 172
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 80256 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 80368 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/lv-LV:
total 172
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 80248 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 80240 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/nb-NO:
total 220
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 79752 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 79752 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 45584 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/nl-NL:
total 228
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 82400 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 82288 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 45368 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/pl-PL:
total 228
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 82808 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 82912 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 46096 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/pt-BR:
total 220
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 81272 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 81280 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 45584 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/pt-PT:
total 220
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 81288 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 81376 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 46096 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/qps-ploc:
total 68
drwxr-x---  2 root root  4096 Dec  7  2019 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 54072 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/ro-RO:
total 172
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 80864 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 80880 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/ru-RU:
total 216
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 81776 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 81888 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 44856 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/sk-SK:
total 172
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 81800 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 81888 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/sl-SI:
total 172
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 80768 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 80768 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/sr-Latn-RS:
total 172
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 81904 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 81776 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/sv-SE:
total 220
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 80760 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 80880 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 45072 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/tr-TR:
total 220
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 80240 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 80352 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 45584 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/uk-UA:
total 172
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 81784 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 81888 Jul 10  2024 bootmgr.efi.mui

/efi/EFI/Microsoft/Boot/zh-CN:
total 192
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 66016 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 65904 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 42512 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Boot/zh-TW:
total 192
drwxr-x---  2 root root  4096 May 19  2024 .
drwxr-x--- 38 root root  8192 May 20  2024 ..
-rw-r-----  1 root root 65904 Jul 10  2024 bootmgfw.efi.mui
-rw-r-----  1 root root 66016 Jul 10  2024 bootmgr.efi.mui
-rw-r-----  1 root root 42512 Dec  7  2019 memtest.efi.mui

/efi/EFI/Microsoft/Recovery:
total 8
drwxr-x--- 2 root root 4096 Jun 27  2024 .
drwxr-x--- 4 root root 4096 May 20  2024 ..

/efi/EFI/systemd:
total 132
drwxr-x--- 2 root root   4096 Feb 21 16:04 .
drwxr-x--- 6 root root   4096 May 20  2024 ..
-rw-r----- 1 root root 123904 Feb 13 20:09 systemd-bootx64.efi

/efi/loader:
total 28
drwxr-x--- 4 root root 4096 Feb 21 16:04 .
drwxr-x--- 5 root root 4096 Jan  1  1970 ..
drwxr-x--- 2 root root 4096 Feb 20 12:09 entries
-rw-r----- 1 root root    6 May 20  2024 entries.srel
drwxr-x--- 2 root root 4096 Feb 20 23:10 keys
-rw-r----- 1 root root   63 May 22  2024 loader.conf
-rw-r----- 1 root root   32 Feb 21 16:04 random-seed

/efi/loader/entries:
total 24
drwxr-x--- 2 root root 4096 Feb 20 12:09 .
drwxr-x--- 4 root root 4096 Feb 21 16:04 ..
-rw-r----- 1 root root  644 Feb 21 16:04 83b590f185f2405ca239032d249de10c-6.12.15-1-lts.conf
-rw-r----- 1 root root  684 Feb 21 16:04 83b590f185f2405ca239032d249de10c-6.12.15-1-lts-fallback.conf
-rw-r----- 1 root root  648 Feb 21 16:04 83b590f185f2405ca239032d249de10c-6.13.3-arch1-1.conf
-rw-r----- 1 root root  688 Feb 21 16:04 83b590f185f2405ca239032d249de10c-6.13.3-arch1-1-fallback.conf

/efi/loader/keys:
total 8
drwxr-x--- 2 root root 4096 Feb 20 23:10 .
drwxr-x--- 4 root root 4096 Feb 21 16:04 ..

idk itā€™s my first real time using systemd-boot and dracut

It all looks fine.

The issue is with your BIOS/firmware.

You are not only missing the entry for the ā€œLinux Boot Managerā€ but you are also missing the entry for fallback/default entry. That is abnormal.

Is it possible you deleted something in the BIOS you should not have?

Also, have you confirmed that secureboot is still disabled?

1 Like

yes I did confirm secureboot disabled, fastboot too.

Iā€™m not sure I understand ā€œdeleted something in the BIOSā€

in the result of efibootmgr you mean ?

what ā€œcontrolsā€ that ?

Following just because this sounds like a situation I will be in shortly. Sounds broke enough to qualify.

1 Like

The Op stated that he thinks a Windows update is the culprit for this. Could have Windows deleted the bios entry? I have to admit I would not be surprised if they did but I didnā€™t think they changed anything in the bios on an Update.

1 Like

Thatā€™s very possible. This same situation happened to me as well. I decided to leave my Windows drive unplugged from the computer until I absolutely have to boot into it.

2 Likes

It is possible that Windows deleted the entry but running bootctl install would have re-added it.

Also, I have never seen Windows delete the fallback entry. I donā€™t think it would do that.

2 Likes

as far as I know nothing was changed in the bios indeed, neither by me nor by zindoz.
(and it is an old motherboard with no bios update anymore)
I did review extensively all the bios parameters, looks fine to me

why did it not, if I may ask :grimacing:

2 distinct drives is definitely a good idea :sweat_smile:

Thereā€™s a first time for everything? :sweat_smile:

2 Likes

Yeah I forgot he said he ran bootctl install after. I was just thinking about MSā€™s access for their Update. Glad I no longer have this headache.

2 Likes

It generally indicates a firmware/BIOS issue.

1 Like

I ā€œerasedā€ /efi, so nothing shows up in bios of course (and I mean I say ā€œbiosā€ from the beginning but itā€™s UEFI mode, right), wonderful, and went back to liveOS,
reinstall-kernels bootctl install
and then when I reboot a menu shows upā€¦ with only one entry ----> reboot to firmwareā€¦

You need to run reinstall-kernels after bootctl install

1 Like

No the contrary I think, kernels ā†’ bootctl

is that why?

andā€¦

when I look in /efi initframs arenā€™t there, and there is a /boot directory on my / partition with 2 images (shouldnā€™t it be 4 btw if I have linux kernel + lts if you add the fallback ?) next to intel-microcode.

i.e. thatā€™s not there anymore

Do I mess up when I mount the partitions before I chroot ?

Maybe, but it also could be because you ran reinstall-kernels first. That is definitely not the correct order.

Try re-running it.

Also, make sure you are mounting the Linux EFI partition and not the Windows one.

1 Like