"couldn't find efi partition" during regular upgrade

jona · Sunday at 19:13

Good evening.
I've just upgraded my single node setup via web UI. but unfortunatelly I got a message that tells me, that
```update-initramfs```didn't work.
The log looks like this:

Code:

Setting up curl (7.88.1-10+deb12u8)
Setting up openssl (3.0.15-1~deb12ul)
Setting up iputils-ping (3:20221126-1+deb12ul) ...
Setting up sqlites (3.40.1-2+deb12ul)
Setting up python3.11-minimal (3.11.2-6+deb12u4)
Setting up Fibpython3. 11-stdlib:amd64 (3.11.2-64debi2u4) ...
Setting up fdisk (2.38.1-5+deb12u2)
Setting up python3.11 (3.11.2-6+deb12u4) ...
Processing triggers for libc-bin (2.36-9+deb12u9)...
Processing triggers for systemd (252.31-1~deb12ul) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for dbus (1.14.10-1~debl2ul)...
Processing triggers for mailcap (3.70+nmul) ...
Processing triggers for initramfs-tools (0.142+deb12ul) ...
update-initramfs: Generating /boot/initrd.img-6.8.12-2-pve
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.
Your System is up-to-date
starting shell

So first of all I tried to upgrade again via "Refresh" and upgrade -> nothing to do.

Then I tried to execute the ```update-initramfs``` explicitly and got the same issue:

Code:

update-initramfs -u -k 6.8.12-2-pve
update-initramfs: Generating /boot/initrd.img-6.8.12-2-pve
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.

I found this post but it doesn't seem to be adequate, as I already have a /boot directory with content.
Anyone knows how to solve the issue?

jsterr · Monday at 17:56

Hello Jona,

Whats the output of proxmox-boot-tool status? What about efibootmgr -v?

Greetings Jonas

jona · Monday at 18:14

Thanks for your reply,
the output is as follows

Code:

# 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.
# efibootmgr -v
EFI variables are not supported on this system.

jsterr · Monday at 18:37

Thanks! Seems like your not booting from an efi system. What is the output of:

findmnt /and lsblk -o +FSTYPE

jona · Monday at 19:17

Code:

# findmnt /
TARGET SOURCE               FSTYPE OPTIONS
/      /dev/mapper/pve-root ext4   rw,relatime,errors=remount-ro
# lsblk -o +FSTYPE
NAME                         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS FSTYPE
sda                            8:0    0  5.5T  0 disk             
├─sda1                         8:1    0 1007K  0 part             
├─sda2                         8:2    0    1G  0 part             vfat
└─sda3                         8:3    0  5.5T  0 part             LVM2_member
  ├─pve-swap                 252:0    0    8G  0 lvm  [SWAP]      swap
  ├─pve-root                 252:1    0   96G  0 lvm  /           ext4
  ├─pve-data_tmeta           252:2    0 15.9G  0 lvm             
  │ └─pve-data-tpool         252:4    0  5.3T  0 lvm             
  │   ├─pve-data             252:5    0  5.3T  1 lvm             
  │   ├─pve-vm--100--disk--0 252:6    0   20G  0 lvm              ext4
  │   ├─pve-vm--103--disk--0 252:7    0  500G  0 lvm              ext4
  │   ├─pve-vm--105--disk--0 252:8    0   50G  0 lvm              ext4
  │   ├─pve-vm--102--disk--0 252:9    0  150G  0 lvm              ext4
  │   ├─pve-vm--201--disk--0 252:12   0  350G  0 lvm             
  │   ├─pve-vm--101--disk--0 252:13   0   80G  0 lvm              ext4
  │   ├─pve-vm--202--disk--0 252:14   0  200G  0 lvm             
  │   ├─pve-vm--204--disk--0 252:15   0    4M  0 lvm             
  │   ├─pve-vm--204--disk--1 252:16   0  100G  0 lvm             
  │   ├─pve-vm--204--disk--2 252:17   0    4M  0 lvm             
  │   ├─pve-vm--204--disk--3 252:18   0    4M  0 lvm             
  │   ├─pve-vm--205--disk--0 252:19   0    4M  0 lvm             
  │   ├─pve-vm--205--disk--1 252:20   0   32G  0 lvm             
  │   ├─pve-vm--205--disk--2 252:21   0    4M  0 lvm             
  │   └─pve-vm--108--disk--0 252:22   0  100G  0 lvm             
  └─pve-data_tdata           252:3    0  5.3T  0 lvm             
    └─pve-data-tpool         252:4    0  5.3T  0 lvm             
      ├─pve-data             252:5    0  5.3T  1 lvm             
      ├─pve-vm--100--disk--0 252:6    0   20G  0 lvm              ext4
      ├─pve-vm--103--disk--0 252:7    0  500G  0 lvm              ext4
      ├─pve-vm--105--disk--0 252:8    0   50G  0 lvm              ext4
      ├─pve-vm--102--disk--0 252:9    0  150G  0 lvm              ext4
      ├─pve-vm--201--disk--0 252:12   0  350G  0 lvm             
      ├─pve-vm--101--disk--0 252:13   0   80G  0 lvm              ext4
      ├─pve-vm--202--disk--0 252:14   0  200G  0 lvm             
      ├─pve-vm--204--disk--0 252:15   0    4M  0 lvm             
      ├─pve-vm--204--disk--1 252:16   0  100G  0 lvm             
      ├─pve-vm--204--disk--2 252:17   0    4M  0 lvm             
      ├─pve-vm--204--disk--3 252:18   0    4M  0 lvm             
      ├─pve-vm--205--disk--0 252:19   0    4M  0 lvm             
      ├─pve-vm--205--disk--1 252:20   0   32G  0 lvm             
      ├─pve-vm--205--disk--2 252:21   0    4M  0 lvm             
      └─pve-vm--108--disk--0 252:22   0  100G  0 lvm

