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.

zfs disks with unassigned devices

Featured Replies

What are the best practices to create single zfs disk in Unassigned devices and then add them to the array later or pull devices out of the array and have them mountable in UDev?

Especially with pool names?

Something seems to be different with these disks:

image.thumb.png.a0c992c12c037597b7579c11660cbf64.png

 

1 is not mountable in Udev, even though it was mounted in the array. The other 2 are mountable. It seems to have something to do with the pool names. 

 

Here is the zpool import for sdc which was mounted in the array as disk7:

   pool: disk7

     id: 10683320168744557805

  state: ONLINE

action: The pool can be imported using its name or numeric identifier.

config:

 

disk7       ONLINE

  sdc1      ONLINE

 

How would I make it mountable in Udev?

 

How would I make future drives mountable in both Udev and Arrays?

 

Thanks

 

  • Author

I ran zpool import disk7 and now it shows up in Udev as disk7:

 

image.thumb.png.46927dfe24b41eeb1846a36920548ec9.png

 

but I feel like there will be a conflict when or if I add a disk7 to the array esp a zfs disk since the pool names will collide. 

 

I think this is how I ran into a problem with missing a mount that I posted about in another thread.

 

Edited by foo_fighter

If a zfs array disk was rebuilt, the old one won't mount together without changing the GUID first.

  • Author

I think it's more a matter of colliding mount points as removing a disk from the array and then using Udev to mount it will mount it to the original location. 

You have to use a zfs command line to change the mountpoint. 

 

Creating a zfs disk in Udev also has some mount point problems once it's put into the array and then taken back out.

 

Maybe these are pathological use cases. 

 

7 hours ago, foo_fighter said:

I think it's more a matter of colliding mount points as removing a disk from the array and then using Udev to mount it will mount it to the original location. 

You can change pool name during import, but still need to change the UUID first, this should work:

 

zpool reguid

 

You can then import the old disk using the ID, e.g.:


zpool import -N 9764320268923478566 temp
zfs set mountpoint=/x temp

 

 

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.