NVME serial number error

[irs]

I am trying to add NVME to new data pool but following error pops up.

Error: Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/middlewared/job.py", line 355, in run
await self.future
File "/usr/local/lib/python3.9/site-packages/middlewared/job.py", line 391, in __run_body
rv = await self.method(*([self] + args))
File "/usr/local/lib/python3.9/site-packages/middlewared/schema.py", line 975, in nf
return await f(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/middlewared/plugins/pool.py", line 638, in do_create
verrors.check()
File "/usr/local/lib/python3.9/site-packages/middlewared/service_exception.py", line 62, in check
raise self
middlewared.service_exception.ValidationErrors: [EINVAL] pool_create.topology: Disks have duplicate serial numbers: '' (mfid0, mfid1, mfid2).


although my NVME should be nvd0 but error displays different. what wrong I am doing.
Thx for reading and helping.

 

[NugentS]

Whats the hardware (please see forum rules)

 

[irs]

The Hardware is Dell R510

 

[irs]

I can see the Drive but can not use it as data pool. But can use it as pool-boot

 

[Patrick M. Hausen]

Which version of FreeNAS/TrueNAS are you running? How and on which version was the pool created?

From your error message I strongly suspect that it is refusing any modification of the pool topology because it cannot get the true serial numbers of your existing disks - not the serial of the new drive.

mfid0, ... look suspiciously like RAID volumes, which is not a supported configuration. Which leaves me to wonder how the pool was ever created in the first place.

Kind regards,
Patrick

 

[irs]

yes you are right I guess it was created on FreeNAS 7 when first pool was created. Now Installed True 13 and imported the pool.

 

[irs]

Acctually i want all the data should be copied on the new NVME as SAS drives are reaching to end of life.

 

[Patrick M. Hausen]

You can use the CLI to create a new pool, then export, then re-import via UI.

Could you post the output of this command? I'll probably answer with instructions tomorrow, though. Time for a good night's sleep here.

Code:

gpart show mfid0

 

[irs]

root@truenas[~]# gpart show mfid0=>
40 248774576 mfid0 GPT (119G)
40 532480 1 efi (260M)
532520 33554432 3 freebsd-swap (16G)
34086952 214663168 2 freebsd-zfs (102G)
248750120 24496 - free - (12M)

 

[irs]

root@truenas[~]# gpart show mfid1=>
40 1952448432 mfid1 GPT (913G)
40 88 - free - (44K)
128 4194304 1 freebsd-swap (2.0G)
4194432 1948254040 2 freebsd-zfs (929G)

 

[Patrick M. Hausen]

OK, got it. mfid0 is your boot drive, mfid1 the first of your data pool drives. How are you going to boot the system after the change? Do you plan to retire the mfi controller altogether? Can you connect the boot drive by some other means? New boot drive?

 

[irs]

I will use same mfid0 as boot drive or can be connected to SATA port directly and discard mfi controller

 

[irs]

I guess it is much simple to use SATA boot drive and NVME data storage.

 

[Patrick M. Hausen]

So let's get that pool created on your shiny new NVMe drive first.

Code:

gpart backup mfid1 | gpart restore -F nvd0
gpart resize -i 2 nvd0
gpart list nvd0
# look for the attribute "rawuuid" of partition number 2
zpool create <name of new pool> gptid/<rawuuid from above>
zpool export <name of new pool>

Then import the new pool from the UI. You can now proceed to copy your data.

As for the boot drive - yes, after moving everything to the new pool, I would disconnect/export the old pool from the UI. Then make sure everything is working as it should. Then export the configuration.

Next step: remove the mfi controller and all connected drives. Attach boot drive to on-board SATA.
In case it does not boot, perform a fresh install and reimport the saved configuration.

HTH,
Patrick