is it safe to reboot please?

[HarryS]

i just updated my proxmox and got a popup box about installing grub

i picked my boot sda drive,, but got another error screen, but forced the update by selecting yes twice ...

by terminal output showed some grub errors which are above my head on diagnosing....

**************************************************
Setting up grub-common (2.06-3~deb11u1) ...
Installing new version of config file /etc/grub.d/10_linux ...
Installing new version of config file /etc/grub.d/20_linux_xen ...
Installing new version of config file /etc/grub.d/30_os-prober ...
Installing new version of config file /etc/grub.d/30_uefi-firmware ...
Installing new version of config file /etc/grub.d/41_custom ...
Setting up libgssrpc4:amd64 (1.18.3-6+deb11u2) ...
Setting up proxmox-backup-client (2.2.6-1) ...
Setting up libpve-rs-perl (0.7.2) ...
Setting up libavahi-common-data:amd64 (0.8-5+deb11u1) ...
Setting up systemd-timesyncd (247.3-7+deb11u1) ...
Setting up udev (247.3-7+deb11u1) ...
Setting up libhttp-daemon-perl (6.12-1+deb11u1) ...
Setting up libproxmox-rs-perl (0.2.1) ...
Setting up proxmox-offline-mirror-helper (0.3.0-1) ...
Setting up libpam-systemd:amd64 (247.3-7+deb11u1) ...
Setting up libcurl4:amd64 (7.74.0-1.3+deb11u3) ...
Setting up libgdk-pixbuf-2.0-0:amd64 (2.42.2+dfsg-1+deb11u1) ...
Setting up curl (7.74.0-1.3+deb11u3) ...
Setting up grub-efi-amd64-bin (2.06-3~deb11u1) ...
Setting up libc-dev-bin (2.31-13+deb11u4) ...
Setting up libc-devtools (2.31-13+deb11u4) ...
Setting up grub-efi-ia32-bin (2.06-3~deb11u1) ...
Setting up grub2-common (2.06-3~deb11u1) ...
Installing new version of config file /etc/kernel/postinst.d/zz-update-grub ...
Installing new version of config file /etc/kernel/postrm.d/zz-update-grub ...
Setting up libavahi-common3:amd64 (0.8-5+deb11u1) ...
Setting up pve-kernel-helper (7.2-12) ...
Setting up pve-manager (7.2-11) ...
Setting up grub-pc-bin (2.06-3~deb11u1) ...
Setting up grub-pc (2.06-3~deb11u1) ...
Installing for i386-pc platform.
File descriptor 3 (pipe:[7508221]) leaked on vgs invocation. Parent PID 1259114: grub-install.real
File descriptor 3 (pipe:[7508221]) leaked on vgs invocation. Parent PID 1259114: grub-install.real
File descriptor 3 (pipe:[7508221]) leaked on vgs invocation. Parent PID 1259114: grub-install.real
grub-install.real: warning: this GPT partition label contains no BIOS Boot Parti tion; embedding won't be possible.
grub-install.real: error: embedding is not possible, but this is required for RA ID and LVM install.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.53-1-pve
Found initrd image: /boot/initrd.img-5.15.53-1-pve
Found linux image: /boot/vmlinuz-5.15.39-4-pve
Found initrd image: /boot/initrd.img-5.15.39-4-pve
Found linux image: /boot/vmlinuz-5.15.39-3-pve
Found initrd image: /boot/initrd.img-5.15.39-3-pve
Found linux image: /boot/vmlinuz-5.15.39-2-pve
Found initrd image: /boot/initrd.img-5.15.39-2-pve
Found linux image: /boot/vmlinuz-5.15.39-1-pve
Found initrd image: /boot/initrd.img-5.15.39-1-pve
Found linux image: /boot/vmlinuz-5.15.35-3-pve
Found initrd image: /boot/initrd.img-5.15.35-3-pve
Found linux image: /boot/vmlinuz-5.13.19-6-pve
Found initrd image: /boot/initrd.img-5.13.19-6-pve
Found linux image: /boot/vmlinuz-5.13.19-2-pve
Found initrd image: /boot/initrd.img-5.13.19-2-pve
Found linux image: /boot/vmlinuz-5.4.128-1-pve
Found initrd image: /boot/initrd.img-5.4.128-1-pve
Found linux image: /boot/vmlinuz-5.4.106-1-pve
Found initrd image: /boot/initrd.img-5.4.106-1-pve
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up libgdk-pixbuf2.0-bin (2.42.2+dfsg-1+deb11u1) ...
Setting up libc6-dev:amd64 (2.31-13+deb11u4) ...
Setting up libavahi-client3:amd64 (0.8-5+deb11u1) ...
Processing triggers for libc-bin (2.31-13+deb11u4) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for dbus (1.12.20-2) ...
Processing triggers for pve-ha-manager (3.4.0) ...
Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.15.53-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount names pace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.

 

