zpool upgrade

[Stoiko Ivanov]

So, what you are saying is, if zfs is not used for boot, everything will be fine and zpool upgrade should work fine?

I have the zpool on 2 partitions outside of booting areas (nvme0n1p3/nvme1n1p3):

The zpool upgrade should not be an issue then - but as always before touching the disk-configuration of a productive system - make sure you have working and tested backups!

For completeness sake - mdraid is not supported by us.

 

[MrBrown]

So, I found what the documentation has to say on this: https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_zfs_features

Since my system is configured with grub, I think it is not safe to upgrade for new pool features.

pve ~ # proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with legacy bios
E231-DD93 is configured with: grub (versions: 6.2.16-20-pve, 6.2.16-3-pve, 6.5.13-5-pve)
E232-5756 is configured with: grub (versions: 6.2.16-20-pve, 6.2.16-3-pve, 6.5.13-5-pve)

I'm in the exact same situation... running Proxmox 8.2.2 and my rpool wants an upgrade.

proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with legacy bios
470D-341E is configured with: grub (versions: 6.5.13-3-pve, 6.5.13-5-pve, 6.8.4-3-pve)
DE92-A66D is configured with: grub (versions: 6.5.13-3-pve, 6.5.13-5-pve, 6.8.4-3-pve)

proxmox-boot-tool says I'm using legacy BIOS.

But I'm not sure if the fact that proxmox-boot-tool is used (even with a legacy BIOS) means that upgrading rpool is safe.
It seems that there are three different versions for the boot process:
- UEFI with proxmox-boot-tool --> upgrading rpool is safe
- legacy BIOS with proxmox-boot-tool --> is upgrading rpool safe or not?
- direct grub boot from old proxmox versions without proxmox-boot-tool

Can someone clarify this, as this question seems to come up frequently?

Thanks in advance

 

[MrBrown]

I upgraded all my pools except for the rpool.

Can anyone provide insights on this situation?

Or is switching to UEFI mode the only solution? If so, is it possible to switch to UEFI with the current installation, or will I need to perform a new installation with UEFI enabled?

Thanks in advance for any suggestions!

 

[Kingneutron]

I would not upgrade rpool at any point after install, just to be safe, bc unless you do a zpool checkpoint beforehand it is irreversible. And most people (I would say) are not even aware of that.

https://openzfs.github.io/openzfs-docs/man/master/8/zpool-checkpoint.8.html

https://www.reddit.com/r/zfs/comments/s438qu/zpool_upgrade/

For completeness sake, I would backup your configs and critical files and reinstall fresh with UEFI mode (to a different disk if possible, and you may have to turn off Secure boot) and migrate your configs over. Then do a qm rescan to attach all the vdisks to VMs/CTRs.

https://github.com/kneutron/ansitest/tree/master/proxmox

Look into the bkpcrit script, set target to separate non-root disk or NAS

Of course, it's always a good idea to have a full backup of all your VMs and such before doing something like this.

 

[MrBrown]

Thank you. So for the moment I think it will be best to just stick with what I have. Since rpool is not the biggest and other pools are upgraded, it shouldn't have a big impact to run the "old" rpool at all.