Error Creating Pool - Disks have duplicate serial numbers

[pixelwave]

I recently decided to start over with my HDD pool and deleted it. Now when I want to create a new one i get the error message:

"[EINVAL] pool_create.topology: Disks have duplicate serial numbers: 'S2GMNCAGB03832B' (nvme0n1, nvme0n1)."

Those disks are in the system and the pool I want to create with sdb+sdc+sdd:

And I have a boot pool with a partioned NVMe M2(32GB boot / rest zfs pool) + 60GB SSD:

 

[NugentS]

Did you reboot. There is an issue on Scale & Core (cos I found it yesterday on Core) where disks don't get updated.
After deleting the pool, reboot the server

 

[pixelwave]

Did you reboot. There is an issue on Scale & Core (cos I found it yesterday on Core) where disks don't get updated.
After deleting the pool, reboot the server

Yes did this already many times. It actually fixed an issue I had in the very beginning when initially setting up SCALE (also replied to that thread) but this issue now seems different?

Maybe because I installed the system on a partition of the NVMe and the second partition for storage ... ?

 

[NugentS]

The boot pool shouldn't matter - its different disks
Try creating the pool on the command line - does that work?

 

[pixelwave]

Ok seems to be because of that ... I detached the NVMe from the boot mirror pool and after that I was able to create the pool using the 3x 3.5" HDDs.

Bad thing now I can not reattach the partition from the NVMe .. at least via GUI. It is not selectable:

 

[NugentS]

TrueNAS works in whole disks.
If you want to add partitions to pools, then the only way is the commandline

 

[pixelwave]

What is the command to add the "nvme0n3" partition to the boot-pool via CLI?

 

[NugentS]

Look up zpool add "PoolName" .............................................


Caveat - use the GPTID and not the /dev/nvme'n' as sometimes things can change on a boot - which is bad

 

[pixelwave]

It worked with:

zpool attach boot-pool /dev/sda3 /dev/nvme0n1p3

Since I am still learning a little help for newbies like me ... to find the partitions use this command path:

cd / # navigate to root path
cd /dev # navigate to dev path
ls # lists content

Some more resource:

Adding TrueNAS Boot Mirror Disk via CLI

You can configure a mirrored boot pool for your TrueNAS system using the CLI.

blog.stefandroid.com

 

[pixelwave]

Look up zpool add "PoolName" .............................................


Caveat - use the GPTID and not the /dev/nvme'n' as sometimes things can change on a boot - which is bad

How to use the GPTID?

 

[pixelwave]

That is the output of zpool status:

 

[pixelwave]

Is the part:

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.

... normal for the boot-pool or do I have to do something there? I can imagine that maybe the boot-pool is intentionally a bit more conservative?

 

[pixelwave]

Also is there a way to change the order of the boot-pool ... I want to have the nvme as primary boot.

What I did know was detach the ssd (sda3 ... after finishing of nvme resilvering) and then reattach with:

zpool attach boot-pool /dev/nvme0n1p3 /dev/sda3

 

[NugentS]

Honestly I am not sure - its not something I have done exactly (similar, but not quite the same)
GPTID are the xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx. They could be found with glabel status in core - but you are running scale, so I don't know

 

[NugentS]

The boot pool order is BIOS dependant, nothing to do with TN, but the order in which the BIOS attempts the boot