Disks have duplicate serial numbers: None (sdi, sdj)

TrueNAS General
1

Hello,

I have two SSD (250 and 240gb) connected to an IBM M1015 (sas9211-8i) flashed in IT mode (along other 6 rotating drives).

It should be an ideal configuration, yet it won’t allow me to put them in a stripe array (yes I know it’s dangerous, it’s just to have high I/O to the download folder): I’m getting an “Disks have duplicate serial numbers: None (sdi, sdj).” error message

My steps are the following

The disks obvilusly do NOT have duplicate serial numbers and they’re not even the disk in question, the ones in the error are the boot drives (which also do not have duplicate serial numbers).

There is no virtualization anywhere, this is a bare metal system. I’m on the latest stable, 25.10.1 - Goldeye at the moment.

I tried also width 1 and VDEVs 2 yet I’m getting the exact same error.

What am I doing wrong? What am I missing?

Thanks and cheers

2

Your exact hardware make up.

3

Also, the history of this system. Was it running before and what were the changes you recently made?

4

I wish I placed all my comments in one posting, but another question, are you running 25.10.1.2 ? the dot 2 fixed many issues.

1 Like
5

I’m running the latest version of the general profile: normally I don’t use the early adopter train unless needed and I didn’t see anything in the changelog to suggest this is the case.

The system is a Dell Optiplex with a IBM M1015 SAS card, it’s an i5-3570 CPU @ 3.40GHz with 16gb of ram, nothing fancy. Dual USB drives as boot, the main pool is 6x8TB drives with an old 64gb as zlog… nothing special

It has been running fine since FreeNAS 9, this looks either like a bug or that I’m overlooking something simple.

Any ideas?

6

A mirror? Not strictly necessarily, but a lot of people do it.

Pretty sure there a quite a few threads with USB devices and duplicates serials on this forum. I think one case was like yours, the usb serial was listed as empty, so two drives, two empty serials → duplicates.

Edit: found one

7

This is a bug that should be solved in 26 Beta 1 as well as 25.10.2.2 according to this ticket if it is the same issue. You can always create another one with as much information as you can and see if it will be closed with a reference to this one.

Hope that helps

2 Likes
8

Thanks for chiming in with that. It is a very odd issue for certain, especially since the serial number are displayed on TrueNAS.

You could try using the CLI and manually creating the stripe.
Here is the basic command zpool create pool_name /dev/sda /dev/sdb /dev/sdc
And you just keep adding on the drives in the single command. If you add 8 drives, then you need 8 /dev/sd?. Do some google searching if you need more clarification.

Hope it works out.

9

That bug does look similar to mine: I have all the serial numbers correctly showing in the GUI and they’re all different, yet the message shows.

I haven’t switched trains yet but it looks like SCALE-25.10.2.2 is not out publicly yet? Do I understand that correctly?

10

I just checked, it is not available in the General or Early Adopter Train yet. I’m waiting for it too. Would really like to be create my pool from the GUI and know that TrueNAS (appliance) sees the serials correctly. Who knows what else this could impact.

11

@pushacoustics I just found out something: Changing one of the USB Sticks to a USB SSD fixed the issue. I have no idea why. But maybe this is an option for you.

12

25.10.2.2 is not released, and as far as i know there’s also no ETA when it will relese…

13

You mean to physically replace it with an SSD USB or to change its type via software somehow? Because I’ve looked for that option but only found how to change the drives description. And I don’t want to purchase new hardware for a gui bug.

Fun fact: after setting up a drive description somehow the problem got worse :smiley:

Just for reference this is the list of drives with their serial.

14

I physically replaced it. Had an old external enclosure and an unused and reserved for such a thing 120GB SSD lying around. I didn’t want to do it this way since there is no space in the enclosure to fit it but it was the only sane option. Killed 2 sticks already. But purchasing a tiny m.2 enclosure with a tiny m.2 disk doesn’t make sense currently.

15

Remove one of the two boot drives from your mirror using zpool detach boot-pool sdi. You should be able to create your new SSD stripped pool and then just add SDI back to your boot pool using the GUI and boot pool menus.

1 Like
16

That is an interesting idea I didn’t think of and that should work imho. Thanks Barky!
I can’t test it any more maybe pushacoustics can.

17

Thank you! That did it!

For anyone in the same boat I made screenshots every step of the process:

Thanks also to everyone that chimed in.

Cheers!

18

@pushacoustics That’s great to read! Would you mind marking Barky’s comment as the solution, so others can find it more easily?

19

Sure thing! I didn’t do that before as it’s still somewhat a workaround, but I realize it’s useful nevertheless until the new version is out.