Hi,
Thanks for your answer, for the output of udevadm info --query=all --name=/dev/sd{b,c} | grep -i serial, I see the following:
For sdb:
E: ID_SERIAL=ST16000NE000-2RW103_ZL2PR3AS
E: ID_SERIAL_SHORT=ZL2PR3AS
E: ID_USB_SERIAL=ASMT_ASM1352R-PM_AAAABBBB0003-0:0
E: ID_USB_SERIAL_SHORT=AAAABBBB0003
For sdc:
E: ID_SERIAL=ST16000NE000-2RW103_ZL2PR3B1
E: ID_SERIAL_SHORT=ZL2PR3B1
E: ID_USB_SERIAL=ASMT_ASM1352R-PM_AAAABBBB0003-0:1
E: ID_USB_SERIAL_SHORT=AAAABBBB0003
The only conflict is ID_USB_SERIAL_SHORT. Also, when I look to the other values, esp disk-* ones, they are all enumerated correctly. So the devices are enumerated and created correctly by the kernel.
With my programmer hat on, I’d argue that, if the device has ID_USB strings, it can be used to understand that the disks are coming from an external enclosure, and if the long serial numbers address the devices sufficiently, short can be ignored or used for another reasons.
Also, having an ID_USB* string can be used to warn user about the dangerous thing they are going to do.
At the end of the day, I’m digging this, with the help of the experts here, to arrive to the correct & desirable behavior, even if it’s TrueNAS saying “This is dangerous, and I’m not doing this”, instead of giving weird errors and triggering runaway logging in some logs.
Thanks again!