Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Wrong Pool State - orphan ZFS subpool

Featured Replies

I upgraded from v7.0.1 to v7.1.1 and I had a fully pool based UNRAID configuration that was confirmed working with no errors that I could see or was available in the UI. After downloading my old configuration before doing the upgrade and sending it, I can no longer start my UNRAID pools and I get the following error:

Wrong Pool State

styx~cache - orphan ZFS subpool

Attached are the diagnostics and overview of the configuration, I have confirmed that the drives are in the same location on the pools and all are displaying correctly and are physically powering on. The basic overview of the configuration is that the drives are encrypted with a keyfile and are using zfs with a metedata pool (appdata), the main pool (styx), and subpool (styx-cache)

Screenshot from 2025-05-09 03-33-32.png

tower-diagnostics-20250509-0330.zip

Solved by JorgeB

  • Author

Also I completely understand there are two 10TB in the pool, they will be upgraded soon to 14TB but I haven't got the chance lately or the money.

  • Community Expert

Post the output from

 

zpool import

 

  • Author
root@Tower:~# zpool import
no pools available to import
root@Tower:~#

 

Edited by Dr.Kerberos

  • Community Expert

You are using encryption, so you need to start the array first or manually decrypt the devices.

  • Author

Yeah the slight problem is that I cannot start the array because of the error, I can manually decrypt the array and get back to you, but that's the interesting part, is that I have never been required to do that before. I'll do that know and get back to you.

  • Author
  pool: appdata
    id: 17249144222958010068
 state: ONLINE
status: Some supported features are not enabled on the pool.
        (Note that they may be intentionally disabled if the
        'compatibility' property is set.)
action: The pool can be imported using its name or numeric identifier, though
        some features will not be available without an explicit 'zpool upgrade'.
config:

        appdata                                   ONLINE
          mirror-0                                ONLINE
            fb467038-b962-4fa8-a847-4eb6ec77fc64  ONLINE
            2c28b1c5-a306-4593-93cf-62a066a0c6d5  ONLINE

  pool: styx
    id: 834650131511755417
 state: ONLINE
status: One or more devices contains corrupted data.
action: The pool can be imported using its name or numeric identifier.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
config:

        styx                                      ONLINE
          raidz2-0                                ONLINE
            f2f66545-c20c-4835-917a-c352f1533681  ONLINE
            3c5a3e0b-0657-4e1a-a19a-7df401449b00  ONLINE
            3e7210a4-8962-4598-81f7-17aa36993b49  ONLINE
            1240f020-cd4b-4254-9668-1cdcb47a40a6  ONLINE
            566cd016-9fc4-4db8-be8a-bc6924182c30  ONLINE
            3eaf16da-62b0-41d5-a4f1-2c7f4d80f28c  ONLINE
            7e8c2d37-424f-42cc-8900-cf05db3540ea  ONLINE
        cache
          c5d615b2-58b7-4c87-8091-cc4ef8536e23
          b2f6751c-4dd3-440d-a4ba-172fa191ed0c

 

  • Author
root@Tower:/dev/shm# zpool import -o readonly=on styx
root@Tower:/dev/shm# zpool status styx
  pool: styx
 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 14:50:40 with 0 errors on Thu May  1 11:50:42 2025
config:

        NAME                                      STATE     READ WRITE CKSUM
        styx                                      ONLINE       0     0     0
          raidz2-0                                ONLINE       0     0     0
            f2f66545-c20c-4835-917a-c352f1533681  ONLINE       0     0     0
            3c5a3e0b-0657-4e1a-a19a-7df401449b00  ONLINE       0     0     0
            3e7210a4-8962-4598-81f7-17aa36993b49  ONLINE       0     0     0
            1240f020-cd4b-4254-9668-1cdcb47a40a6  ONLINE       0     0     0
            566cd016-9fc4-4db8-be8a-bc6924182c30  ONLINE       0     0     0
            3eaf16da-62b0-41d5-a4f1-2c7f4d80f28c  ONLINE       0     0     0
            7e8c2d37-424f-42cc-8900-cf05db3540ea  ONLINE       0     0     0
        cache
          c5d615b2-58b7-4c87-8091-cc4ef8536e23    ONLINE       0     0     0
          b2f6751c-4dd3-440d-a4ba-172fa191ed0c    ONLINE       0     0     0

errors: No known data errors
root@Tower:/dev/shm# 

 

  • Community Expert
  • Solution

There's an issue with the cache subpool cfg, click the first styx pool device, then "remove pool"

back on main, create a new pool with the same name and 9 slots
assign all the pool devices together, don't create subpools, leave the filesystem set to auto
start the array to import the pool

  • Author

I think we are getting somewhere but I don't know if it's properly detecting the filesystem. I might have done something wrong in your instructions.

Screenshot from 2025-05-09 04-40-00.png

  • Author

Fixed it, it was because I exported the pool but forgot the re-encrypt the pool and I guess it tripped up UNRAID when I started the array. You comment solved my issue thank you. Also if you could how did you know it was a config issue with cache sub-pool, and how did it occur because all I did was upgrade to a newer version.

Screenshot from 2025-05-09 04-48-39.png

  • Community Expert
56 minutes ago, Dr.Kerberos said:

Also if you could how did you know it was a config issue with cache sub-pool, and how did it occur because all I did was upgrade to a newer version.

 

The subpool cfg was set to one device:

 

diskFsWidth="1"

 

Most likely, just changing that to 2 and rebooting would have resolved the issue, but just in case there were other problems, reimporting is better to make sure all is correct, and it happened now because previous releases were more lax with these things, now they must be correct.

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.