Systemd-Boot Repair

Hi. I am running a dual boot system configuration with EndeavourOS and Windows 11.

Unexpectedly, my EndeavourOS boot entry was erased recently and I am trying to restore it. Currently, on boot I only have the option to boot into Windows 11.

In an attempt to resolve the issue, I booted into a Live-USB and did the following:

sudo mount /dev/sda2 /mnt
sudo mount /dev/sda1 /mnt/efi
sudo arch-chroot /mnt
bootctl install

The last command seems to run, but I am advised that there is a security hole:

[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).

I tried rebooting here, but the entry still wasn’t present. So I repeated the steps, but this time also ran:

reinstall-kernels

This command doesn’t work, and the output (abbreviated) is:

[root@EndeavourOS /]# reinstall-kernels
Installing kernel 6.12.1-arch1-1
depmod: ERROR: failed to load symbols from /lib/modules/6.12.1-arch1-1/kernel/drivers/net/ethernet/broadcom/cnic.ko.zst: Invalid argument

So that’s where I am stuck at, I’m hoping reinstalling the kernel will restore EndeavourOS’ boot entry.
In an attempt to resolve the error, I also ran the following from the chroot:

[root@EndeavourOS /]# pacman -Q | grep -E "(grub|mkinitcpio|dracut)"
dracut 105-1
kernel-install-for-dracut 1.10.1-1

I feel like I’m not making any progress on resolving the issue, so any help is much appreciated.

Edit: The only thing I can currently think of is that maybe my Live-USB is outdated and that’s why I can’t perform the last action.

I found this on the arch wiki. Is this something you’ve tried?

https://bbs.archlinux.org/viewtopic.php?id=287790

I haven’t tried resolving that notice, but thanks for the reference on how to potentially resolve it. In the thread you linked, OP writes that systemd-boot still works with the notice and you can see that the command completes successfully for me as well. My problem is that there is no entry for EndeavourOS in systemd-boot.

Ah, sorry, i did not completely understand your problem then.