NVME Drive Serial "unknown"

[Stoiker]

Dear Proxmox Community,

Two SK Hynix PC711 NVME drives in my Proxmox Node have an "unknown" serial in the Disks table. There seems to be a parsing error when trying to detect it. I found the following thread where another user had a similar problem.

When I run the udev command to read out the serial number, I get the following output (abbreviated):

udevadm info -p /sys/block/nvme0n1 --query all

ID_SERIAL_SHORT=   KGADN486501210C70H

Notice the spaces after the equal sign. Could the leading spaces be the reason, why there is a problem with the serial number?

I created a mirrored ZFS Pool using the command line and use it as storage for VMs and Containers. Everything seems to work, and I'm not super worried about this small bug. I just wanted to ask if I could potentially run into problems down the road, if the Proxmox System doesn't know the serial number of the drives.

Thank you for your help!

 

[sterzy]

can you post the full output of udevadm info -p /sys/block/nvme0n1 --query all? the regex in question does seem to expect there to be no leading spaces [1]. however, there also needs to be a leading E:, that is missing from your output too.

[1]: https://git.proxmox.com/?p=pve-stor...d206e67fb731bfd9fa638f5a78067c68;hb=HEAD#l331

 

[Stoiker]

Hi sterzy,

Thank you for looking into this.

Here is the complete output:

P: /devices/pci0000:00/0000:00:02.1/0000:01:00.2/0000:02:00.0/0000:03:00.0/nvme/nvme0/nvme0n1
M: nvme0n1
R: 1
U: block
T: disk
D: b 259:1
N: nvme0n1
L: 0
S: disk/by-id/nvme-PC711_NVMe_SK_hynix_1TB____FDB1N44991350194T_1
S: disk/by-diskseq/10
S: disk/by-path/pci-0000:03:00.0-nvme-1
S: disk/by-id/nvme-nvme.1c5c-2020204b4e41394e3436323231303430394f3148-5043373131204e564d6520534b2068796e697820315442-00000001
S: disk/by-id/nvme-PC711_NVMe_SK_hynix_1TB____FDB1N44991350194T
Q: 10
E: DEVPATH=/devices/pci0000:00/0000:00:02.1/0000:01:00.2/0000:02:00.0/0000:03:00.0/nvme/nvme0/nvme0n1
E: SUBSYSTEM=block
E: DEVNAME=/dev/nvme0n1
E: DEVTYPE=disk
E: DISKSEQ=10
E: MAJOR=259
E: MINOR=1
E: USEC_INITIALIZED=3750300
E: ID_SERIAL_SHORT=   FDB1N44991350194T
E: ID_WWN=nvme.1c5c-2020204b4e41394e3436323231303430394f3148-5043373131204e564d6520534b2068796e697820315442-00000001
E: ID_MODEL=PC711 NVMe SK hynix 1TB
E: ID_REVISION=41001131
E: ID_NSID=1
E: ID_SERIAL=PC711_NVMe_SK_hynix_1TB____FDB1N44991350194T_1
E: ID_PATH=pci-0000:03:00.0-nvme-1
E: ID_PATH_TAG=pci-0000_03_00_0-nvme-1
E: ID_PART_TABLE_UUID=80c6cd6c-e47c-0148-b666-3e254b2c3ef4
E: ID_PART_TABLE_TYPE=gpt
E: DEVLINKS=/dev/disk/by-id/nvme-PC711_NVMe_SK_hynix_1TB____FDB1N44991350194T_1 /dev/disk/by-diskseq/10 /dev/disk/by-path/pci-0000:03:00.0-nvme-1 /dev/disk/by-id/nvme-nvme.1c5c-2020204b4e41394e3436323231303430394f3148-5043373131204e564d6520534b2068796e697820315442-00000001 /dev/disk/by-id/nvme-PC711_NVMe_SK_hynix_1TB____FDB1N44991350194T
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

 

[sterzy]

hm yeah, this seems to be an exception to an unwritten rule kind of situation. anyway, i send a patch that should fix this [1].

[1]: https://lore.proxmox.com/pve-devel/20250312083819.15379-1-s.sterz@proxmox.com/T/#u

 

[Stoiker]

It is really odd, that the drive reports the serial number with leading spaces. Sounds like a buggy implementation on the OEMs side.

If this fixes this small annoyance and doesn't cause trouble for other drives, I will be very happy. Thank you for taking care of this so quickly. I will report back once I have the patch on my system.

Do you happen to know if this serial number is used for anything else than identifying the component in case of a failure?