One of my pools is mentioning it could be upgraded. not sure if i should try running the zpool upgrade command on it or not. I know when I ran truenas OS before getting the nas servers, I had no issues doing updates to the pools like that. But i have no idea how qnap quts handles it. below the message on the zpool status command.
Anyone else run into this before? I may open a support ticket to ask what to do but figured i also ask here. This is my main data pool so i rather not fubar it but i do have it backed up.
pool: zpool4
state: ONLINE
status: Some supported 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 0 in 0 days 20:27:37 with 0 errors on Tue Mar 17 10:08:09 2026
prune: last pruned 17724121 entries, 856301381 entries are pruned ever
total pruning count #37, avg. pruning rate = 12917 (entry/sec)
expand: none requested
If you have solid backups and do not mind complete re-setup, try it.
But we had other topics where direct ZFS interaction (snapshots) resulted in issues, so it might be best to not fiddle with it, if you cannot handle the results.
We understand that this notice was observed when checking the pool status from the command line. For this situation, we recommend performing the upgrade through the QTS / QuTS hero user interface instead of running zpool upgrade manually from the command line, in order to avoid unexpected issues or exceptions.
We will also share this with the relevant team and suggest improving the wording of this message so that the guidance is clearer.
We understand that your main concern is why only one pool shows this related message while the other pools do not show the same behavior.
Based on the information currently available to us internally, one possible explanation is that this pool may be in a different ZFS feature or compatibility state from the other pools. For example, it may have been created at a different time, imported from another system, or have a different underlying pool feature status.
However, based on the information currently available in the forum, we are not able to confirm the exact cause or determine the most appropriate corrective action at this stage. Since this appears to be related to the status of a specific pool, we would recommend opening a support ticket so our internal team can further check the actual system and pool status and provide a more suitable next-step recommendation.