July 31, 20241 yr Hi, my new build with 6.12.11 gives my pool drives the following message: 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. If I do zpool upgrade in the terminal, it does not change anything. I still keep getting the notification for all drives in the pool. How to solve? Thanks.
July 31, 20241 yr Author Hi JorgeB, thanks for your help in my both posts. 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 --------------- disk1 async_destroy empty_bpobj lz4_compress multi_vdev_crash_dump spacemap_histogram enabled_txg hole_birth extensible_dataset embedded_data bookmarks filesystem_limits large_blocks large_dnode sha512 skein edonr userobj_accounting encryption project_quota device_removal obsolete_counts zpool_checkpoint spacemap_v2 allocation_classes resilver_defer bookmark_v2 redaction_bookmarks redacted_datasets bookmark_written log_spacemap livelist device_rebuild zstd_compress draid disk2 async_destroy empty_bpobj lz4_compress multi_vdev_crash_dump spacemap_histogram enabled_txg hole_birth extensible_dataset embedded_data bookmarks filesystem_limits large_blocks large_dnode sha512 skein edonr userobj_accounting encryption project_quota device_removal obsolete_counts zpool_checkpoint spacemap_v2 allocation_classes resilver_defer bookmark_v2 redaction_bookmarks redacted_datasets bookmark_written log_spacemap livelist device_rebuild zstd_compress draid disk3 async_destroy empty_bpobj lz4_compress multi_vdev_crash_dump spacemap_histogram enabled_txg hole_birth extensible_dataset embedded_data bookmarks filesystem_limits large_blocks large_dnode sha512 skein edonr userobj_accounting encryption project_quota device_removal obsolete_counts zpool_checkpoint spacemap_v2 allocation_classes resilver_defer bookmark_v2 redaction_bookmarks redacted_datasets bookmark_written log_spacemap livelist device_rebuild zstd_compress draid disk4 async_destroy empty_bpobj lz4_compress multi_vdev_crash_dump spacemap_histogram enabled_txg hole_birth extensible_dataset embedded_data bookmarks filesystem_limits large_blocks large_dnode sha512 skein edonr userobj_accounting encryption project_quota device_removal obsolete_counts zpool_checkpoint spacemap_v2 allocation_classes resilver_defer bookmark_v2 redaction_bookmarks redacted_datasets bookmark_written log_spacemap livelist device_rebuild zstd_compress draid disk5 async_destroy empty_bpobj lz4_compress multi_vdev_crash_dump spacemap_histogram enabled_txg hole_birth extensible_dataset embedded_data bookmarks filesystem_limits large_blocks large_dnode sha512 skein edonr userobj_accounting encryption project_quota device_removal obsolete_counts zpool_checkpoint spacemap_v2 allocation_classes resilver_defer bookmark_v2 redaction_bookmarks redacted_datasets bookmark_written log_spacemap livelist device_rebuild zstd_compress draid disk8 async_destroy empty_bpobj lz4_compress multi_vdev_crash_dump spacemap_histogram enabled_txg hole_birth extensible_dataset embedded_data bookmarks filesystem_limits large_blocks large_dnode sha512 skein edonr userobj_accounting encryption project_quota device_removal obsolete_counts zpool_checkpoint spacemap_v2 allocation_classes resilver_defer bookmark_v2 redaction_bookmarks redacted_datasets bookmark_written log_spacemap livelist device_rebuild zstd_compress draid disk9 async_destroy empty_bpobj lz4_compress multi_vdev_crash_dump spacemap_histogram enabled_txg hole_birth extensible_dataset embedded_data bookmarks filesystem_limits large_blocks large_dnode sha512 skein edonr userobj_accounting encryption project_quota device_removal obsolete_counts zpool_checkpoint spacemap_v2 allocation_classes resilver_defer bookmark_v2 redaction_bookmarks redacted_datasets bookmark_written log_spacemap livelist device_rebuild zstd_compress draid Regards, Ronald
July 31, 20241 yr Community Expert And those pools were created with Unraid? Also post the diagnostics zip.
August 1, 20241 yr Author Yes, I first accidentally had one drive in XFS, but changed and formatted to ZFS. All drives are ZFS. Hereby the diag. backuppie-diagnostics-20240801-1436.zip
August 1, 20241 yr Community Expert Solution These issue is very strange, new pools should never show that if used with the same opnezfs release, I aslo see data corrution being detected on disks 8 and 9, post the output of zpool status -v disk8 zpool status -v disk9 Also run zpool upgrade -a and post he output of zpool upgrade again
August 2, 20241 yr Author Hi JorgeB, BEFORE: zpool status -v disk8 pool: disk8 state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A config: NAME STATE READ WRITE CKSUM disk8 ONLINE 0 0 0 md8p1 ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: disk8:<0x611> disk8:<0x527> disk8:<0x3ab> zpool status -v disk9 pool: disk9 state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A config: NAME STATE READ WRITE CKSUM disk9 ONLINE 0 0 0 md9p1 ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: disk9:<0x4780> For the data, there is NO data yet on those 2 drives. A scrub fixed the issues. After: zpool status -v disk8 pool: disk8 state: ONLINE scan: scrub repaired 0B in 00:00:03 with 0 errors on Fri Aug 2 10:53:27 2024 config: NAME STATE READ WRITE CKSUM disk8 ONLINE 0 0 0 md8p1 ONLINE 0 0 0 errors: No known data errors zpool status -v disk9 pool: disk9 state: ONLINE scan: scrub repaired 0B in 00:00:05 with 0 errors on Fri Aug 2 10:48:08 2024 config: NAME STATE READ WRITE CKSUM disk9 ONLINE 0 0 0 md9p1 ONLINE 0 0 0 errors: No known data errors zpool upgrade -a brought everything up: zpool upgrade This system supports ZFS pool feature flags. All pools are formatted using feature flags. Every feature flags pool has all supported and requested features enabled. Thank you! Edited August 2, 20241 yr by TallMan206
August 2, 20241 yr Community Expert Glad to hear it's resolved, but those were some weird errors, so there may be an underlying issue, keep monitoring the pools.
August 2, 20241 yr Author I will, thanks. The pool is also much faster now, or maybe it is my feeling, but copying is faster. I'll keep an eye on it. Thanks again.
May 7, 20251 yr Hello, what happens to the data on the hard drives, are they deleted for the upgrade or are they retained? Can I upgrade if Docker is currently running on the hard drive in question or should I stop the Docker beforehand?
May 7, 20251 yr Community Expert 18 minutes ago, SteveAusPuchheim said: Hello, what happens to the data on the hard drives, are they deleted for the upgrade or are they retained? Data is kept, and docker service can remain running
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.