root@tower:/# zpool status

pool: hdd

state: ONLINE

scan: scrub repaired 0B in 1 days 03:31:50 with 0 errors on Wed Jul 2 07:51:51 2025

config:

NAME STATE READ WRITE CKSUM

hdd ONLINE 0 0 0

raidz1-0 ONLINE 0 0 0

ata-ST14000NM001G-2KJ103_ZTM0CELT ONLINE 0 0 0

ata-ST14000NM001G-2KJ103_ZL2A9ZPK ONLINE 0 0 0

ata-ST14000NM001G-2KJ103_ZL2AM87Y ONLINE 0 0 0

ata-ST14000NM001G-2KJ103_ZLW2MKW8 ONLINE 0 0 0

raidz1-1 ONLINE 0 0 0

ata-ST14000NM001G-2KJ103_ZL2AN75Z ONLINE 0 0 0

ata-ST14000NM001G-2KJ103_ZTM0CD44 ONLINE 0 0 0

ata-ST14000NM001G-2KJ103_ZL2CJ47G ONLINE 0 0 0

ata-ST14000NM001G-2KJ103_ZL2BWGB3 ONLINE 0 0 0

errors: No known data errors

pool: nvme

state: ONLINE

scan: scrub repaired 0B in 00:18:50 with 0 errors on Tue Jul 1 04:38:51 2025

config:

NAME STATE READ WRITE CKSUM

nvme ONLINE 0 0 0

nvme0n1 ONLINE 0 0 0 (trimming)

errors: No known data errors

root@tower:/# zdb -l /dev/disk/by-id/ata-ST14000NM001G-2KJ103_ZLW2MKW8

failed to unpack label 0

failed to unpack label 1

failed to unpack label 2

failed to unpack label 3

root@tower:/# zdb -l /dev/disk/by-id/ata-ST14000NM001G-2KJ103_ZLW2MKW8-part1

------------------------------------

LABEL 0

------------------------------------

version: 5000

name: 'hdd'

state: 0

txg: 14043265

pool_guid: 5764276688367145208

errata: 0

hostname: 'tower'

top_guid: 7301316167661736821

guid: 16225184805902845557

vdev_children: 2

vdev_tree:

type: 'raidz'

id: 0

guid: 7301316167661736821

nparity: 1

metaslab_array: 266

metaslab_shift: 34

ashift: 12

asize: 56001724153856

is_log: 0

create_txg: 4

children[0]:

type: 'disk'

id: 0

guid: 9689511457415648178

path: '/dev/disk/by-id/ata-ST14000NM001G-2KJ103_ZTM0CELT-part1'

devid: 'ata-ST14000NM001G-2KJ103_ZTM0CELT-part1'

phys_path: 'pci-0000:2e:00.0-sas-phy2-lun-0'

whole_disk: 1

DTL: 9378

create_txg: 4

children[1]:

type: 'disk'

id: 1

guid: 10443037663573755569

path: '/dev/disk/by-id/ata-ST14000NM001G-2KJ103_ZL2A9ZPK-part1'

devid: 'ata-ST14000NM001G-2KJ103_ZL2A9ZPK-part1'

phys_path: 'pci-0000:2e:00.0-sas-phy7-lun-0'

whole_disk: 1

DTL: 9377

create_txg: 4

children[2]:

type: 'disk'

id: 2

guid: 12687003923774484790

path: '/dev/disk/by-id/ata-ST14000NM001G-2KJ103_ZL2AM87Y-part1'

devid: 'ata-ST14000NM001G-2KJ103_ZL2AM87Y-part1'

phys_path: 'pci-0000:2e:00.0-sas-phy4-lun-0'

whole_disk: 1

DTL: 9376

create_txg: 4

children[3]:

type: 'disk'

id: 3

guid: 16225184805902845557

path: '/dev/disk/by-id/ata-ST14000NM001G-2KJ103_ZLW2MKW8-part1'

devid: 'ata-ST14000NM001G-2KJ103_ZLW2MKW8-part1'

phys_path: 'pci-0000:2e:00.0-sas-phy1-lun-0'

whole_disk: 1

DTL: 9375

create_txg: 4

features_for_read:

com.delphix:hole_birth

com.delphix:embedded_data

labels = 0 1 2 3

I've always had the same partition labels X, X-part1, X-part2 - and this is my second zpool setup (Mirrored initially, now z1 w/4 disks)

