Proxmox no longer UEFI booting, UEFI says "Drive not present"

[piexil]

Topic title pretty much sums it up

I have two NVMe (wd/hgst sn200) drives in a zfs mirror and the server no longer boots correctly after a pve-efiboot-tool refresh.
If I select either UEFI OS or Linux Boot Manager it just goes back into the uefi setup screen without booting.


However, if I go into the UEFI shell and manually select the filesystem and load the bootx64.efi file it works just fine.



I cannot get my uefi to recognize that the drive and efi file are present. It was working fine beforehand.

Board is an AsrockRack EPYCD8-2t with an Epyc 7282 cpu. Latest 2.60 bios.

 

[piexil]

root@epyc:~# bootctl
Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.
Alternatively, use --path= to specify path to mount point.
System:
     Firmware: UEFI 2.70 (American Megatrends 5.14)
  Secure Boot: disabled
   Setup Mode: setup

Current Boot Loader:
      Product: systemd-boot 241
     Features: ✓ Boot counting
               ✓ Menu timeout control
               ✓ One-shot menu timeout control
               ✓ Default entry control
               ✓ One-shot entry control
          ESP: /dev/disk/by-partuuid/65fa6b99-da72-4a2a-805e-832796bafcd9
         File: └─/EFI/BOOT/BOOTX64.EFI

Boot Loaders Listed in EFI Variables:
        Title: UEFI OS
           ID: 0x0001
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/65fa6b99-da72-4a2a-805e-832796bafcd9
         File: └─/EFI/BOOT/BOOTX64.EFI

        Title: Linux Boot Manager
           ID: 0x0000
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/65fa6b99-da72-4a2a-805e-832796bafcd9
         File: └─/EFI/systemd/systemd-bootx64.efi

root@epyc:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
2806-EC10 is configured with: uefi
8477-7354 is configured with: uefi

root@epyc:~# zpool status
  pool: rpool
 state: ONLINE
  scan: resilvered 1.86T in 01:04:46 with 0 errors on Thu May 20 16:33:50 2021
config:

        NAME           STATE     READ WRITE CKSUM
        rpool          ONLINE       0     0     0
          mirror-0     ONLINE       0     0     0
            nvme1n1p3  ONLINE       0     0     0
            nvme0n1p3  ONLINE       0     0     0

errors: No known data errors
root@epyc:~# lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sr0          11:0    1  1024M  0 rom 
sr1          11:1    1  1024M  0 rom 
sr2          11:2    1  1024M  0 rom 
sr3          11:3    1  1024M  0 rom 
zd0         230:0    0     1M  0 disk
zd16        230:16   0    64G  0 disk
├─zd16p1    230:17   0   512M  0 part
├─zd16p2    230:18   0   488M  0 part
└─zd16p3    230:19   0    63G  0 part
zd32        230:32   0   256G  0 disk
├─zd32p1    230:33   0   549M  0 part
└─zd32p2    230:34   0 255.5G  0 part
zd48        230:48   0     1M  0 disk
zd64        230:64   0     2T  0 disk
├─zd64p1    230:65   0     1M  0 part
├─zd64p2    230:66   0     1G  0 part
└─zd64p3    230:67   0     2T  0 part
zd80        230:80   0   256G  0 disk
├─zd80p1    230:81   0   512M  0 part
└─zd80p2    230:82   0 255.5G  0 part
nvme3n1     259:0    0  13.4G  0 disk [SWAP]
nvme2n1     259:1    0  13.4G  0 disk [SWAP]
nvme0n1     259:2    0   2.9T  0 disk
├─nvme0n1p2 259:3    0   512M  0 part
└─nvme0n1p3 259:4    0   2.9T  0 part
nvme1n1     259:5    0   2.9T  0 disk
├─nvme1n1p2 259:6    0   512M  0 part
└─nvme1n1p3 259:7    0   2.9T  0 part

 

[piexil]

I was able to solve this by running

proxmox-boot-tool init

on both my esp partitions again