PVE 9 - zpool upgrade

J

jiriteach

New Member
Nov 14, 2024
15
2
3
Hi - Hoping someone can help here.

After a successful upgrade from PVE 8 to 9 - I am just running checks, all is working well.
Both my PVE nodes where originally installed at PVE 8.

zpool status recommends an upgrade. Is it OK to upgrade? Should I upgrade the using zpool?

Thanks

NODE 1

These is my external HDD disk datastore and internal SSD disk datastore - not the boot disk.

Code: 
root@pve:~# zpool status
  pool: dsedd
 state: ONLINE
status: Some supported and requested features are not enabled on the pool.
        The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0B in 00:00:58 with 0 errors on Sun Aug 10 00:24:59 2025
config:

        NAME                                              STATE     READ WRITE CKSUM
        dsedd                                             ONLINE       0     0     0
          ata-WDC_WD15JDRW-11C7VS0_WD-WX32A348ZY90-part2  ONLINE       0     0     0

errors: No known data errors

  pool: dsssd
 state: ONLINE
status: Some supported and requested features are not enabled on the pool.
        The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0B in 00:03:56 with 0 errors on Sun Aug 10 00:27:58 2025
config:

        NAME                                STATE     READ WRITE CKSUM
        dsssd                               ONLINE       0     0     0
          ata-CT1000BX500SSD1_2432E8BE939E  ONLINE       0     0     0

errors: No known data errors

Code: 
root@pve:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
E: /etc/kernel/proxmox-boot-uuids does not exist.

NODE 2

Code: 
root@pve:~# zpool status
  pool: dshdd
 state: ONLINE
status: Some supported and requested features are not enabled on the pool.
        The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0B in 00:08:23 with 0 errors on Sun Aug 10 00:32:24 2025
config:

        NAME                                      STATE     READ WRITE CKSUM
        dshdd                                     ONLINE       0     0     0
          mirror-0                                ONLINE       0     0     0
            ata-WDC_WD60EFZX-68B3FN0_WD-C80RT8GG  ONLINE       0     0     0
            ata-WDC_WD60EFZX-68B3FN0_WD-C80RPMUG  ONLINE       0     0     0

errors: No known data errors

  pool: dsssd
 state: ONLINE
status: Some supported and requested features are not enabled on the pool.
        The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0B in 00:00:28 with 0 errors on Sun Aug 10 00:24:31 2025
config:

        NAME                                  STATE     READ WRITE CKSUM
        dsssd                                 ONLINE       0     0     0
          mirror-0                            ONLINE       0     0     0
            ata-CT1000BX500SSD1_2432E8BE9493  ONLINE       0     0     0
            ata-CT1000BX500SSD1_2423E8B6EA5A  ONLINE       0     0     0

errors: No known data errors

Code: 
root@pve:~# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
E: /etc/kernel/proxmox-boot-uuids does not exist.
 
  • Like
Reactions: Kingneutron
If it is irreversible and does not return to pve8, then it is fine.
The only impact is that if something goes wrong, you can't even see that pool in pve8.That is if it is a version of zpool that does not support it.

If various checks have been completed in pve9, then there is nothing wrong.
 
Last edited:
  • Like
Reactions: jiriteach
I would only recommend doing a zpool upgrade if kernel 6.14 is working well for you.. After the upgrade, you can't use older kernels, as the ZFS will have features that won't work with them.

On my system I had to pin kernel 6.11, as the passthrough of an Intel I211 to a VM does not work on 6.14.
 
  • Like
Reactions: Kingneutron, jedie and jiriteach
jiriteach said:
Thanks - After some reading, and being on the safer side that these zfs pools are non boot ones - I went ahead and upgraded them.

Code: 
zpool upgrade -a

Will upgrade and enable them to the latest features for zfs.
Reboot and all is working well.

Thanks
Click to expand...
is upgrading a boot pool not okay?
 
If you don't connect that rpool to a computer with an older version of the ZFS module when a failure occurs, there should be no problem.

*Do not use the -a option when executing.

I don't think it matters if you don't do it, since I don't think it changes anything unless you use the updated functionality. So I don't see any benefit in doing it.
 
No, zpool status -v <poolname>doesn't list the features.


wmr said:
Without a pool identifier zpool upgrade will only show what feature is not activated for every pool.
Click to expand...
That's it. Thanks.

In my case the output is:


Code: 
~# zpool upgrade
This system supports ZFS pool feature flags.

All pools are formatted using feature flags.


Some supported features are not enabled on the following pools. Once a
feature is enabled the pool may become incompatible with software
that does not support the feature. See zpool-features(7) for details.

Note that the pool 'compatibility' feature can be used to inhibit
feature upgrades.

POOL  FEATURE
---------------
tank
      zilsaxattr
      head_errlog
      blake3
      block_cloning
      vdev_zaps_v2
      redaction_list_spill
      raidz_expansion
      fast_dedup
      longname
      large_microzap


Seems many features was added since the creation of my pool...

Hm! But i'm still on kernel v6.14.11-4-pve and the last one is v6.17.4-2-pve ... I should reboot and see if the new kernel makes any trouble and only after this i should apply the new features, isn't it?!?
 
  • Like
Reactions: proxuser77
jedie said:
No, zpool status -v <poolname>doesn't list the features.
Click to expand...
Yes, you're right, of course zpool upgrade without identifier it is. My memory played tricks on me, and since all my ZFS pools, TrueNAS, and Proxmox are up to date, I couldn't really test it, but I posted anyways. ;-)
 
You must log in or register to reply here.
Top Bottom
Back