arcayne

That's encouraging. I've intentionally avoided running any pool upgrades for some time now, for fear of making my eventual exodus even harder. So... fingers crossed. pool: home 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 19:40:54 with 0 errors on Thu Jan 16 00:01:05 2025 config: NAME STATE READ WRITE CKSUM home ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 /dev/sdg1 ONLINE 0 0 0 /dev/sde1 ONLINE 0 0 0 /dev/sda1 ONLINE 0 0 0 errors: No known data errors pool: work 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 06:34:05 with 0 errors on Wed Jan 15 10:54:06 2025 config: NAME STATE READ WRITE CKSUM work ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 /dev/sdd1 ONLINE 0 0 0 /dev/sdc1 ONLINE 0 0 0 errors: No known data errors home feature@async_destroy enabled local home feature@empty_bpobj active local home feature@lz4_compress active local home feature@multi_vdev_crash_dump enabled local home feature@spacemap_histogram active local home feature@enabled_txg active local home feature@hole_birth active local home feature@extensible_dataset active local home feature@embedded_data active local home feature@bookmarks enabled local home feature@filesystem_limits enabled local home feature@large_blocks enabled local home feature@large_dnode enabled local home feature@sha512 enabled local home feature@skein enabled local home feature@edonr enabled local home feature@userobj_accounting active local home feature@encryption enabled local home feature@project_quota active local home feature@device_removal enabled local home feature@obsolete_counts enabled local home feature@zpool_checkpoint enabled local home feature@spacemap_v2 active local home feature@allocation_classes enabled local home feature@resilver_defer enabled local home feature@bookmark_v2 enabled local home feature@redaction_bookmarks disabled local home feature@redacted_datasets disabled local home feature@bookmark_written disabled local home feature@log_spacemap disabled local home feature@livelist disabled local home feature@device_rebuild disabled local home feature@zstd_compress disabled local home feature@draid disabled local home feature@zilsaxattr disabled local home feature@head_errlog disabled local home feature@blake3 disabled local home feature@block_cloning disabled local home feature@vdev_zaps_v2 disabled local home feature@redaction_list_spill disabled local home feature@raidz_expansion disabled local home feature@fast_dedup disabled local work feature@async_destroy enabled local work feature@empty_bpobj active local work feature@lz4_compress active local work feature@multi_vdev_crash_dump enabled local work feature@spacemap_histogram active local work feature@enabled_txg active local work feature@hole_birth active local work feature@extensible_dataset active local work feature@embedded_data active local work feature@bookmarks enabled local work feature@filesystem_limits enabled local work feature@large_blocks enabled local work feature@large_dnode enabled local work feature@sha512 enabled local work feature@skein enabled local work feature@edonr enabled local work feature@userobj_accounting active local work feature@encryption enabled local work feature@project_quota active local work feature@device_removal enabled local work feature@obsolete_counts enabled local work feature@zpool_checkpoint enabled local work feature@spacemap_v2 active local work feature@allocation_classes enabled local work feature@resilver_defer enabled local work feature@bookmark_v2 enabled local work feature@redaction_bookmarks disabled local work feature@redacted_datasets disabled local work feature@bookmark_written disabled local work feature@log_spacemap disabled local work feature@livelist disabled local work feature@device_rebuild disabled local work feature@zstd_compress disabled local work feature@draid disabled local work feature@zilsaxattr disabled local work feature@head_errlog disabled local work feature@blake3 disabled local work feature@block_cloning disabled local work feature@vdev_zaps_v2 disabled local work feature@redaction_list_spill disabled local work feature@raidz_expansion disabled local work feature@fast_dedup disabled local

I started out using Unraid many, many moons ago. I eventually switched to TrueNAS Scale, quickly regretted it, and have felt a bit stuck ever since. With the release of Unraid 7, I just can't take it anymore - I want to come back already! But, I noticed this line in the release notes: Nooooo! I've tried searching around the docs and this forum tonight for more information, but I'm still unclear on whether I can sidestep this limitation or not. So, I'll outline my scenario and pray that I don't have to wait for yet another release cycle before I can safely switch back to Unraid. I'm currently running TrueNAS 24.10.0.2. Aside from my "boot pool" (which is a mirrored pair of 216 GiB M.2 SSDs), I have 2 storage pools, "home" and "work". Topology is as follows: Home Data VDEVs - 1 x RAIDZ1 | 3 wide @ 10.91 TiB | Capacity: 21.68 TiB | Used: 19 TiB | Available: 2.68 TiB Work Data VDEVs - 1 x MIRROR | 2 wide @ 7.28 TiB | Capacity: 7.14 TiB | Used: 2.93 TiB | Available: 4.21 TiB Now, the way I interpret that line from the release notes is that if I just rebooted my server into Unraid 7, I would not currently be able to run a zfs export/import on those two pools and go on my merry way, right? If I'm wrong, please enlighten me. But if that is the case, I'm hoping there might be a workaround. I recently purchased 2x 24TB Exos drives that I was planning to add to my server this weekend. So... could I potentially do some data-juggling? E.g. boot into Unraid, set up the 2x 24TB drives as a new array, move the data from my TrueNAS home/work pools to the new Unraid array (whether from Unraid itself, or by temporarily booting back into TrueNAS), then destroy the old pools so that I can bring those disks into the new array? I'd be so happy to finally be able to switch back to Unraid this weekend if at all possible, so here's hoping we can find a way! Thanks in advance to anyone willing/able to provide some guidance.