Since upgraded to pve 9,
While this does not have any impact to booting and running proxmox, but I'd like to find out how to fix the
I have tried the following and none worked so far:
fwupdmgr has stopped working. After searching on the web, I found a few probable solutions but none of them worked. And during that time I am sure I did something stupid and now when I run proxmox-boot-tool refresh I get the following.
Code:
Running hook script 'proxmox-auto-removal'..
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/E389-10C6
Copying kernel and creating boot-entry for 6.14.11-3-pve
Copying kernel and creating boot-entry for 6.14.11-4-pve
/var/tmp/espmounts/E389-10C6/EFI/proxmox/fwupdx64.efi is not a directory - skipping
Copying and configuring kernels on /dev/disk/by-uuid/E389-8099
Copying kernel and creating boot-entry for 6.14.11-3-pve
Copying kernel and creating boot-entry for 6.14.11-4-pve
/var/tmp/espmounts/E389-8099/EFI/proxmox/fwupdx64.efi is not a directory - skipping
While this does not have any impact to booting and running proxmox, but I'd like to find out how to fix the
/var/tmp/espmounts/xxxx-xxxx/EFI/proxmox/fwupdx64.efi is not a directory - skipping error.I have tried the following and none worked so far:
- removing it using
efibootmgr -b X -B - running
proxmox-boot-tool init <disk>