I understand your frustration with the formatting @mbod , so I have fixed it for this post, and gone back and edited previous posts in the thread, too. For other newbies reading this in the future, a good forum thread regarding formatting is here. Thank you for your patience.
This is the rough protocol I just followed. I exited the arch-chroot, checked the drives again, unmounted the previously mounted partitions (nvme0n1p2 for the OS on /mnt, nvme0n1p1 for the vfat on /mnt/efi) with sudo umount, remounted those same partitions with sudo mount, then re-accessed the install with arch-chroot.
[root@EndeavourOS /]# exit exit [liveuser@eos-2022.12.17 ~]$ sudo lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS loop0 squashfs 4.0 0 100% /run/archiso/airootfs sda └─sda1 ext4 1.0 9d7c24b4-c9bb-47ad-86f9-f5f38a468949 sdb └─sdb1 ext4 1.0 4672a3f5-0834-463c-8e33-54bceed39191 sdc iso9660 Joliet Extension EOS_202212 2022-12-17-15-01-34-00 ├─sdc1 iso9660 Joliet Extension EOS_202212 2022-12-17-15-01-34-00 0 100% /run/archiso/bootmnt └─sdc2 vfat FAT16 ARCHISO_EFI A59C-8529 nvme0n1 ├─nvme0n1p1 vfat FAT32 DAF4-F2D2 634M 36% /mnt/efi └─nvme0n1p2 ext4 1.0 endeavouros b8be75f5-b29e-4fb4-a43d-6e0bbebcfc45 188.3G 74% /mnt [liveuser@eos-2022.12.17 ~]$ sudo mount /dev/nvme0n1p2 /mnt mount: /mnt: /dev/nvme0n1p2 already mounted on /mnt. dmesg(1) may have more information after failed mount system call. [liveuser@eos-2022.12.17 ~]$ sudo mount /dev/nvme0n1p1 /mnt/efi mount: /mnt/efi: /dev/nvme0n1p1 already mounted on /mnt/efi. dmesg(1) may have more information after failed mount system call. [liveuser@eos-2022.12.17 ~]$ umount /mnt/efi umount: /mnt/efi: must be superuser to unmount. [liveuser@eos-2022.12.17 ~]$ sudo umount /mnt/efi [liveuser@eos-2022.12.17 ~]$ sudo umount /mnt [liveuser@eos-2022.12.17 ~]$ sudo mount /dev/nvme0n1p2 /mnt [liveuser@eos-2022.12.17 ~]$ sudo mount /dev/nvme0n1p1 /mnt/efi [liveuser@eos-2022.12.17 ~]$ sudo arch-chroot /mnt
From there, I reinstalled the systemd boot entry with bootctl install, then checked the efibootmgr output again. Unfortunately, the Boot0001 entry seems similar to before. Can you see a particular issue with how I have executed it now? Might it be possible to switch to using grub as a bootloader while in with arch-chroot? Or does this poster’s solution seem applicable?
[root@EndeavourOS /]# bootctl install Running in a chroot, enabling --graceful. Created "/efi/loader/keys". 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). Not booted with EFI or running in a container, skipping EFI variable modifications. [root@EndeavourOS /]# efibootmgr -v BootCurrent: 0003 Timeout: 1 seconds BootOrder: 0001,0002,0003 Boot0001* UEFI OS HD(1,GPT,b84194c9-c938-bb46-a054-e311f5128a68,0x1000,0x1f4000)/\EFI\BOOT\BOOTX64.EFI0000424f dp: 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 40 1f 00 00 00 00 00 c9 94 41 b8 38 c9 46 bb a0 54 e3 11 f5 12 8a 68 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 42 00 4f 00 4f 00 54 00 58 00 36 00 34 00 2e 00 45 00 46 00 49 00 00 00 / 7f ff 04 00 data: 00 00 42 4f Boot0002* UEFI: USB PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x3)/USB(7,0)/CDROM(1,0x398c00,0x34a98)0000424f dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 01 / 01 01 06 00 00 00 / 01 01 06 00 00 08 / 01 01 06 00 03 00 / 03 05 06 00 07 00 / 04 02 18 00 01 00 00 00 00 8c 39 00 00 00 00 00 98 4a 03 00 00 00 00 00 / 7f ff 04 00 data: 00 00 42 4f Boot0003* UEFI: USB, Partition 2 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x3)/USB(7,0)/HD(2,MBR,0x5ab6cd03,0x398c00,0x34800)0000424f dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 01 / 01 01 06 00 00 00 / 01 01 06 00 00 08 / 01 01 06 00 03 00 / 03 05 06 00 07 00 / 04 01 2a 00 02 00 00 00 00 8c 39 00 00 00 00 00 00 48 03 00 00 00 00 00 03 cd b6 5a 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 7f ff 04 00 data: 00 00 42 4f [root@EndeavourOS /]# bootctl list type: Boot Loader Specification Type #1 (.conf) title: EndeavourOS (6.18.18-1-lts) (default) (not reported/new) id: bbad49b99d8d44288f4c4feee6dd5807-6.18.18-1-lts.conf source: /efi//loader/entries/bbad49b99d8d44288f4c4feee6dd5807-6.18.18-1-lts.conf (on the EFI System Partition) sort-key: endeavouros-6.18.18-1-lts version: 6.18.18-1-lts machine-id: bbad49b99d8d44288f4c4feee6dd5807 linux: /efi//bbad49b99d8d44288f4c4feee6dd5807/6.18.18-1-lts/linux initrd: /efi//bbad49b99d8d44288f4c4feee6dd5807/6.18.18-1-lts/initrd options: nvme_load=YES rw root=UUID=b8be75f5-b29e-4fb4-a43d-6e0bbebcfc45 rw root=UUID=b8be75f5-b29e-4fb4-a43d-6e0bbebcfc45 systemd.machine_id=bbad49b99d8d44288f4c4feee6dd5807 type: Boot Loader Specification Type #1 (.conf) title: EndeavourOS (6.18.18-1-lts-fallback) (not reported/new) id: bbad49b99d8d44288f4c4feee6dd5807-6.18.18-1-lts-fallback.conf source: /efi//loader/entries/bbad49b99d8d44288f4c4feee6dd5807-6.18.18-1-lts-fallback.conf (on the EFI System Partition) sort-key: endeavouros-6.18.18-1-lts-fallback version: 6.18.18-1-lts-fallback machine-id: bbad49b99d8d44288f4c4feee6dd5807 linux: /efi//bbad49b99d8d44288f4c4feee6dd5807/6.18.18-1-lts/linux initrd: /efi//bbad49b99d8d44288f4c4feee6dd5807/6.18.18-1-lts/initrd-fallback options: nvme_load=YES rw root=UUID=b8be75f5-b29e-4fb4-a43d-6e0bbebcfc45 rw root=UUID=b8be75f5-b29e-4fb4-a43d-6e0bbebcfc45 systemd.machine_id=bbad49b99d8d44288f4c4feee6dd5807 type: Boot Loader Specification Type #1 (.conf) title: EndeavourOS (6.19.8-arch1-1) (not reported/new) id: bbad49b99d8d44288f4c4feee6dd5807-6.19.8-arch1-1.conf source: /efi//loader/entries/bbad49b99d8d44288f4c4feee6dd5807-6.19.8-arch1-1.conf (on the EFI System Partition) sort-key: endeavouros-6.19.8-arch1-1 version: 6.19.8-arch1-1 machine-id: bbad49b99d8d44288f4c4feee6dd5807 linux: /efi//bbad49b99d8d44288f4c4feee6dd5807/6.19.8-arch1-1/linux initrd: /efi//bbad49b99d8d44288f4c4feee6dd5807/6.19.8-arch1-1/initrd options: nvme_load=YES rw root=UUID=b8be75f5-b29e-4fb4-a43d-6e0bbebcfc45 rw root=UUID=b8be75f5-b29e-4fb4-a43d-6e0bbebcfc45 systemd.machine_id=bbad49b99d8d44288f4c4feee6dd5807