February 1, 20251 yr 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: Quote Currently unable to import TrueNAS pools. This will be fixed in a future release. 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.
February 1, 20251 yr Community Expert Current import support will depend mostly on which version the pools were created, please post the output from: zpool status -LP and zpool get all <pool name> | grep feature the latter for both data pools
February 1, 20251 yr Author 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
February 1, 20251 yr Community Expert Both pools should import with Unraid 7 without any issues, just add two new pools using the GUI with the correct number of slots, assign the respective devices, leave the fs set to auto, and start the array.
March 3, 20251 yr I join this discussion because I've the same "issue" and I want to be back to my beloved Unraid. I attach the result of the commands above. Could I also have Green Light to go?
March 4, 20251 yr Community Expert 14 hours ago, kiwivda said: Could I also have Green Light to go? The pool layouts are fine, but you have some flags enabled that are only supported by openZFS 2.3, so you'll need to wait for Unraid 7.1, but should not need to wait long, the first public beta is expected later this month.
March 5, 20251 yr I have also done this thing and would love to know whether or not I have to wait. Which flags meant that I would have to wait? Sorry for asking you to help with parsing this. I seem to be joining others on finally wanting to understand my server.
March 5, 20251 yr Community Expert 6 hours ago, valek879 said: Which flags meant that I would have to wait? In terms of flags it's OK, but cannot see the partitions, are you using zpool status -LP Is this from TN Core or Scale?
March 11, 20251 yr I am on Scale and I am pretty certain I ran zpool status -LP I copied everything directly from this thread. I actually only have a single partition. Your reaction makes it feel like maybe this is not the norm. I am actually asking because I don't have a clue how my server works and I am really trying to find a solution that would let me do more with it and understand what I am doing when I do it. I hope this clarifies things a little bit. I can of course run anything again should you need it.
March 11, 20251 yr Community Expert 2 hours ago, valek879 said: I am on Scale If you are on Scale, post the output from: fdisk -l /dev/sdX Replace X with one of the pool member devices.
March 19, 20251 yr Hello friends, I'm planning on migrating from Scale to Unraid as well. I only have 1 vdev with 4 drives in the pool, and I want to make sure I can migrate it over.
March 19, 20251 yr Community Expert 7 hours ago, Shamrock013 said: I only have 1 vdev with 4 drives in the pool, and I want to make sure I can migrate it over. It should always be fine with 7.1.0-beta.1, if you want to use 7.0, On 2/1/2025 at 11:21 AM, JorgeB said: please post the output from: zpool status -LP and zpool get all <pool name> | grep feature
March 19, 20251 yr 3 hours ago, JorgeB said: It should always be fine with 7.1.0-beta.1, if you want to use 7.0, pool: boot-pool state: ONLINE scan: scrub repaired 0B in 00:00:51 with 0 errors on Tue Mar 18 03:45:52 2025 config: NAME STATE READ WRITE CKSUM boot-pool ONLINE 0 0 0 /dev/sda3 ONLINE 0 0 0 errors: No known data errors pool: disk 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 scan: scrub repaired 0B in 09:45:54 with 91 errors on Mon Mar 3 23:48:42 2025 config: NAME STATE READ WRITE CKSUM disk ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 /dev/sdb1 ONLINE 0 0 0 /dev/sdc1 ONLINE 0 0 0 /dev/sdd1 ONLINE 0 0 0 /dev/sde1 ONLINE 0 0 0 disk feature@async_destroy enabled local disk feature@empty_bpobj active local disk feature@lz4_compress active local disk feature@multi_vdev_crash_dump enabled local disk feature@spacemap_histogram active local disk feature@enabled_txg active local disk feature@hole_birth active local disk feature@extensible_dataset active local disk feature@embedded_data active local disk feature@bookmarks enabled local disk feature@filesystem_limits enabled local disk feature@large_blocks enabled local disk feature@large_dnode enabled local disk feature@sha512 enabled local disk feature@skein enabled local disk feature@edonr enabled local disk feature@userobj_accounting active local disk feature@encryption enabled local disk feature@project_quota active local disk feature@device_removal enabled local disk feature@obsolete_counts enabled local disk feature@zpool_checkpoint enabled local disk feature@spacemap_v2 active local disk feature@allocation_classes enabled local disk feature@resilver_defer enabled local disk feature@bookmark_v2 enabled local disk feature@redaction_bookmarks enabled local disk feature@redacted_datasets enabled local disk feature@bookmark_written enabled local disk feature@log_spacemap active local disk feature@livelist enabled local disk feature@device_rebuild enabled local disk feature@zstd_compress enabled local disk feature@draid enabled local disk feature@zilsaxattr active local disk feature@head_errlog active local disk feature@blake3 enabled local disk feature@block_cloning active local disk feature@vdev_zaps_v2 active local disk feature@redaction_list_spill enabled local disk feature@raidz_expansion enabled local disk feature@fast_dedup enabled local
March 21, 20251 yr Community Expert 7 minutes ago, Shamrock013 said: what do you think regarding what I pasted in my previous post? Sorry, missed your post, that pool won't import with 7.0.x because of this: On 3/19/2025 at 11:50 AM, Shamrock013 said: disk feature@redaction_list_spill enabled local disk feature@raidz_expansion enabled local disk feature@fast_dedup enabled local These require OpenZFS 2.3+, so it would only import with 7.1.0-beta.1 or newer.
March 21, 20251 yr No worries whatsoever. That kind of stinks. I'm not sure if you'd be able to assist, but is this solution possible? I pull a drive from my current pool, put it in new hardware, set that up with Unraid, migrate data to that drive, and then move the rest of my drives over and use one as parity.
March 21, 20251 yr Community Expert 4 minutes ago, Shamrock013 said: I pull a drive from my current pool, put it in new hardware, set that up with Unraid, migrate data to that drive, and then move the rest of my drives over and use one as parity. That would work assuming all the data fits in one drive, but I would just use 7.1.0-beta.1, it's beta, but there aren't many big code changes vs 7.0.1, I think it's fairly safe to use, I'm using it with both my main servers.
March 21, 20251 yr 6 minutes ago, JorgeB said: That would work assuming all the data fits in one drive, but I would just use 7.1.0-beta.1, it's beta, but there aren't many big code changes vs 7.0.1, I think it's fairly safe to use, I'm using it with both my main servers. Is there documentation I can follow for that? I've barely scratched the surface with Unraid and haven't touched 7.1 yet to see what it is like.
March 21, 20251 yr Community Expert 21 minutes ago, Shamrock013 said: haven't touched 7.1 yet to see what it is like. It's very similar to 7.0, adds Wi-Fi support and few other things, but user interaction is basically the same as 7.0
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.