Grub Problem after upgrade

[MH_MUC]

Hi,
I just upgraded from proxmox 6.3 to 6.4

During the upgrade process I got the following message:

update-initramfs: Generating /boot/initrd.img-5.4.78-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/cmdline found - falling back to /proc/cmdline
/dev/disk/by-uuid/8209-F228 contains no grub directory - skipping
/dev/disk/by-uuid/820A-31D3 contains no grub directory - skipping
Errors were encountered while processing:
 pve-manager
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

The proxmox-boot-tool shows the following

proxmox-boot-tool refresh
Running hook script 'proxmox-auto-removal'..
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/cmdline found - falling back to /proc/cmdline
/dev/disk/by-uuid/8209-F228 contains no grub directory - skipping
/dev/disk/by-uuid/820A-31D3 contains no grub directory - skipping


proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
8209-F228 is configured with: uefi
820A-31D3 is configured with: uefi

This is interesting, because it is not an EFI board. So I guess If I reboot now the system won't be bootable. How do I fix this?
Thanks

 

[Moayad]

Hi,

Could you please post the output of apt update && apt dist-upgrade and pveversion -v

 

[MH_MUC]

Hi Moayad,
thank you very much for your help. Here the requested data:

Spoiler: apt update / upgrade

apt update && apt dist-upgrade
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.de.debian.org/debian buster InRelease
Get:3 http://ftp.de.debian.org/debian buster-updates InRelease [51.9 kB]
Get:4 http://download.proxmox.com/debian/pve buster InRelease [3,051 B]
Fetched 55.0 kB in 1s (104 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
pve-manager
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 2,048 kB of archives.
After this operation, 1,024 B disk space will be freed.
Do you want to continue? [Y/n]

Spoiler: pveversion -v

pveversion -v
proxmox-ve: 6.4-1 (running kernel: 5.4.73-1-pve)
pve-manager: 6.4-11 (running version: 6.4-11/28d576c2)
pve-kernel-5.4: 6.4-4
pve-kernel-helper: 6.4-4
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.10-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.2-4
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

EDIT:
The /boot Partition contains grub with all recent kernels. Is the proxmox-boot tool just running parallely?
I just want to make sure the system will be bootable of both mirrored ZFS disks.
I was confused by the message mentioned in my initial post.

 

[Moayad]

Hello,

When you run zpool status it should tell you that there are new features that can be enabled for the pools. Only after you enabled those features, will the pool require a kernel that supports ZFS 2.0.

Therefore, it is safe to upgrade to the latest Proxmox VE version. The system will still be able to boot from older kernels as well until you run zpool upgrade <pool>. After that, you will need to boot from a kernel that supports ZFS 2.0 or higher to access the pool.

please check our wiki below link [0] about the Upgrade to Proxmox VE 6.4

[0] https://pve.proxmox.com/wiki/ZFS:_S...roxmox_Boot_Tool#0._Upgrade_to_Proxmox_VE_6.4

 

[MH_MUC]

Hi Moayad,

thank you for the quick reply. The server is on 6.4 already. I just didn't find a good slot for rebooting it for 6 month. I will migrate the machines shortly and reboot afterwards.
I read through the supplied link. However I am still not sure if the system is bootable now.
I understand that 6.4 is able to provide legacy boot through the proxmox-boot-tool. This doesn't seem to be configured correctly. In Post #1 the tool seems to be configured for EFI, which my board doesn't offer.
How can I make sure the machine will boot up again? Or do you suggest to proceed accoring "Switching to proxmox-boot-tool" as mentioned in your link?

 

[MH_MUC]

For people finding this thread later on. It working even though the boot tool shows UEFI on a legacy booted server.