When working with replacement/removal of local storage devices it is critical that the correct device is identified.
Failure to identify the correct device can result in an incorrect, functional device being removed, this can lead to further issues and/or delay in issue resolution (e.g. due to another trip to the datacenter required).
VMware vSphere ESXi 7.0
VMware vSphere ESXi 8.0
VMware vSAN 7.x
VMware vSAN 8.x
When working live on a system and have SSH access the host, physical slot location of storage devices can be determined using:
# esxcli storage core device physical get -d naa.xxxxxxxxxxxxx
Or for instance using a loop to query all in-use vSAN devices:
# for i in $(vdq -Hi| grep -E "SSD|MD"| awk '{print $2}');do echo $i;esxcli storage core device physical get -d $i;done
However, these data are not generated as part of a standard ESXi log bundle (and hence there is no localcli_storage-core-device-physical-get.txt present in commands/ folder).
Physical slot information for devices can be determined from the contents of vmware-vimdump_-o----U-dcui.txt in the commands/ folder of the ESXi bundle e.g.:
Example output from a local SSD device (where naa.xxxxxxxxxxxxxxxx is the unique identifier of the device):
devicePath = '/vmfs/devices/disks/naa.xxxxxxxxxxxxxxxx', ssd = true, localDisk = true, physicalLocation = (str) [ 'enclosure 1, slot 1' ],
Example output from a local NVMe device (where eui.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx is the unique identifier of the device):
devicePath = '/vmfs/devices/disks/eui.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx', ssd = true, localDisk = true, physicalLocation = (str) [ 'PCIe SSD in Slot 8 Bay 0' ],