HV: Proxmox Virtual Environment 9.0.11 VM: TrueNAS Scale: 25.10.0 - Goldeye Drives NVME SSD: NVME WDC 64Gb - Boot drive HDD : WD Drives Data Mirror 4Tb SSD: Kingston SA400 120Gb I’m trying to add the Kingston SSD as cache drive in an existing pool. I always get this error, even though this is…

Do NOT pass virtual drives from Proxmox (other than the VM itself); pass through the SATA/SAS controller and NVMe drives as PCIe devices—and blacklist them in Proxmox.

Ohh I finally have the proper passthrough. I added the entire SATA Controller to the TrueNas VM as PCI Device so the TrueNAS will have a complete control with my SATAs. Thank you

I’m having a similar problem, but I’m using an ACASIS 5-bay RAID 0 with two 14TB Seagate IronWolf HDDs connected via USB to a miniPC with an i5 processor, 8GB of RAM, and 256GB of storage, running TrueNAS-SCALE-25.10.0.1. Could you help me with this? Hard Drive IronWolf 14 TB (A) CrystalDiskInfo …

[image] Gil_Crespo: ACASIS 5-bay RAID 0 with two 14TB Seagate IronWolf HDDs connected via USB to a mini-PC This is your problem, and there’s no solution other than using hardware that is suitable for ZFS, namely either a PC that is large enough to host drives internally, attached to motherboa…

Just out of curiosity: you mentioned RAID 0 However, the external enclosure presents the HDDs individually, and you can read the individual drive information with CrystalDiskInfo ?

I’m having this same error attempting to add a disk as a spare. My drives are direct attached via SCSI, no external bay, no USB, and TrueNas is not virtualized. Does anyone have any ideas why this may be the case still? I submitted a bug report, NAS-139550, but they thought it was due to my “disk …

Same error with Hyper-V and Truenas 25.10.x and 26.01.x. Drives are passed, seriald are visible in menu “DISKS” but error… BUT! With 25.04.2.6 ALL WORKED! The coders broke something…. PS: HW: Xeon x99 board, E5-2697v3 CPU, 128 GB of DDR4 RAM, INTEL SATA controller with AHCI mode, 6x500GB SATA dr…

Andrey, See my post in another thread about this issue. Good ol - Disks have duplicate serial numbers: None - But they don't? - #20 by HKfan The method of getting drive serial numbers was changed between 25.04 and 25.10, making it incompatible with your virtualization.

I think I ran in the same problem with PVE, having fully virtualized TrueNAS test systems here, and since 25.10 it has started to act up. Though I found a solution, for the test system use case, I was using virtual SCSI disks so far, but this throws a None serial now, so switched to SATA and seems…

On my old system that does not support IOMMU (groups), I resolved this issue without passing through a controller, with just disk passthrough. The solution was to add additional “serial=” to VM conf. nano /etc/pve/qemu-server/123.conf ... scsi1: /dev/disk/by-id/ata-STmodel_456,serial=456,backup=0…

Error: topology Disks have duplicate serial numbers: None (sda, sdb, sdc)

TrueNAS General

SmallBarky February 2, 2026, 10:13pm 8

Try the following thread. Similar issues. You didn’t list detailed hardware and I can’t see what info was submitted to the Jira ticket since I don’t work for TrueNAS. Disk shelf has to be related to your chassis.

Topic		Replies	Views
Topology: Disks have duplicate serial numbers: None (sdb, sdc) TrueNAS General	46	4809	July 12, 2026
TrueNAS 25.10.1 is Now Available! Announcements	49	8141	February 22, 2026
Disks have duplicate serial numbers: None (sdi, sdj) TrueNAS General SCALE	19	637	June 16, 2026
TrueNAS Scale boot-pool Error: topology Disks have duplicate serial numbers TrueNAS General SCALE , pool	8	296	January 12, 2026
Good ol - Disks have duplicate serial numbers: None - But they don't? TrueNAS General SCALE	26	1371	March 31, 2026

Error: topology Disks have duplicate serial numbers: None (sda, sdb, sdc)

Related topics