Can't boot endeavourOS from systemd after update

General system Newbie
1

I ran an update today and on restarting my install is no longer discoverable in my Systemd boot menu. My 2 options are booting to windows or resetting to bios.

Current Fstab

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=55ED-7580                            /efi           vfat    fmask=0137,dmask=0027 0 2
UUID=0ec078e3-2a7b-44fa-8ae3-2cbbca577aa4 /              ext4    noatime    0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
UUID=bed3b042-df50-4947-ba03-77c98dc6b096	/run/media/kenny/Wilson	ext4	nofail,x-systemd.device-timeout=15	0	2
UUID=6d5b434d-903c-4f02-b960-46ba608e65e0	/run/media/kenny/MegaDisk	ext4	nofail,x-systemd.device-timeout=15	0	2

output of efibootmgr

# efibootmgr
BootCurrent: 0008
Timeout: 1 seconds
BootOrder: 0000,0001,0007,0008
Boot0000* Linux Boot Manager    HD(1,GPT,9cfb03af-bc34-4e14-9df3-2685aee47da1,0x1000,0x400000)/\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI
Boot0001* Windows Boot Manager  HD(2,GPT,881f33b3-1a2c-426d-8e5c-e46289c1cd5b,0xfa000,0x31800)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000064000100000010000000040000007fff0400
Boot0007* Windows Boot Manager  HD(1,GPT,9cfb03af-bc34-4e14-9df3-2685aee47da1,0x1000,0x400000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI0000424f
Boot0008* UEFI: VendorC ProductCode 3.20, Partition 1   PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/USB(2,0)/HD(1,MBR,0x45763,0x800,0x752f7c0)0000424f

fdisk -l output

# fdisk -l
Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C58D80A9-0DDD-43B1-B2D0-31A7DE69DFC2

Device       Start        End    Sectors  Size Type
/dev/sda1     4096    4198399    4194304    2G EFI System
/dev/sda2  4198400 3907029101 3902830702  1.8T Linux filesystem


Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdc: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xddc460dc

Device     Boot Start        End    Sectors  Size Id Type
/dev/sdc1        2048 3907028991 3907026944  1.8T  7 HPFS/NTFS/exFAT


Disk /dev/sdd: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sde: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: SanDisk SD6SB2M-
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 764B9F47-FD52-4477-9A4E-87B78659A19D

Device         Start        End   Sectors   Size Type
/dev/sde1       2048    1023999   1021952   499M Windows recovery environment
/dev/sde2    1024000    1226751    202752    99M EFI System
/dev/sde3    1226752    1259519     32768    16M Microsoft reserved
/dev/sde4    1259520  998492159 997232640 475.5G Microsoft basic data
/dev/sde5  998492160 1000212479   1720320   840M Windows recovery environment


Disk /dev/sdf: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: MB2000GCWDA     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4DBE1279-A8B6-40B0-A005-B4B35852B827

Device     Start        End    Sectors  Size Type
/dev/sdf1     34      32767      32734   16M Microsoft reserved
/dev/sdf2  32768 3907026943 3906994176  1.8T Microsoft basic data


Disk /dev/sdg: 58.59 GiB, 62914560000 bytes, 122880000 sectors
Disk model: ProductCode     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00045763

Device     Boot Start       End   Sectors  Size Id Type
/dev/sdg1  *     2048 122879935 122877888 58.6G  c W95 FAT32 (LBA)


Disk /dev/loop0: 2.6 GiB, 2788671488 bytes, 5446624 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[root@EndeavourOS /]# fdisk -l
Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C58D80A9-0DDD-43B1-B2D0-31A7DE69DFC2

Device       Start        End    Sectors  Size Type
/dev/sda1     4096    4198399    4194304    2G EFI System
/dev/sda2  4198400 3907029101 3902830702  1.8T Linux filesystem


Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdc: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xddc460dc

Device     Boot Start        End    Sectors  Size Id Type
/dev/sdc1        2048 3907028991 3907026944  1.8T  7 HPFS/NTFS/exFAT


Disk /dev/sdd: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: Samsung SSD 870 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sde: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: SanDisk SD6SB2M-
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 764B9F47-FD52-4477-9A4E-87B78659A19D

Device         Start        End   Sectors   Size Type
/dev/sde1       2048    1023999   1021952   499M Windows recovery environment
/dev/sde2    1024000    1226751    202752    99M EFI System
/dev/sde3    1226752    1259519     32768    16M Microsoft reserved
/dev/sde4    1259520  998492159 997232640 475.5G Microsoft basic data
/dev/sde5  998492160 1000212479   1720320   840M Windows recovery environment


Disk /dev/sdf: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: MB2000GCWDA     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4DBE1279-A8B6-40B0-A005-B4B35852B827

Device     Start        End    Sectors  Size Type
/dev/sdf1     34      32767      32734   16M Microsoft reserved
/dev/sdf2  32768 3907026943 3906994176  1.8T Microsoft basic data


Disk /dev/sdg: 58.59 GiB, 62914560000 bytes, 122880000 sectors
Disk model: ProductCode     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00045763

Device     Boot Start       End   Sectors  Size Id Type
/dev/sdg1  *     2048 122879935 122877888 58.6G  c W95 FAT32 (LBA)


Disk /dev/loop0: 2.6 GiB, 2788671488 bytes, 5446624 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

I typically choose boot devices from bios and I haven’t booted windows for a couple months before today so I don’t see how it could anything windows related. I can still select my linux boot drive in bios but I’m just dropped into the systemd boot menu with no option to boot endeavourOS. I’ve reinstalled Systemd with arch-chroot and at the end it gives me a “Couldn’t find EFI systems partitions, skipping.” message which seemed relevant but I’m pretty novice in figuring out boot issues. My last update was a little over 2 weeks ago. Sorry if I’m adding tons of extraneous info I just want to cover the first things people asked in threads covering similar issues.

2

The issues we are experiencing are similar, and I have discussed the same matters in this thread. I believe our forum administrators will merge the two threads. I recommend you follow this thread as well. https://forum.endeavouros.com/t/pc-wont-get-past-hp-logo-after-upgrade/75237/3

3

It sounds like something went wrong in your update. I would arch-chroot into your system again. Two things to be extra careful of:

  • Make sure you boot the ISO in UEFI mode
  • Make sure you mount the EFI partition in the correct location

Once you successfully arch-chroot in, run pacman -Syu followed by reinstall-kernels. If you get any errors, stop and report them here.

If you don’t get any errors try rebooting.

You issue appears to be totally different and unrelated. Even if they were similar, it is pretty unlikely we would merge two troubleshooting topics.

4

Thanks!

I’ve never manually mounted an efi partition before. Is it as simple as mounting it to /efi or is there system specific mount point I should be using?

5

Yes, although you should mount it to /mnt/efi in this case since you are going to chroot in. This article in our wiki covers the details.

6

Thanks so much!

Issue is resolved now. I updated systemd with the efi partition mounted correctly and rebuilt kernels and my system’s back to booting correctly

1 Like