Update fails complaining about grub-efi-amd64

[dignus]

I just updated 2 PBS's to the latest versions, enterprise repo. Both machines fail with these lines as the last ones:

update-initramfs: Generating /boot/initrd.img-6.8.4-2-pve
W: No zstd in /usr/bin:/sbin:/bin, using gzip
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.
Alternatively, use --esp-path= to specify path to mount point.

I've read about this error on the PVE 7 to 8 upgrade thread, but I'm not sure if the fix for this is the same. I could install grub-efi-amd64 but how to proceed after that?

 

[Chris]

I just updated 2 PBS's to the latest versions, enterprise repo. Both machines fail with these lines as the last ones:

update-initramfs: Generating /boot/initrd.img-6.8.4-2-pve
W: No zstd in /usr/bin:/sbin:/bin, using gzip
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.
Alternatively, use --esp-path= to specify path to mount point.

I've read about this error on the PVE 7 to 8 upgrade thread, but I'm not sure if the fix for this is the same. I could install grub-efi-amd64 but how to proceed after that?

Hi,
are you referring to this section? https://pve.proxmox.com/wiki/Upgrade_from_7_to_8#GRUB_Might_Fail_To_Boot_From_LVM_in_UEFI_Mode

If so and you are running with the root filesystem on LVM, you should simply install the package via apt install grub-efi-amd64, which will also trigger regeneration of the grub configuration.

 

[dignus]

Thanks @chris. However, that'll trigger the removal of grub-pc, is that correct?

root@pbs:~# apt install grub-efi-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  pve-kernel-6.2 pve-kernel-6.2.16-4-pve
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  grub-pc
The following NEW packages will be installed:
  grub-efi-amd64
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 45.7 kB of archives.
After this operation, 384 kB disk space will be freed.
Do you want to continue? [Y/n]

 

[Chris]

Thanks @chris. However, that'll trigger the removal of grub-pc, is that correct?

root@pbs:~# apt install grub-efi-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  pve-kernel-6.2 pve-kernel-6.2.16-4-pve
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  grub-pc
The following NEW packages will be installed:
  grub-efi-amd64
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 45.7 kB of archives.
After this operation, 384 kB disk space will be freed.
Do you want to continue? [Y/n]

Yes, the grub-pc is for legacy bios mode. Please double check that you are booted using EFI firmware by checking that the /sys/firmware/efi directory exists. Are you maybe using systemd-boot instead of grub? What is the output of proxmox-boot-tool status?