[EINVAL] pool_create.topology: Disks have duplicate serial numbers: '' (da0, da1).

[lmiksche]

Hi,
Found a similar thread, but doesnt answer my problem.

I run Truenas under proxmox and Indeed there seems to be duplicate (absolutely none) serial number in drive description of both drives. How can I change that? Im trying to add cache drive, but cant add any VDEV or anything because of this.

Thanks a lot!

 

[Arwen]

Are you using USB devices?

A great many USB devices from the same vendor have the same serial number. This can also applies to USB enclosures for SATA disks.

 

[lmiksche]

To clarify that proxmox didnt provide serials for system drive and data drive. Now I want to add cache drive, so i passed through NVMe (which has serial) and it complains about those first two having same serial, so i cant add anything.

 

[Whattteva]

To clarify that proxmox didnt provide serials for system drive and data drive. Now I want to add cache drive, so i passed through NVMe (which has serial) and it complains about those first two having same serial, so i cant add anything.

You didn't provide any information other than Proxmox and no serial numbers. You didn't even bother to link the other thread. We can only guess what your setup is and USB tends to exhibit this behavior. Perhaps provide more information before you snap at someone who's just trying to help?

 

[Ericloewe]

<Moderator hat>
@lmiksche, if you want help you must:

1. Participate constructively - answer questions and attempt to clarify things in good faith.
2. Be respectful of other users, especially when they took a few minutes out of their day to try to help you.
3. Communicate clearly - be specific, add context, illustrate as needed, ...

I suggest you take a deep breath and provide details of your system, in particular how storage is configured on the VM.
</Moderator hat>

 

[Arwen]

There was no link to any other post. With the limited information I asked a reasonable question. Further, my question was related to the existing 2 drives which seemed to have prevented the new drive.

Anyway, good luck.

 

[jgreco]

I run Truenas under proxmox and Indeed there seems to be duplicate (absolutely none) serial number in drive description of both drives. How can I change that? Im trying to add cache drive, but cant add any VDEV or anything because of this.

Proxmox and virtual disk devices do not mix in many cases. You need to use PCIe passthru of the disk controller in order to make this work correctly. Please see the guidance at

"Absolutely must virtualize FreeNAS!" ... a guide to not completely losing your data.

[---- 2018/02/27: This is still as relevant as ever. As PCIe-Passthru has matured, fewer problems are reported. I've updated some specific things known to be problematic ----] [---- 2014/12/24: Note, there is another post discussing how to deploy a small FreeNAS VM instance for basic file...

www.truenas.com

 

[lmiksche]

Proxmox and virtual disk devices do not mix in many cases. You need to use PCIe passthru of the disk controller in order to make this work correctly. Please see the guidance at

"Absolutely must virtualize FreeNAS!" ... a guide to not completely losing your data.

[---- 2018/02/27: This is still as relevant as ever. As PCIe-Passthru has matured, fewer problems are reported. I've updated some specific things known to be problematic ----] [---- 2014/12/24: Note, there is another post discussing how to deploy a small FreeNAS VM instance for basic file...

www.truenas.com

That is exactly what I have done as stated above. But because the 1st 2 drives (system +DATA(Z2)) dont have any serials the GUI refuses to add cache or any other VDEV. It can clearly see the serial of passed through NVMe Drive. Someone suggested it could possibly be done from comman line, but this kind of linux escapes me.

 

[Ericloewe]

If the disks themselves don't have serial numbers, then one of the following is likely:

1. There's Proxmox trickery afoot
2. The controller wasn't actually passed through
3. You have some obscure disks which don't behave well

While it's probably possible to resolve the immediate issue, it's suggestive of a larger problem, so it's worth looking into it. Though it might be more of an issue the Proxmox forums can help with, unless someone here who's familiar can help.

 

[Whattteva]

I use Proxmox myself and haven't seen this issue, at least not with the entire HPE HP220 controller passed through. Perhaps it might be a unique issue with your particular type of HBA. What card are you using?

 

[lmiksche]

Sorted... in VM config of server node, you need to add the serial manually. I think my mistake was not to pass through whole controller but only the RAID6 drive as I found the ZFS performance pretty bad after testing and at the time wasnt sure about my system drives, but I know now that they are on separate controller. But there is an easy fix.

In you VM config file just add the serial at the end of each line that concerns drives as fallows:

scsi0: storage1:vm-104-disk-0,size=32G,serial=12345

 

[Ericloewe]

I think my mistake was not to pass through whole controller but only the RAID6 drive

That, as previously indicated, is known to be extremely unreliable. It also bypasses many of ZFS' protections, so it is highly not recommended.