Proxmox - Serial number for “disks” incorrect

Dr. Bell

New Member
Jul 17, 2022
2
0
1
Hello all,


I recently spun up a server node with a fresh installation of Proxmox however, when I tried to build out a ZFS pool of 10 drives I would get an error. When I sorted by “Serial”, in the GUI, the disk serial numbers are the same between 4 of the drives (highlighted in red). Why is the serial the same between these particular drives?

Screen Shot 2022-07-16 at 11.46.18 AM.png

For more granular exploration to the problem I decided to SSH into the server and ran the following command:

Bash:
root@Newton:~# udevadm info -p 'block/sdc' --query  all

P: /devices/pci0000:00/0000:00:02.2/0000:02:00.0/host0/target0:0:2/0:0:2:0/block/sdc

N: sdc

L: 0

S: disk/by-path/pci-0000:02:00.0-scsi-0:0:2:0

S: disk/by-id/wwn-0x502b2a201d1c1b1a

S: disk/by-id/scsi-3502b2a201d1c1b1a

E: DEVPATH=/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host0/target0:0:2/0:0:2:0/block/sdc

E: DEVNAME=/dev/sdc

E: DEVTYPE=disk

E: DISKSEQ=11

E: MAJOR=8

E: MINOR=32

E: SUBSYSTEM=block

E: USEC_INITIALIZED=5697461

E: ID_SCSI=1

E: ID_VENDOR=ATA

E: ID_VENDOR_ENC=ATA\x20\x20\x20\x20\x20

E: ID_MODEL=KINGSTON_SA400S3

E: ID_MODEL_ENC=KINGSTON\x20SA400S3

E: ID_REVISION=0004

E: ID_TYPE=disk

E: ID_SERIAL=3502b2a201d1c1b1a

E: ID_SERIAL_SHORT=502b2a201d1c1b1a

E: ID_WWN=0x502b2a201d1c1b1a

E: ID_WWN_WITH_EXTENSION=0x502b2a201d1c1b1a

E: ID_SCSI_SERIAL=50026B728234D063

E: ID_BUS=scsi

E: ID_PATH=pci-0000:02:00.0-scsi-0:0:2:0

E: ID_PATH_TAG=pci-0000_02_00_0-scsi-0_0_2_0

E: DEVLINKS=/dev/disk/by-path/pci-0000:02:00.0-scsi-0:0:2:0 /dev/disk/by-id/wwn-0x502b2a201d1c1b1a /dev/disk/by-id/scsi-3502b2a201d1c1b1a

E: TAGS=:systemd:

E: CURRENT_TAGS=:systemd:

It seems as though Proxmox uses the ‘ID_SERIAL_SHORT’ field to populate the ‘Serial’ info in the GUI. My question is, how do I fix this issue with /sdc, /sdj, /sdm, and /sdn with the same serial number?
 
Do the disks actually have different or same serials?

Whats the output of "for disk in c j m n;do echo /dev/sd$disk;udevadm info -p block/sd$disk --query all|grep ID_SERIAL;done;
If the disks truly have identical serials, then you got a bad batch. Reach out to the vendor on how you can change the firmware information.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Do the disks actually have different or same serials?
Interestingly enough, they all have the same serials...

Bash:
root@newton:~# echo /dev/sdc;udevadm info -p block/sdc --query all|grep ID_SERIAL
/dev/sdc
E: ID_SERIAL=3502b2a201d1c1b1a
E: ID_SERIAL_SHORT=502b2a201d1c1b1a
root@newton:~# echo /dev/sdj;udevadm info -p block/sdj --query all|grep ID_SERIAL
/dev/sdj
E: ID_SERIAL=3502b2a201d1c1b1a
E: ID_SERIAL_SHORT=502b2a201d1c1b1a
root@newton:~# echo /dev/sdm;udevadm info -p block/sdm --query all|grep ID_SERIAL
/dev/sdm
E: ID_SERIAL=3502b2a201d1c1b1a
E: ID_SERIAL_SHORT=502b2a201d1c1b1a
root@newton:~# echo /dev/sdn;udevadm info -p block/sdn --query all|grep ID_SERIAL
/dev/sdn
E: ID_SERIAL=3502b2a201d1c1b1a
E: ID_SERIAL_SHORT=502b2a201d1c1b1a
root@newton:~#