Systemd-boot missing in boot menu

General system Kernel, boot, graphics & hardware
1

Hello,

I am using EndeavourOS on a dual boot system with Windows 11.

After starting my computer yesterday I noticed that the systemd-boot entry in the boot menu is completely missing.

I used an live ISO with EndeavourOS and arch-chroot to get into my original EndeavourOS installation.

bootctl does not show any issues and bootctl is-installed returns yes. However, when doing efibootmgr there’s no entry for systemd-boot / EndeavourOS listed.

I also tried using bootctl install and reinstall-kernels and these commands did not return any errors.

I also used the following guides / forum posts for help, yet the boot menu entry is still missing.

I have basically no experience on this field, so I’m a bit lost why the boot menu entry is disappearing out of nowhere and how to get it back.

2

What did you do on the computer before shutting it down?

3

Playing a game and browsing the web on windows.
I didn’t make any updates and there are no windows updates listed in the history.

4

do you have what is it fastboot enabled in Windows?

5

Fast boot, secure boot and CSM support are disabled in UEFI.

Fast startup is disabled in Windows control panel.

1 Like
6

Maybe you need to check the disk that you have EOS installed on. Maybe its in read only mode. not sure what could be going on without any logs.

7

Check what and how exactly? EOS is installed on the same disk as Windows.

8

Unfortunately I don’t us Windows nor do I have any clue as to what could have happened since you don’t really give us any information other than you were playing some games.

But this is what you last did in windows. What did you last do in EndeavourOS?

are you able to chroot into the existing system and post logs?
https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/

9

That’s why I’m here, to ask for help and what I need to do.

I’m not an expert and I don’t know what information or logs exactly are required here.
I’ve described everything I tried above.

As I mentioned in my initial post, I can use arch-chroot to get into my system.
If you can tell me what kind of logs are necessary I can definitely provide them.

10

maybe start with hardware/software.

describe what you were doing last on both windows and Endeavour. I know Windows updates are notorious for removing Linux boot entries from your boot partition one of the reason I never recommend dual booting. I know you stated that Windows history doesn’t show an update but how far back is the history? When did you last update windows? endeavourOS?

Hopefully someone who uses windows can chime in with some suggestions. Last time I ran a dual boot was before Windows 8 and even then that was on separate drives.

11

I have been having this kind of problems for years until I discovered this method:

  1. install refind
  2. install a 3rd Linux e.g. Debian using grub
  3. whenever refind (and systemd-boot) are missing an entry in BIOS, I go into Debian - always hangs around in BIOS - and remove/install refind
  4. refind finds EnOS systemd-boot

Very robust, quick and faily easy method.

1 Like
12

Not sure why you replied to me however I wouldn’t recommend this either ATM.

OP is on 1 disk and sharing between windows and linux. Something I would advice to change ASAP. I would look to get an external if I can’t put in another internal drive and just install EOS on it.

I would keep M$ on its own drive with its own bootloader.

Also OP is able to chroot and ran commands for Systemd boot but says it did nothing so I wonder if maybe Grub is installed instead?

13

Thank you.

rEFind is detecting systemd-boot and I’m able to boot into EOS.

However, after the boot process the signal is gone and the monitors stay black.

Also tried EOS Fallback but it’s giving me NVIDIA errors: “Flip event timeout on head 0” after reaching the target graphical interface.

1 Like
14

I guess, you have to re-install EnOS which might be the quickest way. Then, use

nvidia-inst -h

which is very good. I have choosen nouveau as it always works and has matured over the years. Just some ideas, no more.

15

Well, yes, while reinstalling is possible, I would like to access my current EOS installation, as it’s still there and worked before.

16

Sorry to reply by mistake to your message. Anything is possible but the question always is - for me only - what takes the least amount of time and the least amount of knowledge.

1 Like
17

since you can chroot into the system are you able to run and update?

18

Yes, I went through this but it is also about efficiency for me. That is why.

19

I did eos-update, or what do you mean exactly?

1 Like
20

when?