[SCALE] [Solved]Use /dev/disk/by-path for creating ZFS pool? [Not supported]

Is there any way in the UI to configure a pool using /dev/disk/by-path/ paths instead of /dev/sd*?

Using /dev/sd* isn’t stable between boots depending on the order disks wake up and I have found it quite useful to have the slot identification in front of me when managing ZFS pools on other systems for replacing failed drives.

If the drive sdf has failed i have to look up which slot it is/was in, but if i see that pci-0000:07:00.0-sas-phy-0-lun7 has failed i know exactly which slot in the backplane is bad.

I could drop into the CLI to do this of course, but i’d rather manage things through the UI as much as possible, so if there’s some configuration option to switch what the UI displays for drive identifiers it’d be awesome to know.

No version of TrueNAS uses sd* (or da*) identifiers to create a pool; they all use partition UUIDs, which are stable. The GUI “helpfully” translates those to sd* identifiers, but those aren’t what’s used to create the pool. Run zpool status from the shell to confirm this.

okay, if that’s what its using behind the scenes that’s fine… I guess, but given that’s not show in the UI that’s not obvious.

So how do i get the UI to show me the by-path paths and not the raw device names? because my test server with Scale just shows me the names as sd*

I don’t believe that’s possible. As I said above, if you want to see what the system’s using under the hood, run zpool status (might need to prefix with sudo) at the shell.

1 Like

Hmm… well that’s disappointing.

really feels like a missed opportunity, unless that’s something that unlocks for their enterprise licenses because home gamers only deal with one or two installs so finding disks isn’t as big a deal as datacentres…

in any case i guess that’s the solution. “no you may not” isn’t the answer i wanted… but it will have to do unless i want to move back to debian and roll my own server again… no thank you! :smiley:

Their enterprise licenses are on their hardware and thus provide an “enclosure view” which maps disk to slot. Their community product doesn’t do this, though there are some third-party tools (e.g., GitHub - danb35/zpscan-scale: Light drive failure LEDs on SAS backplanes under TrueNAS SCALE) to try to address that issue.

1 Like