Am I going to have an issue with importing these? I have 2 Unraid premium (or whatever) licenses, but very worried about trying to export/import in my running 7.2.4 system.

Edited July 11, 20251 yr by OneMeanRabbit

Pool should be importable with 7.2, and if it isn't it won't damage it, but post the output from

zpool status -LP

also

fdisk -l /dev/sdX

for one of the drives

root@tower:~# zpool status -LP

pool: hdd

state: ONLINE

scan: scrub repaired 0B in 1 days 03:31:50 with 0 errors on Wed Jul 2 07:51:51 2025

config:

NAME STATE READ WRITE CKSUM

hdd ONLINE 0 0 0

raidz1-0 ONLINE 0 0 0

/dev/sdi1 ONLINE 0 0 0

/dev/sdf1 ONLINE 0 0 0

/dev/sdk1 ONLINE 0 0 0

/dev/sdh1 ONLINE 0 0 0

raidz1-1 ONLINE 0 0 0

/dev/sdj1 ONLINE 0 0 0

/dev/sdm1 ONLINE 0 0 0

/dev/sdl1 ONLINE 0 0 0

/dev/sdg1 ONLINE 0 0 0

errors: No known data errors

pool: nvme

state: ONLINE

scan: scrub repaired 0B in 00:18:50 with 0 errors on Tue Jul 1 04:38:51 2025

config:

NAME STATE READ WRITE CKSUM

nvme ONLINE 0 0 0

/dev/nvme0n1p1 ONLINE 0 0 0

errors: No known data errors

root@tower:~# fdisk -l /dev/sdh1

Disk /dev/sdh1: 12.73 TiB, 14000435757056 bytes, 3418075136 sectors

Units: sectors of 1 * 4096 = 4096 bytes

Sector size (logical/physical): 4096 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Thank you @JorgeB. I'm assuming this means I'm not using whole disk, which was my intention. I'd love to understand anything I should expect due to not using whole disk. Specific export/import flags, "/dev/disk/by-id", UI capabilities, etc. Thank you again!

Edited July 12, 2025Jul 12 by OneMeanRabbit

9 hours ago, OneMeanRabbit said:

root@tower:~# fdisk -l /dev/sdh1

This would be for the disk, not the parotipnt, but it shoudl be fine based on the zpool status otuout.

9 hours ago, OneMeanRabbit said:

I'm assuming this means I'm not using whole disk,

Unraid also uses partitions, so that's ideal.

9 hours ago, OneMeanRabbit said:

I'd love to understand anything I should expect due to not using whole disk. Specific export/import flags, "/dev/disk/by-id", UI capabilities, etc.

You shouldn't have to do anything special, just make sure the pool is exported first, then on main, create a new pool with the name you want and 8 slots

assign the pool devices, leave the filesystem set to auto

start the array to import the pool

root@tower:/boot/syslinux# fdisk -l /dev/sdh

Disk /dev/sdh: 12.73 TiB, 14000519643136 bytes, 3418095616 sectors

Disk model: ST14000NM001G-2K

Units: sectors of 1 * 4096 = 4096 bytes

Sector size (logical/physical): 4096 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disklabel type: gpt

Disk identifier: 4F70D89C-52AE-6843-A532-A5B5765B03B7

Device Start End Sectors Size Type

/dev/sdh1 2048 3418077183 3418075136 12.7T Solaris /usr & Apple ZFS

/dev/sdh9 3418077184 3418093567 16384 64M Solaris reserved 1

Here is the proper command, thanks for clarification.

Regarding the import process in 7.1.4, I'm not wanting to have an array. Are your steps the same in that scenario - I tried this on 7.0 and I named it the same name as my zfs pool and it failed to import saying there was something there with the same name - I think?

In other systems, I wouldn't normally create anything just do zfs import {exported pool}

Thank you @JorgeB for your support and on a weekend at that!

Edited July 13, 2025Jul 13 by OneMeanRabbit

13 hours ago, OneMeanRabbit said:

Are your steps the same in that scenario

Yes, the steps are to import a pool.

13 hours ago, OneMeanRabbit said:

I tried this on 7.0 and I named it the same name as my zfs pool and it failed to import saying there was something there with the same name - I think?

It should work based on what I see, but woudl need the diags to see what the issue was.