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.

UNRAID 7 importing ZFS pool incorrectly

Featured Replies

I've upgraded from 6.11.5 to 7.0, and after a lot of debugging here is what I see is happening. Everything works, but the UI shows my 4-drive RAIDZ1 incorrectly. The reason is because it maps the /dev/sdh1 drive in the UI but not the /by-partuuid/ drives. In the syslog, the zfs import command only includes /dev/sdh1 . You can see for the "hddm-storage" mirror import command it includes both /dev/sdc1 and /dev/sdb1 .

 

I figured out that it simply needs to import the pool like this "zpool import -d /dev/disk/by-id <pool-name>" but it doesn't and i can't force it to. The best I was able to do was start a new config with just the hddm-storage and not the hdd-storage 4-drive RAIDZ1, and manually import hdd-storage with "-d /dev/disk/by-id" , THEN add the pool, and THEN the UI shows all 4 drives BUT to the right it says "unable to mount this pool" so it's bugged THAT way instead.

 

How can I make it import the hdd-storage pool with "by-id" or at least all uniformly so that one drive (sdh1) isn't different from the others which then confuses the UI reporting?

 

image.png.c5e1626ec8143096723fd92a621d0e69.png

 

syslog_hdd-storage.thumb.jpg.9084834f2a31ff45d6b5b2d3f8d81f68.jpg

 

 

 

image.thumb.png.d8e5751a738c92c5182a69ef84a35e5f.png

 

 

image.thumb.png.c9745e3d215f859f18b1d4393327c398.png

  • Community Expert

Unraid always uses the device IDs, since the pools must be assigned, so it doesn't matter if they change, where/how was the pool created, and do you know why just one device is using /dev/sdX?

 

Please post the complete diagnostics after trying to start the array but you will likely need to recreate the pool.

  • Community Expert
4 hours ago, JorgeB said:

you will likely need to recreate the pool.

Another option, and possibly easier if you don't have a full backup, would be to offline one of the devices that is using the UUID, and then replace it with the same device using /dev/sdX1, then repeat for the remianing ones.

  • Author
7 hours ago, JorgeB said:

Another option, and possibly easier if you don't have a full backup, would be to offline one of the devices that is using the UUID, and then replace it with the same device using /dev/sdX1, then repeat for the remianing ones.


I tried offlining sdh and replacing with itself with its by-partuuid like the others. It said you can’t replace a drive with itself. 
 

Sdh is different because it is the drive that failed and i had to replace back under 6.11.5 i did a manual replace with another disk and it ended up going by dev/sdh instead of partuuid.

 

i can’t recreate the whole pool. Should be possible to remove the drive and add it back as a new drive but by its by-partuuid. It would have to resilver all over again. Would that work, Does unraid just want them all by partuuid?

Edited by 0edge

  • Community Expert
10 hours ago, 0edge said:

I tried offlining sdh and replacing with itself with its by-partuuid like the others.

No, the other way around, replace them all with /dev/sdX devices.

  • Author

You get an error that you can’t replace a drive with itself, like I said.


However, are you saying Unraid will simply not detect any drive that does not go by /dev/sdX? I’m starting to think that’s the case (i thought surely if they were all the same aka by partuuid, unraid would not be confused).

 

This is pretty shortsighted, especially since /dev/sdX is not actually recommended and people may be migrating their ZFS pools from elsewhere. Unraid should detect all drives as provided by the zpool status command…

  • Community Expert
1 hour ago, 0edge said:

(i thought surely if they were all the same aka by partuuid, unraid would not be confused)

Possibly, never tested.

 

1 hour ago, 0edge said:

You get an error that you can’t replace a drive with itself, like I said.

Try again after offlining the disk and then rebooting, if it still doesn't allow, try swapping vales wot a different disk so that the sdX IDs change

  • Author

I need to know if it’s enough for all of them to go by-partuuid before I replace the sdh drive with my spare to force it to be by-partuuid from the beginning. This will take time and resilvering. I suspect that’s the only thing that would work, if Unraid doesnt fix this bug. The offlining does not work because at the very least the replace command leads to a resilver, and i’m not resilvering 3 drives instead of just the 1 to make it by-partuuid like the others.

Edited by 0edge

  • Community Expert

Did a quick test and it does work if all devices are using by-partuuid.

  • Community Expert

Hmm, but it's also working for me with the same mismatched config you had:

 

image.png

  • Author

It works, it’s the UNRAID UI that displays it weird. My mirror says “this is a pool of 2 drives”, but the RAIDZ1 just shows the single sdh drive and the other 3 show up under “unassigned”

  • Community Expert
38 minutes ago, 0edge said:

It works, it’s the UNRAID UI that displays it weird. My mirror says “this is a pool of 2 drives”, but the RAIDZ1 just shows the single sdh drive and the other 3 show up under “unassigned”

I meant that the pool was imported correctly using the GUI, and it renamed all the devices to sdX

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.