GUI error - duplicate drive serials

TrueNAS General
,
1

Hi All,

New to TrueNAS, and not sure if this is the right place for this.

I have installed on a main server, and also installed on an old QNAP device. TLDR; QNAP only has 4 x HDDs and didn’t want to waste them on boot, so I used two decent quality USB sticks in the USB 3.1 ports (bad I know).

Install went fine, but when trying to create a data pool, I got an error that sde and sdg had identical serials (the two USB drives in the boot pool).

I think this is a GUI error, as:

  1. The two USBs weren’t part of the pool I was trying to create
  2. The boot pool created without problem
  3. The USBs had unique serials (checked with smartctl and under /dev/disk/by-id, and also in the GUI itself under disks)

I think the problem was that the USB bus ID was prepended to the USB serial, so the total serial was about 122 characters for each. I’m guessing the GUI checks all connected drives, not just those for the new pool, and for some reason, obfuscates long serials. The serials differed at the 5th character, and the very last character, but had similar patterns within and a long run of zeros, so it’s unlikely simple truncation.

Probably a pretty edge problem but thought I’d post if anyone else encounters this issue, the solution is to degrade the boot pool (remove one of the usb drives), create the new data pool, then reinsert the second USB for resilvering. There is probably a safer method but I don’t really care about this device it will be a second back-up.

Cheers,

Chris

1 Like
2

The best place would be to file a bug report on this, documenting that serial numbers as shown to TrueNAS are indeed unique so there is likely a flaw in the logic for checking duplicates.

3

Thanks, I’ve tried creating an Atlassian account to file a bug report, but it won’t let me, I keep getting an error e.g. “Something went wrong on our end

If this keeps happening, share this information with your admin, who should contact support.

Hash 167A36U Trace ed8dd043c50f42169453cc83aa8ce120"

I’ve tried two different Atlassian accounts, and two different browsers, so I don’t know what the issue is.

I’ll try again later.