jsterr · Monday at 20:22

jona said:

Code:

# findmnt /
TARGET SOURCE               FSTYPE OPTIONS
/      /dev/mapper/pve-root ext4   rw,relatime,errors=remount-ro
# lsblk -o +FSTYPE
NAME                         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS FSTYPE
sda                            8:0    0  5.5T  0 disk           
├─sda1                         8:1    0 1007K  0 part           
├─sda2                         8:2    0    1G  0 part             vfat
└─sda3                         8:3    0  5.5T  0 part             LVM2_member
  ├─pve-swap                 252:0    0    8G  0 lvm  [SWAP]      swap
  ├─pve-root                 252:1    0   96G  0 lvm  /           ext4
  ├─pve-data_tmeta           252:2    0 15.9G  0 lvm           
  │ └─pve-data-tpool         252:4    0  5.3T  0 lvm           
  │   ├─pve-data             252:5    0  5.3T  1 lvm           
  │   ├─pve-vm--100--disk--0 252:6    0   20G  0 lvm              ext4
  │   ├─pve-vm--103--disk--0 252:7    0  500G  0 lvm              ext4
  │   ├─pve-vm--105--disk--0 252:8    0   50G  0 lvm              ext4
  │   ├─pve-vm--102--disk--0 252:9    0  150G  0 lvm              ext4

When I compare this to my homeserver. This is different:

Code:

# You dont have /boot/efi
root@pveneo:~# lsblk -o +FSTYPE
NAME                            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS             FSTYPE
sda                               8:0    0 447.1G  0 disk
├─sda1                            8:1    0  1007K  0 part
├─sda2                            8:2    0     1G  0 part /boot/efi               vfat
└─sda3                            8:3    0 446.1G  0 part                         LVM2_member

# The same

root@pveneo:~# 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.

# Different

root@pveneo:~# efibootmgr -v
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0004,0005,0001,0000
Boot0000  Windows Boot Manager  VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...................
Boot0001  debian        VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0004* proxmox       HD(2,GPT,e3c5dd4c-12b2-4ef0-b867-ec9ce711610c,0x800,0x200000)/File(\EFI\PROXMOX\GRUBX64.EFI)
Boot0005* UEFI OS       HD(2,GPT,e3c5dd4c-12b2-4ef0-b867-ec9ce711610c,0x800,0x200000)/File(\EFI\BOOT\BOOTX64.EFI)..BO

I personally would go for: https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_proxmox_boot_tool but make sure to have a backup from your vms, in case something goes wrong. "Setting up a new partition for use as synced ESP" and "Updating the configuration on all ESPs".

Search

Search

"couldn't find efi partition" during regular upgrade

jona

New Member

jsterr

Renowned Member

jona

New Member

jsterr

Renowned Member

jona

New Member

jsterr

Renowned Member