That didn’t help either.
Here is where I think the problem become visible early, neither the efibootmgr --create --disk /dev/nvme0n1 --part 1 --loader "\EFI\manjaro\grubx64.efi" --label "manjaro" --verbose [1] nor the grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck --no-rs-codes --verbose [2] commands seem to add an entry in /boot/efi/EFI.
Here’s how I know:
manjaro-chroot -a-
[root@manjaro-gnome /]# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=3E2D-C09A /boot/efi vfat umask=0077 0 2
UUID=69d80b23-c4e3-49a1-9ec9-a45ea00bfead / ext4 defaults,noatime 0 1
UUID=d7e8de54-a2a1-4e4c-8103-71695a986efb /home ext4 defaults,noatime 0 2
Note that the UUID of the /boot/efi partition is 3E2D-C09A
3.
[root@manjaro-gnome /]# blkid
/dev/loop1: TYPE="squashfs"
/dev/nvme0n1p7: UUID="fec75e21-7303-4a72-a5e7-2c94a9c93dca" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="eac06ff1-8567-cf4d-be64-45e7e76c29a0"
/dev/nvme0n1p5: UUID="69d80b23-c4e3-49a1-9ec9-a45ea00bfead" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="9d1eadf7-ccce-0a43-bfad-4a74bd4daa21"
/dev/nvme0n1p3: LABEL="Windows" BLOCK_SIZE="512" UUID="902C2E712C2E5290" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="867fd4ba-bd06-478c-a55b-3254a901f683"
/dev/nvme0n1p1: LABEL_FATBOOT="SYSTEM" LABEL="SYSTEM" UUID="3E2D-C09A" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="187cd5f4-1d56-4e19-bb9f-63b345ddf421"
/dev/nvme0n1p6: UUID="d7e8de54-a2a1-4e4c-8103-71695a986efb" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0f3d8dc4-1dc9-d046-bcf5-a9427a904b62"
/dev/nvme0n1p4: LABEL="WinRE" BLOCK_SIZE="512" UUID="64E82EF2E82EC1E2" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="fc57d984-6919-4cf3-bb9c-e1ced50bcb41"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="bd1d6f4d-6d2e-4a95-b967-0ed8fbcaa077"
/dev/loop2: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="MISO_EFI" LABEL="MISO_EFI" UUID="A70B-30CF" BLOCK_SIZE="512" TYPE="vfat"
/dev/sda1: BLOCK_SIZE="2048" UUID="2021-10-17-17-43-04-00" LABEL="MANJARO_GNOME_2116" TYPE="iso9660"
/dev/loop3: TYPE="squashfs"
Note that /dev/nvme0n1p1 is indeed 3E2D-C09A
Now after executing either commands 1 or 2 followed by a ‘grub-update’ and ‘grub-mkconfig’, I should be seeing manjaro under /boot/efi/EFI, but that’s not the case as demonstrated below
-
[root@manjaro-gnome /]# efibootmgr -v
BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0005,0004,2001,0001,0000,0002,2002,2003
Boot0000* Windows Boot Manager HD(1,GPT,187cd5f4-1d56-4e19-bb9f-63b345ddf421,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0001* ubuntu HD(1,GPT,187cd5f4-1d56-4e19-bb9f-63b345ddf421,0x800,0x32000)/File(\EFI\ubuntu\shimx64.efi)RC
Boot0002* Fedora HD(1,GPT,187cd5f4-1d56-4e19-bb9f-63b345ddf421,0x800,0x32000)/File(\EFI\fedora\shim.efi)RC
Boot0003* EFI USB Device (SanDisk Cruzer Glide) PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(1,MBR,0x0,0x5d5a40,0x2000)RC
Boot0004* manjaro HD(1,GPT,187cd5f4-1d56-4e19-bb9f-63b345ddf421,0x800,0x32000)/File(\EFI\manjaro\grubx64.efi)
Boot0005* manjaro HD(1,GPT,187cd5f4-1d56-4e19-bb9f-63b345ddf421,0x800,0x32000)/File(\EFI\manjaro\grubx64.efi)
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
-
[root@manjaro-gnome /]# ls /boot/efi/EFI/
Boot HUAWEI Microsoft UpdateCapsule fedora ubuntu
I feel that after running step 4, step 5 should have a different output and that’s the crux of the problem. Thoughts?
)