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.

Zpool unmountable after New Config

Featured Replies

Hi all,

Hoping to get some expert advice here. I created a New Config under Tools to swap out a single drive that was in my Array Devices. I swapped out this single drive to two new, 18 TB drives. 

I already had a running Zpool with three 12 TB drives formatted as zfs. The New Config was started and the two 18 TB drives are expectedly reporting Unmountable: Unsupported partition layout as they are new drives. However, the big issue is that my active zpool now shows as Unmountable: Unsupported partition layout. 

It would be great to not have to reformat the zpool as I have data I really would like to not lose. Thanks in advance!normasraid-diagnostics-20231126-2031.zip

Solved by JorgeB

  • Community Expert

Post the output of:

zpool import

 

  • Author

I had a cache drive used before, could that be it? It looks like my cache drive got relabeled as sdg. image.thumb.png.c2939ea24071879ab4ea5c7ff3d23290.png

 

Output of zpool import

 

~# zpool import
   pool: zpool
     id: 15075536597851971656
  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:

        zpool       ONLINE
          raidz1-0  ONLINE
            sdc1    ONLINE
            sdd1    ONLINE
            sdb1    ONLINE
        cache
          sdb

 

Edited by norma_567

  • Author

I noticed the drive sdg is different that the output of the cache text above with sdb. opened up my server and noticed that drive had become unplugged. plugged it back in and the correct cache is in that slot. new zpool import results below

 

~# zpool import
   pool: zpool
     id: 15075536597851971656
  state: ONLINE
 action: The pool can be imported using its name or numeric identifier.
 config:

        zpool       ONLINE
          raidz1-0  ONLINE
            sdd1    ONLINE
            sde1    ONLINE
            sdc1    ONLINE
        cache
          sdb

 

  • Author

i ran the following command: zpool import zpool and all my shares are mounted, but I am now seeing: 

 

Unmountable: Unsupported or no file system

 

any idea how to correct?

Edited by norma_567

  • Community Expert
10 hours ago, norma_567 said:

I had a cache drive used before, could that be it? It looks like my cache drive got relabeled as sdg.

You cannot have the zpool pool cache vdev assigned to a different Unraid pool, you need to create a new pool with all the devices and re-import it, see here for how to re-import a pool.

  • Author

Thanks for the reply! I noticed in bullet 3 of that link that it wants me to reformat the array. Won't I loose my data?

I am wondering if I need to back up all the data to a different set of drives before doing this. The data is accessible via CLI and could be moved to a different drive.

Thoughts?

  • Community Expert
1 hour ago, norma_567 said:

Thanks for the reply! I noticed in bullet 3 of that link that it wants me to reformat the array. Won't I loose my data?

Look only at the pool import section in the end, nothing else.

  • Author

I am looking at those steps but something isn't lining up as I am still seeing Unmountable: Unsupported or no file system

 

Below you will see the exact steps I did from the forum post referenced and actions/observations taken

 

Steps done:

  • when all the vdev(s) are added to the pool stop the array, now you need to re-import the pool
    • they are all already added correct(didnt need to do anything)? stopped array via GUI
  • unassign all pool devices
    • removed all drives for the cache and zpool via GUI
  • start array (check the "Yes I want to do this" box)
    • "Yes I want to do this" box is not present when array is stopped, it only shows up once I start it. Then it shows up due to my new drives under a standard array actually need formatting, did this then went to next step
    • screenshot when array is stopped
      • image.thumb.png.e524c8ea636f11ec97bb7641950269c6.png
    • screenshot when array is started
      • image.thumb.png.7a9fb85a07da29e386fd0a2ef60bd33f.png
  • stop array
    • clicked stop array after stopping parity sync for the drives in the main array
  • re-assign all pool devices, including the new vdev(s), assign all devices sequentially in the same order as zpool status shows, and don't leave empty slots in the middle of the assigned devices.
    • added all zpool drives back to their orginal slots and the cache drive via the GUI
  • start array
    • started array in maintenance mode and it doesnt show Unmountable: Unsupported or no file system but when out of maintenance mode it shows up again

 

- I feel like I am missing something simple here? Do I need to change anything under the device settings? I have been forcing it to pick zfs as the file system instead of auto and setting the drives to never spin down to fully utilize the benefits of zfs.

- Could it also be the cached drive? Do I need to remove it from the zpool entirely? Then add it back? If so, how do you do that?

normasraid-diagnostics-20231128-1513.zip

Edited by norma_567

  • Community Expert

Looking at the syslog you are not assigning the cache vdev together with the pool, post again the output of

zpool import 

so that I can post step by step instructions.

  • Author

I ran a variation of commands to get the info you are looking to see, had to run zpool status.

After work today, my secondary array will finish it's parity sync. I am tempted to just copy everything over and start this zpool from scratch but would rather learn the correct way to do things. Thank you for your continued help on this!

 

root@normasraid:~# zpool import
no pools available to import
root@normasraid:~# zpool export zpool
cannot unmount '/mnt/zpool/system': pool or dataset is busy
root@normasraid:~# zpool status
  pool: zpool
 state: ONLINE
  scan: scrub repaired 0B in 03:41:58 with 0 errors on Tue Nov 28 00:23:48 2023
config:

        NAME        STATE     READ WRITE CKSUM
        zpool       ONLINE       0     0     0
          raidz1-0  ONLINE       0     0     0
            sdd1    ONLINE       0     0     0
            sde1    ONLINE       0     0     0
            sdc1    ONLINE       0     0     0
        cache
          sdb       ONLINE       0     0     0

errors: No known data errors
root@normasraid:~# 

 

Edited by norma_567

  • Community Expert
  • Solution

Leave the zpool exported, then delete the cache pool, change the zpool slots to 4, assign all 4 devices to the same pool (zpool), leave the fs set to auto, start array, if it doesn't mount post new diags.

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.