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:
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 ?
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:
Hello,
Yesterday i experienced a sudden powerloss, my proxmox node reboots automatically when the power returns.
When the power returned, the node rebooted but i wasn't abte to connect or even ping to it, but it was on.
Attached a screen to it and got this output;
I've did some research on this and booted proxmox debug mode with a usb.
I've tried these steps;
Yesterday i experienced a sudden powerloss, my proxmox node reboots automatically when the power returns.
When the power returned, the node rebooted but i wasn't abte to connect or even ping to it, but it was on.
Attached a screen to it and got this output;
Code:
Error: disk 'lvmid/***' not found.
grub rescue>
I've did some research on this and booted proxmox debug mode with a usb.
I've tried these steps;
Code:
vgscan
found volume group "pve" using metadata type lvm2
vgchange -ay
18 logical volume(s) in volume group "pve" now active
mkdir /media/RESCUE
mount /dev/pve/root...
- anoo222
- grub rescue
- Replies: 49
- Forum: Proxmox VE: Installation and configuration
Help me.
I did not turn on the proxmox server.
I have only been able to access by chroot from the systemrecuecd.
* Error Grub:
error disk 'lvmid/XyYOqp-wfj3-zsZC-s1d4-...' .
Entering rescue mode...
* Error install grub:
grub-probe --device /dev/pve/root
grub-probe: error: no s'ha trobat el disc «lvmid/XyYOqp-wfj3-zsZC-s1d4-jLw6-2XfG-kk1hmE/lbOS2h-dvdX-U18v-zubX-v5Cn-vjUQ-gzTvgi».
grub-install /dev/sda
S'està instal·lant per la plataforma x86_64-efi.
File descriptor 4 (/dev/sda2) leaked on vgs invocation. Parent PID 5764: grub-install.real
File descriptor 4 (/dev/sda2) leaked on vgs...
I did not turn on the proxmox server.
I have only been able to access by chroot from the systemrecuecd.
* Error Grub:
error disk 'lvmid/XyYOqp-wfj3-zsZC-s1d4-...' .
Entering rescue mode...
* Error install grub:
grub-probe --device /dev/pve/root
grub-probe: error: no s'ha trobat el disc «lvmid/XyYOqp-wfj3-zsZC-s1d4-jLw6-2XfG-kk1hmE/lbOS2h-dvdX-U18v-zubX-v5Cn-vjUQ-gzTvgi».
grub-install /dev/sda
S'està instal·lant per la plataforma x86_64-efi.
File descriptor 4 (/dev/sda2) leaked on vgs invocation. Parent PID 5764: grub-install.real
File descriptor 4 (/dev/sda2) leaked on vgs...
- Miquel Gual Torner
- Replies: 30
- Forum: Proxmox VE: Installation and configuration
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: