Closed alanbach closed 3 months ago
We have now seen this happening randomly between NVME disks from different vendors, where:
esxcli nvme device get -A <vmhba-name>
Returns an empty value. Implemented a workaround to fall back to serial numbers to avoid data store creation failures.
This is a spotty behavior from vendor to vendor.
We have now seen this happening randomly between NVME disks from different vendors, where:
esxcli nvme device get -A <vmhba-name>
Returns an empty value. Implemented a workaround to fall back to serial numbers to avoid data store creation failures.
This is a spotty behavior from vendor to vendor.