Good ol - Disks have duplicate serial numbers: None - But they don't?

TrueNAS General
21

I wonder where can one do this? Should we organize a petition.. :slight_smile:

I have the same issue with multiple systems (hardware or virtualised TrueNAS installations), and where things have worked perfectly and flawlessly in this regard for me, for years.. Now I have to start reconsidering whether I can use TrueNAS at all going forward with versions 25.10 and newer.

Btw. even the midclt call disk.query shows that the disks have unique serial numbers, and the GUI portion still fails to create a pool complaining about duplicate serial numbers…
For example:

# midclt call disk.query | jq
[
{
“identifier”: “{serial_lunid}BTHC601206EQ480MGN_55cd2e404c18b6fe”,
“name”: “sdb”,
“subsystem”: “scsi”,
“number”: 2064,
“serial”: “BTHC601206EQ480MGN”,
“lunid”: “55cd2e404c18b6fe”,
“size”: 480103981056,
“description”: “”,
“transfermode”: “Auto”,
“hddstandby”: “ALWAYS ON”,
“advpowermgmt”: “DISABLED”,
“togglesmart”: true,
“smartoptions”: “”,
“expiretime”: null,
“critical”: null,
“difference”: null,
“informational”: null,
“model”: “INTEL_SSDSC2BX480G4K”,
“rotationrate”: null,
“type”: “HDD”,
“zfs_guid”: null,
“bus”: “ATA”,
“devname”: “sdb”,
“enclosure”: null,
“supports_smart”: null,
“pool”: null
},

Honestly, it’s ridiculous.

22

P.S.

Forgot to mention that I did create a ticket regarding my issue which was quickly dismissed on the count that virtualisation is not supported with TrueNAS scale, even though the issue has nothing to do with virtualization and everything to do with some software component of middleware disk identifier interaction.
Fair enough, I created another ticket this time with the same issue on a bare-bones server install, and I’m curious to see how will that go..

I would be perfectly willing to pay for a software license to use TrueNAS without any of these (seemingly software only) issues and limitations, but we can’t be all expected to house and run enterprise servers in our homes..

23

There’s a feature request section of the forum that can be used for this purpose.

24

Please edit your post or make an additional one with a link to your JIRA trouble ticket.

26

Hi,
It’s 3 tickets so far.. :slight_smile:

NAS-140408
NAS-140445
NAS-140473

27

I edited your post to add links for the tickets. It’s easier for others. I didn’t find a NAS-140473?

NAS-140445 states “We have reason to believe your issue has been fixed in the latest stable version available. Please upgrade and report back if the problem persists.” Ticket shows submitted on 25.10.1 version. It looks like you mentioned other trying other versions and still had the issue in your initial JIRA post. If you tried a version of 26, what is the exact version?

28

Thanks, I seem to be having issues posting links here (maybe I haven’t posted enough for that), but the NAS-140473 is the correct one - and actually the only one opened at the moment. Exact 26 version (posted in that ticket) is 26.0.0-MASTER+20260330-020259.

And yes, for the ticket NAS-140473 I had to test it on the VM as I simply do not have a capability to change as quickly to the physical system, as fast as Bug Clerk can close my tickets :slight_smile: (NAS-140445 in that case). But.. as I mentioned, I’m 99.999% certain that the issue is not due to virtualization. It simply works on 25.04.

(yep, I get a reject when I put a link to the jira)