Skip to main content
Pure Technical Services

Matching VMDK to Array Volumes Using VMware Logs

Currently viewing public documentation. Please login to access the full scope of documentation.

KP_Ext_Announcement.png

Finding VMDK volumes in ESX support bundle. 

ESX can make it hard to find the volume names in the support bundle for VMDK. To find the volumes and the associated logs, take a look in the support bundle in the vmfs/volumes folder 

The VMFS volumes will be stored under GUID in that folder

jahenry@cloudfuse-prod-055c51dad72d0d0e4:/support/ES-57730/VMware-Logs/ESXi_Host-Logs/esx-jmpvmw40-2018-12-05--18.47-747768/vmfs/volumes$ls
57d1c7cc-27920e1a-5d1d-28f10eaa5d91  58dbca98-15c2f133-9bc9-b82a72377901  59499858-715f36ac-7409-b82a72377983  59c29dd3-c65eaf5a-bbe3-b82a72377942  59cd0462-d32e949d-e54b-b82a72377901  5b15a8c1-d51735ad-5cf6-b82a7237790e  vsanDatastore
57d1c7fa-0c6a9f42-8dbb-28f10eaa5d91  58dbcadd-bdd45c56-de2f-b82a72377901  5963b67f-485149ea-fd25-b82a72377901  59c29fbf-1d04c24c-9d31-b82a72377942  5a4e98cb-1ec38c85-81be-b82a7237790e  5b15a9cf-988b0b89-6f0e-b82a7237790e
57d1c957-aac73448-fbaf-28f10eaa5d91  58dbcb53-1a9344a2-a605-b82a72377901  5963b7fa-7a916012-9b33-b82a72377901  59cabbc9-120895c2-4d92-b82a7237791b  5a4e9928-d28dd66a-cace-b82a7237790e  5b61ff38-9de5d4c6-ac81-b82a72377969
57d1c9bb-64dd2fb8-b33e-28f10eaa5d91  58dbcb8c-56873a61-32b2-b82a72377901  5963b853-25cc1fbf-2b45-b82a72377901  59cabbfd-da6ebc8e-8ce8-b82a7237791b  5a4e996e-97eb1d4e-61c4-b82a7237790e  5b7f7099-024b2dac-0e90-b82a7237790e
57d1c9e8-687f6175-f456-28f10eaa5d91  590b6cd6-7e6e980d-cfca-b82a72377901  5963b887-d3f4b5cc-e24a-b82a72377901  59cabc23-34259400-3eba-b82a7237791b  5a4e9991-a010dc3a-34e2-b82a7237790e  5b9aa3db-32f6dfb4-225e-b82a7237790e
58a76fa9-a58c223a-f64b-b82a72377901  5949971f-1e0d179c-3c69-b82a72377976  59c28fde-368b6974-287e-b82a72377942  59cd0226-b7e1b30e-d5bc-b82a72377901  5b15a7c3-29101eec-fc1a-b82a7237790e  5bd867b9-5944bd14-1ab0-b82a72377928

From that folder enter ls ./* 

jahenry@cloudfuse-prod-055c51dad72d0d0e4:/support/ES-57730/VMware-Logs/ESXi_Host-Logs/esx-jmpvmw40-2018-12-05--18.47-747768/vmfs/volumes$ ls ./*
./57d1c7cc-27920e1a-5d1d-28f10eaa5d91:
JMPVBP03
./57d1c7fa-0c6a9f42-8dbb-28f10eaa5d91:
JMPMDS01  JMPSQL05  JMPSQL06B
./57d1c957-aac73448-fbaf-28f10eaa5d91:
JMPSQL50A  JMPSQL94
./57d1c9bb-64dd2fb8-b33e-28f10eaa5d91:
JMPSRS000
./57d1c9e8-687f6175-f456-28f10eaa5d91:
JMPSQL03B  JMPSQL66  JMPSQL72
./58a76fa9-a58c223a-f64b-b82a72377901:
JMPSQL51A  JMPSQL51B

CD to the folder with the desired volume name. In this example, we want the volume "JMPVBP03" 

 jahenry@cloudfuse-prod-055c51dad72d0d0e4:/support/ES-57730/VMware-Logs/ESXi_Host-Logs/esx-jmpvmw40-2018-12-05--18.47-747768/vmfs/volumes$ cd 57d1c7cc-27920e1a-5d1d-28f10eaa5d91/JMPVBP03 

From here, you can look at the VMware log that shows us disk operations on the particular volume

jahenry@cloudfuse-prod-055c51dad72d0d0e4:/support/ES-57730/VMware-Logs/ESXi_Host-Logs/esx-jmpvmw40-2018-12-05--18.47-747768/vmfs/volumes/57d1c7cc-27920e1a-5d1d-28f10eaa5d91/JMPVBP03$ ls
dump-vmdk-rdm-info.sh_vmfsvolumes57d1c7cc-27920e1a-5d1d-28f10eaa5d91JMPVBP03JMPVBP03vmx.txt  
JMPVBP03.vmsd  JMPVBP03.vmxf JMPVBP03.vmdk  JMPVBP03.vmx  
ls_-isla-vmfsvolumes57d1c7cc-27920e1a-5d1d-28f10eaa5d91JMPVBP03.txt  
vmware-11.log  vmware-7.log  vmware-9.log vmware-10.log vmware-6.log vmware-8.log vmware.log