Pools Imported As SD(X)

TrueNAS General
1

I “migrated” from CORE to SCALE, had to do a fresh install (because the upgrade wouldn’t work) and restore my backup now my pools have been imported from their BSD gptid to the Linux /dev/sd(X). I manged to get one of the pools back to /dev/disk/by-partuuid (which I understand is the default) by exporting and re-importing it and while my other pool is still imported as /dev/disk/by-id that is not my immediate concern as I’ll get to that eventually.

My main concern is the boot-pool because I cannot figure out for the life of me how this is mounted or imported. There is nothing in /data/zfs/zpool.cache and in the GUI under system->boot I have no way to detach or attach only replace. I don’t think a re-install would work because as soon as I restore the backup I imagine this would happen again. So how do I get my boot-pool back to default?

2

This is expected (Component Naming | TrueNAS Documentation Hub) and the rest of what you’re doing here is not neccessary.

3

This is fine then?

  pool: boot-pool
 state: ONLINE
  scan: scrub repaired 0B in 00:00:06 with 0 errors on Fri Jan 24 15:11:43 2025
config:

	NAME        STATE     READ WRITE CKSUM
	boot-pool   ONLINE       0     0     0
	  mirror-0  ONLINE       0     0     0
	    sdh3    ONLINE       0     0     0
	    sdj3    ONLINE       0     0     0

errors: No known data errors
4

Yes, it is. For the boot pool it used to be the same in CORE:

  pool: boot-pool
 state: ONLINE
  scan: scrub repaired 0B in 00:00:12 with 0 errors on Mon Jan 27 03:45:14 2025
config:

	NAME        STATE     READ WRITE CKSUM
	boot-pool   ONLINE       0     0     0
	  mirror-0  ONLINE       0     0     0
	    ada4p2  ONLINE       0     0     0
	    ada5p2  ONLINE       0     0     0

Only storage pools managed by TrueNAS use the UUID based scheme.

5

Only storage pools managed by TrueNAS use the UUID based scheme.

Well…that’s not entirely true:

  pool: thor
 state: ONLINE
  scan: scrub repaired 0B in 00:08:15 with 0 errors on Fri Jan 24 00:23:11 2025
config:

	NAME                                            STATE     READ WRITE CKSUM
	thor                                            ONLINE       0     0     0
	  mirror-0                                      ONLINE       0     0     0
	    nvme-WD_Blue_SN5000_4TB_XXXXXX1-part2  ONLINE       0     0     0
	    nvme-WD_Blue_SN5000_4TB_XXXXXX2-part2  ONLINE       0     0     0

errors: No known data errors

I’ll fix this later by exporting and re-importing. If the boot-pool is supposed to be like this then I guess this is case closed.

6

I am a bit confused by your reply. The boot pool and the boot pool only uses plain short device names like ada0p2 (CORE) or sda2 (SCALE).

All other pools should use a UUID based device scheme. If your particular pool doesn’t then something is wrong but that does not contradict what I wrote. Boot pools use traditional short partition names.

7

In you initial post, were you talking about sd(x) labels in the UI or command line? This is from a typical install:

  pool: tank
 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 00:00:37 with 0 errors on Mon Jan 20 07:25:40 2025
config:

        NAME                                      STATE     READ WRITE CKSUM
        tank                                      ONLINE       0     0     0
          mirror-0                                ONLINE       0     0     0
            c9ef479e-f4c1-4e05-bd8c-7206f7aa11f5  ONLINE       0     0     0
            551195a2-8d8b-49c1-a238-3bfc1c8af4e3  ONLINE       0     0     0

errors: No known data errors
qe-realmini% zpool status boot-pool
  pool: boot-pool
 state: ONLINE
  scan: scrub repaired 0B in 00:04:09 with 0 errors on Sat Jan 25 03:49:11 2025
config:

        NAME        STATE     READ WRITE CKSUM
        boot-pool   ONLINE       0     0     0
          sde3      ONLINE       0     0     0

image
image756×436 15.5 KB

8

I’m sorry I guess my OP was confusing I was referring to the labels in the CLI specifically the output of zpool status and more specifically the boot-pool. As for my thor pool I have high confidence that exporting and re-importing will bring it back to the default /dev/disk/by-partuuid as that is what fixed my other pool. Thanks.