Interesting boot issue this morning

First off, hello all and thank you for this great distro!

So, I woke up this morning to a black screen. When I went to reboot, the PC booted directly into BIOS. Naturally, I checked the boot settings and found that no disks were detected. Performed a full power cycle (draining residual electricity from the motherboard) and then my Windows drive re-appeared and was able to boot, but EOS was still missing. I did install each separately and they both have their own boot partition. I’ve been running this same setup for months now without issue.

Booted into a live environment of EOS and found that the EFI folder was empty. Not sure what happened. Updates were applied last week and have rebooted several times since. I haven’t chroot’d into the system yet but will report back when I get home.

Just thought I’d share and maybe get some input from the community in the meantime.

1 Like

From your Live USB, run the following commands and post the output here. Hopefully this would give some clues about your setup to start troubleshooting.

sudo parted -l
efibootmgr
1 Like
[root@EndeavourOS /]# ls /efi/
[root@EndeavourOS /]# ls /boot/
amd-ucode.img            initramfs-6.9.0-pf1.img  
[root@EndeavourOS /]# parted -l
Model: Patriot Rage Pro (scsi)
Disk /dev/sda: 124GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size   Type     File system  Flags
 2      2688MB  2855MB  167MB  primary  fat16        esp


Model: SM961 NVMe SAMSUNG 1024GB (nvme)
Disk /dev/nvme0n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  106MB   105MB   fat32        EFI system partition          boot, esp, no_automount
 2      106MB   123MB   16.8MB               Microsoft reserved partition  msftres, no_automount
 3      123MB   1023GB  1023GB               Basic data partition          msftdata
 4      1023GB  1024GB  813MB   ntfs                                       hidden, diag, no_automount


Model: Samsung SSD 990 PRO with Heatsink 1TB (nvme)
Disk /dev/nvme1n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name         Flags
 1      2097kB  1051MB  1049MB  fat32                     boot, esp
 2      1051MB  1000GB  999GB                endeavouros


[root@EndeavourOS /]# efibootmgr
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0001,0002,0000
Boot0000  Windows Boot Manager  HD(1,GPT,aeef7036-0148-4d61-9471-9d2cbc378b6e,0x800,0x32000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000050100000010000000040000007fff0400
Boot0001* Windows Boot Manager  HD(1,GPT,7b87dc1f-7ec8-46b5-aac2-ae29783adc76,0x1000,0x1f4000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI0000424f
Boot0002* UEFI OS       HD(2,MBR,0x7498467c,0x501b60,0x4f800)/\EFI\BOOT\BOOTX64.EFI0000424f
[root@EndeavourOS /]# 

1 Like

I should have mentioned this is a systemd-boot install. I also have borg backups to restore from but figured we can give it a shot at fixing rather than just restoring for now.

From the output you have posted, it can be seen that the Linux Boot Manager ( systemd-boot EFI boot entry) is gone.

Also, your /efi looks to be empty. That is where systemd-boot’s booloader and configurations are stored. /efi harbors your kernel images and initramfs as well on an EnOS’ standard installation.

Something, to me a bit strange, that I see is that you have the initramfs of a custom (?) kernel in
/boot directory. What is that? Do you have other “standard” kernels installed, that is from the Arch’s repo?

By the way, the filesystem type for your endeavouros partition is not shown in the output. What filesystem are you using, Btrfs, EXT4?

If I were in a similar situation, I would chroot into the system, update it fully (pacman -Syu), reinstall the systemd-boot’s bootloader, bootctl install, and reinstall my kernels, regenerate initramfs and create boot entries: reinstall-kernels

2 Likes

Did you mount the EFI partition in the chroot? Otherwise, it will always be empty

2 Likes

Will give it a try, thanks for the tip!

It’s just very strange that all of a sudden this happened. Went to bed like any other night and woke up to a black screen and this issue.

Yeah, I’m running the linux-pf kernel, also EXT4 filesystem.

That did the trick, thanks so much!

Also, I did need to mount /efi and was able to see the entries again. Still baffled at the root cause of this.

1 Like

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