Proxmox 9, update-grub causes "lvmid/***" error

kristapsesterlins

New Member
Dec 18, 2024
3
0
1
Hi,

Recently I did an upgrade from Proxmox 8 to 9 without any issues.

Disk layout:

2x 500Gb SSDs in LVM RAID1 (/dev/sda and /dev/sdb)
2x 4Tb HDDs in LVM RAID1

The pve/root partition was extended from 23.29G to 46.58G

#lvextend -L +23.29G /dev/pve/root
#resize2fs /dev/pve/root

After adding the second EFI (/dev/sda2) partition, since it is not mirrored by RAID (https://wiki.debian.org/UEFI#RAID_for_the_EFI_System_Partition)

I issued the #update-grub command, and the following error is shown:

Code:
root@proxmox-server03:/etc/kernel# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.17.4-2-pve
Found initrd image: /boot/initrd.img-6.17.4-2-pve
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
/usr/sbin/grub-probe: error: disk `lvmid/ycBQtc-nUb2-gzPg-Vlox-jNaW-UBXJ-HqJ1zZ/YnlNT9-23MX-roSN-wkns-04nk-uD4v-zC0fBL' not found.

error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
/usr/sbin/grub-probe: error: disk `lvmid/ycBQtc-nUb2-gzPg-Vlox-jNaW-UBXJ-HqJ1zZ/YnlNT9-23MX-roSN-wkns-04nk-uD4v-zC0fBL' not found.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
error: invalid segment.
/usr/sbin/grub-probe: error: disk `lvmid/ycBQtc-nUb2-gzPg-Vlox-jNaW-UBXJ-HqJ1zZ/YnlNT9-23MX-roSN-wkns-04nk-uD4v-zC0fBL' not found.

Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Found memtest86+ 32bit EFI image: /boot/memtest86+ia32.efi
Found memtest86+ 64bit image: /boot/memtest86+x64.bin
Found memtest86+ 32bit image: /boot/memtest86+ia32.bin
Adding boot menu entry for UEFI Firmware Settings ...
done

Code:
grub-install --version
grub-install.real (GRUB) 2.12-9+pmx2

Before writing this thread I researched the forum posts:


and

https://pve.proxmox.com/wiki/Recover_From_Grub_Failure

The documentation mentions PVE v8, but this system was installed with UEFI only option on the 2nd of July, 2025. Is this still the infamous grub bug - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987008 that was patched ?

Code:
Jul 02 15:13:09 proxmox-server03 kernel: Linux version 6.8.12-9-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-9 (2025-03-16T19:18Z) ()

Code:
root@proxmox-server03:/etc/kernel# lvdisplay /dev/pve/root
  --- Logical volume ---
  LV Path                /dev/pve/root
  LV Name                root
  VG Name                pve
  LV UUID                YnlNT9-23MX-roSN-wkns-04nk-uD4v-zC0fBL
  LV Write Access        read/write
  LV Creation host, time proxmox, 2025-07-02 15:10:08 +0300
  LV Status              available
  # open                 1
  LV Size                46.58 GiB
  Current LE             11925
  Mirrored volumes       2
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           252:4
 
Last edited:
I am not sure if Grub supports LVM RAID, it's not used by the PVE installer and thus not tested by us.

you can probably switch to using proxmox-boot-tool, which will put Grub (or systemd-boot) and the kernel + initrd on the ESP, and thus no longer require Grub to be able to access the root file system (and LVM) at all.
 
>I am not sure if Grub supports LVM RAID, it's not used by the PVE installer and thus not tested by us.

The bootloader's EFI file is on a single disk (/dev/sda2) and it is manually copied and updated to the second disks (/dev/sdb2) EFI partition as shown in the Debian wiki link. This is a known issue with with UEFI and Software RAID, as in my case.

>you can probably switch to using proxmox-boot-tool, which will put Grub (or systemd-boot) and the kernel + initrd on the ESP, and thus no longer require Grub to be able to access the root file system (and LVM) at all.

Unfortunately, I cannot take the system offline, since it is in a remote location.