Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.

muekno

Member
Dec 15, 2023
228
14
18
Did an update "apt update && apt dist-upgrade" on my PBS an got
Code:
update-initramfs: Generating /boot/initrd.img-6.8.12-8-pve
I: The initramfs will attempt to resume from /dev/dm-0
I: (/dev/mapper/pbs-swap)
I: Set the RESUME variable to override this.
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.
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.

did the same update at least once a month since about a year, never got messages like this, normally I get the message about a new kernel and I should reboot as soon as possible, what I did.

Now I do not know what will happen if I do a reboot, will that kill my PBS or can I ignore it, or what else should I do
 
installed
is PBS installed from vanilla ISO or provider by hoster or installed over Debian ?
installed from a vanilla ISO last march or so, updated with "apt update && apt dist-upgrade" at least once a month
 
ouput (in code tags please) of commands :
efibootmgr -v
to check if EFI used or not
then
proxmox-boot-tool status
Code:
root@pvs-rh:~# efibootmgr -v
EFI variables are not supported on this system.
Code:
root@pvs-rh:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
E: /etc/kernel/proxmox-boot-uuids does not exist.
root@pvs-rh:~#
 
output of
cat /etc/fstab
lsblk
Code:
root@pvs-rh:~# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pbs/root / ext4 errors=remount-ro 0 1
/dev/pbs/swap none swap sw 0 0
proc /proc proc defaults 0 0
root@pvs-rh:~#
Code:
root@pvs-rh:~# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda            8:0    0 953.9G  0 disk
├─sda1         8:1    0 953.9G  0 part
└─sda9         8:9    0     8M  0 part
sdb            8:16   0 953.9G  0 disk
├─sdb1         8:17   0 953.9G  0 part
└─sdb9         8:25   0     8M  0 part
nvme0n1      259:0    0 238.5G  0 disk
├─nvme0n1p1  259:1    0  1007K  0 part
├─nvme0n1p2  259:2    0     1G  0 part
└─nvme0n1p3  259:3    0 237.5G  0 part
  ├─pbs-swap 252:0    0   7.6G  0 lvm  [SWAP]
  └─pbs-root 252:1    0 213.9G  0 lvm  /
root@pvs-rh:~#

I did not change anything since the installation, the daily backups runs fine, restorte if nedded worked
even the backups last night are fine
 
UUID of nvme0n1p2 should be set in /etc/kernel/proxmox-boot-uuids
( UUID is displayed using lsblk -f )
To allow kernel update stored in partition nvme0n1p2

the daily backups runs fine, restorte if nedded worked
even the backups last night are fine
Only kernel update seems ignored.
What kernel running now ? (from Web GUI button "Package versions" )
 
Last edited:
UUID of nvme0n1p2 should be set in /etc/kernel/proxmox-boot-uuids
( UUID is displayed using lsblk -f )
To allow kernel update stored in partition nvme0n1p2


Only kernel update seems ignored.
What kernel running now ? (from Web GUI button "Package versions" )
it is Backup Server 3.3.2,
Code:
proxmox-backup: 3.3.0 (running kernel: 6.8.12-6-pve)
proxmox-backup-server: 3.3.2-1 (running version: 3.3.2)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-8
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.8.12-6-pve-signed: 6.8.12-6
proxmox-kernel-6.8.12-5-pve-signed: 6.8.12-5
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.11-6-pve-signed: 6.5.11-6
ifupdown2: 3.2.0-1+pmx11
libjs-extjs: 7.0.0-5
proxmox-backup-docs: 3.3.2-1
proxmox-backup-client: 3.3.2-1
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.4
pve-xtermjs: 5.3.0-3
smartmontools: 7.3-pve1
zfsutils-linux: 2.2.7-pve1