[HarryS]

getting worried to reboot proxmox now

Just tried another update, going round in circles from attachments... screen1, screen2, screen3 ... back to screen1

thanks

 

[Stoiko Ivanov]

How did you setup this system in the first place? (no bios-compat partition sounds odd)

`lsblk` and `findmnt` output might help to see what's going on

 

[HarryS]

How did you setup this system in the first place? (no bios-compat partition sounds odd)

`lsblk` and `findmnt` output might help to see what's going on

Hi,

It was installed via the proxmox ISO (v6, later upgraded to v7 in situ)

sda was the orignal drive it was installed on, I added sdb a few months later to move some VM's on to their own drive

.... that was a few months ago, been running stable since then

i've attached the outputs from the two commands....

Thanks

 

[Dunuin]

sda1 should be your grub boot partition.

I had a similar problem and needed to change the partition type of the sda1 partition because the upgraded grub wasn‘t working with the old grub partition anymore. But in my case I installed PVE6.1 ontop of a Debian 10 using grub with gpt. Can check what I did back then when home again. If I remember right I needed to change that partition ID to "grub_boot" or "bios_grub“ in order for the grub installer to accept that partition.

Whats the output of fdisk -x /dev/sda?

Edit:
Found this:

I'm not using OVH but while upgrading PVE6.4 to 7.0 and debian 10 to 11 the apt dist-upgrade updated grub-pc and wanted to write the new bootloader to my boot disks. But the new grub version wasn't able to recognize my old grub partition. I needed to remove the "boot" flag and add the "bios_grub" flag to my old 1 MB grub partition (sda1) using...

parted /dev/sda
set 1 boot off
set 1 bios_grub on
q
update-grub

...or otherwise update-grub failed with this error:

grub-install.real: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install.real: error: embedding is not possible, but this is required for RAID and LVM install.

 

[HarryS]

sda1 should be your grub boot partition.

I had a similar problem and needed to change the partition type of the sda1 partition because the upgraded grub wasn‘t working with the old grub partition anymore. But in my case I installed PVE6.1 ontop of a Debian 10 using grub with gpt. Can check what I did back then when home again. If I remember right I needed to change that partition ID to "grub_boot" or "bios_grub“ in order for the grub installer to accept that partition.

Whats the output of fdisk -x /dev/sda?

Edit:
Found this:

hi, I've attached the output as requested....

also i went through the commands above and on doing update-grub got the output in output2.txt

i then went back to my other session and answered yes to the dialogue box which did another update-grub and finished off the apt upgrade process

is there a command i can use to check that my grub config is consistent before rebooting my server?

thanks

 

[Dunuin]

Try to run a update-grub to write the grub to disk. You will then see if it fails or not.

 

[HarryS]

Try to run a update-grub to write the grub to disk. You will then see if it fails or not.

Just did an update and got the output below, so looks like is is well... thanks big time for your help !

just in case, i'll download the latest proxmox iso and make a backup of my VM's to my NAS before rebooting (my main pfsense firewall runs as a VM on this server).....

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.60-1-pve
Found initrd image: /boot/initrd.img-5.15.60-1-pve
Found linux image: /boot/vmlinuz-5.15.53-1-pve
Found initrd image: /boot/initrd.img-5.15.53-1-pve
Found linux image: /boot/vmlinuz-5.15.39-4-pve
Found initrd image: /boot/initrd.img-5.15.39-4-pve
Found linux image: /boot/vmlinuz-5.15.39-3-pve
Found initrd image: /boot/initrd.img-5.15.39-3-pve
Found linux image: /boot/vmlinuz-5.15.39-2-pve
Found initrd image: /boot/initrd.img-5.15.39-2-pve
Found linux image: /boot/vmlinuz-5.15.39-1-pve
Found initrd image: /boot/initrd.img-5.15.39-1-pve
Found linux image: /boot/vmlinuz-5.15.35-3-pve
Found initrd image: /boot/initrd.img-5.15.35-3-pve
Found linux image: /boot/vmlinuz-5.13.19-6-pve
Found initrd image: /boot/initrd.img-5.13.19-6-pve
Found linux image: /boot/vmlinuz-5.13.19-2-pve
Found initrd image: /boot/initrd.img-5.13.19-2-pve
Found linux image: /boot/vmlinuz-5.4.128-1-pve
Found initrd image: /boot/initrd.img-5.4.128-1-pve
Found linux image: /boot/vmlinuz-5.4.106-1-pve
Found initrd image: /boot/initrd.img-5.4.106-1-pve
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done