Being a software engineer, I am disturbing by the way this software create the disk ID.
According to the following table from VMware Docs we have some case that the software will not recognize the disk or lost disks.
| ID Formats Supported by Device | Device Identifier Generated by Host | ||
|---|---|---|---|
| EUI64 ID Format | NGUID ID Format | ESXi 6.7 and earlier | ESXi 6.7 Update 2 |
| yes | yes | t10.xxx_EUI64 | t10.xxx_EUI64 |
| yes | no | t10.xxx_EUI64 | t10.xxx_EUI64 |
| no | yes | t10.xxx_controller_serial_number | eui.xxx (NGUID) as primary ID t10.xxx_controller_serial_number as alternative primary ID |
so what if
1. The NVMe SSD from the same company may use the same EUI64 for every NVMe SSD on the same interface (say using an ASUS Hyper M.2 X16 PCIe 3.0x4 Expansion card with 4 identical NVMe SSD). It is possible because of bad design from the SSD manufacturer, the EUI64 are all the same for the 4 NVMe SSD, under this case, the ESXI will only recognized one of the 4 disks (since the disk will be t10.xxx_EUI64, and EUI64 are the same for all 4 NVMe SSD, The "storage" "adapters" tab did show there are 4 interfaces (adapters), but the "stroage" "devices" will only show 1 disks.
2. Why there is no "no, no" options?
I understand that the NVMe standard 1.3 (for ESXi 6.7) is the base of how the NVMe SSD should be designed, but I think the software should be smart enough to cover the mistakes the hardware company may make and so it can recognized most of the NVMe SSD that is available from the market.
Thanks and Regards