EndeavourOS not showing up in boot manager

General system Newbie
1

Hello!
I decided to install EndeavourOS, but after the installation it does not show up in my boot manager. Only things showing up are my Windows installation & the Live USB.

I am using a Asus Zephyrus G15.
I installed Endeavour on a new partition on my NVMe drive.
I also used the NVidia installer option if that matters.
I used systemd-boot
Secure boot is disabled
Fast boot is disabled

Here are some commands I found in similar threads & their output;

$ sudo parted -l
Model: Kingston DataTraveler 3.0 (scsi)
Disk /dev/sda: 124GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name                 Flags
 1      1049kB  124GB  124GB  fat32        Main Data Partition  msftdata


Model: WD PC SN735 SDBPNHH-1T00-1002 (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  274MB   273MB   fat32        EFI system partition          boot, esp
 2      274MB   290MB   16.8MB               Microsoft reserved partition  msftres
 3      290MB   858GB   858GB   ntfs         Basic data partition          msftdata
 7      858GB   1000GB  142GB   ext4         endeavouros
 4      1000GB  1000GB  734MB   ntfs         Basic data partition          hidden, diag, no_automount
 5      1000GB  1024GB  23.6GB  ntfs         Basic data partition          hidden, msftdata, no_automount
 6      1024GB  1024GB  210MB   fat32        Basic data partition          hidden, diag, no_automount

$ efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0000,0001
Boot0000* Windows Boot Manager	HD(1,GPT,9d649454-956a-45c3-a36b-388340b1e835,0x800,0x82000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000072000100000010000000040000007fff0400
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 08 00 00 00 00 00 54 94 64 9d 6a 95 c3 45 a3 6b 38 83 40 b1 e8 35 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 49 00 43 00 52 00 4f 00 53 00 4f 00 46 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 4d 00 47 00 46 00 57 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 72 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0001* UEFI: KingstonDataTraveler 3.0, Partition 1	PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x4)/USB(3,0)/HD(1,GPT,d6544d5c-c82d-456e-a728-dcccfbc842d1,0x800,0xe676bd3)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 01 08 / 01 01 06 00 04 00 / 03 05 06 00 03 00 / 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 d3 6b 67 0e 00 00 00 00 5c 4d 54 d6 2d c8 6e 45 a7 28 dc cc fb c8 42 d1 02 02 / 7f ff 04 00
    data: 00 00 42 4f


$ sudo blkid
/dev/nvme0n1p1: LABEL="SYSTEM" UUID="2CF8-30FC" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9d649454-956a-45c3-a36b-388340b1e835"
/dev/nvme0n1p3: LABEL="OS" BLOCK_SIZE="512" UUID="9C9AF9D79AF9AE40" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="6f976cc3-02fc-42e7-a829-126f12bbe8c3"
/dev/nvme0n1p7: LABEL="endeavouros" UUID="2990222c-1db8-413e-b454-1f5ca9c9a639" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="endeavouros" PARTUUID="f6f88435-bdfc-44ce-a93b-d61925f21c99"
/dev/nvme0n1p4: LABEL="RECOVERY" BLOCK_SIZE="512" UUID="A8C26D2AC26CFE46" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="dde75255-0782-42e5-b488-076bae901103"
/dev/nvme0n1p5: LABEL="RESTORE" BLOCK_SIZE="512" UUID="720071A8007173C7" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="2a703f1f-f5d4-41c9-8ec8-8460474d0f95"
/dev/nvme0n1p6: LABEL="MYASUS" UUID="E071-AD21" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Basic data partition" PARTUUID="0c1bd172-c408-47e0-8e94-2f9a7b4a74de"
/dev/sda1: LABEL="EOS_202305" UUID="1518-3060" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Main Data Partition" PARTUUID="d6544d5c-c82d-456e-a728-dcccfbc842d1"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="cf115995-bb92-4a85-86da-aa663a144316"
/dev/loop0: BLOCK_SIZE="1048576" TYPE="squashfs"

I also uploaded my installation log, but am not sure if it’s showing the previous time, or only this time that I booted into the Live USB; http://ix.io/4ylJ

Thanks for any help

2

Did you use manual partitioning?

You don’t seem to have an appropriately sized EFI partition.

3

What I did is in windows’ disk utility I shrunk the main partition to create an empty partition.
Then in the Endeavour installer I selected “Replace a Partition” and selected the empty/free partition.
So no; I used the GUI

4

When using “replace a partition”, the installer shouldn’t let you choose an EFI partition that is only 273MB when you choose systemd-boot.

5

For EFI system partition I had New selected

6

It doesn’t look like a new ESP was created. It looks like the install failed to me.

Are you sure it succeeded?

7

Everything I know is or should be in the logs. I can try again, just didn’t want to make changes which could interfere with the debug information I provided

8

The log file you posted show an installation that never even started. Are you sure that is the log from your actual install? Where did you get that log from?

9

Like I said I wasn’t sure if that log included my previous install, or just the current session.
I got the log file from ~/endeavour-install.log

$ find *.log
endeavour-install.log

unfortunately it seems like that is the only logfile

10

The log file for your actual install would be in /var/log in the endeavouros partition. You would need to mount it to see it.

That being said, it would probably be easier just to reinstall and check the logs before rebooting.

11

I just want to make sure whether the following looks correct partition wise before I proceed with re-installing

image
image1027Ă—717 80.8 KB

12

Is that all of it?

Usually there would be more after the last line shown there.

13

You are right! I didn’t notice that there was more

image
image1032Ă—830 112 KB

14

Yeah, that looks fine.

15

Here is my post-install pre-restart data;
Install log (http://ix.io/4ylN)

$ efibootmgr
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0002,0000,0001
Boot0000* Windows Boot Manager	HD(1,GPT,9d649454-956a-45c3-a36b-388340b1e835,0x800,0x82000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000072000100000010000000040000007fff0400
Boot0001* UEFI: KingstonDataTraveler 3.0, Partition 1	PciRoot(0x0)/Pci(0x8,0x1)/Pci(0x0,0x4)/USB(3,0)/HD(1,GPT,d6544d5c-c82d-456e-a728-dcccfbc842d1,0x800,0xe676bd3)0000424f
Boot0002* Linux Boot Manager	HD(7,GPT,b3aadc1b-1b6b-43cf-905a-5c105768596e,0x63e4ea8f,0x1f4000)/File(\EFI\systemd\systemd-bootx64.efi)

Looks like the bootmanager was created

16

Yes, it looks like the install was successful this time.

2 Likes
17

It worked!
Thank you so much, and sorry for any trouble caused :slight_smile:
I just didn’t want to ask for support, make a bunch of changes, then get answers that no longer help because I broke things in even more ways :laughing:

2 Likes
18

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