ESXi Datastore to Virtual Drive

[balukr]

Customer has BE7K servers (UCS C-240 M4) it came pre-installed with ESXi 5.5 and 4 virtual drives, each virtual drive is configured with RAID 5. Now we need to install an UC application which requires RAID 10. We are not using one of the Datastore for any guest OS so our plan is to delete that DS and respective Virtual Drive, break that RAID and rebuild that to RAID 10 here is the challenge how can we  identify which Datastore mapped to what Virtual Drive? My understanding is ESXi does not map 1-1 (i.e VD0=DS1). If any one can shed some light on to identify this would be really appreciated.

Thanks..!

[Kirk J · Accepted solution]

Greetings.

Take a look at https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014953 

esxcli storage core path list

esxcli storage filesystem list

esxcli storage vmfs extent list

esxcfg-scsidevs -m

esxcfg-scsidevs -l

These should provide enough info to confirm which datastore is mapped to the VD in question.

Thanks,

Kirk...

[balukr]

Kirk,

Thanks for the quick response. I'm still kind of learning all this on ESXi side.  I have attached all those outputs here, DS what we are trying to break is DS4 how would I find the VD mapping to that here.

Thanks again for your help.

[Kirk J · Accepted solution]

Hopefully this is a little more concise:

Take output of 

~ # esxcfg-scsidevs -m

naa.678da6e715d760101f0aa4a61d982f63:1                           /vmfs/devices/disks/naa.678da6e715d760101f0aa4a61d982f63:1 5777f3b3-7bd4c97a-4ba0-a0369f9400b4  0  datastore4

Then match this with the output of esxcli storage core path list:

unknown.vmhba1-unknown.2:2-naa.678da6e715d760101f0aa4a61d982f63

   UID: unknown.vmhba1-unknown.2:2-naa.678da6e715d760101f0aa4a61d982f63

   Runtime Name: vmhba1:C2:T2:L0

   Device: naa.678da6e715d760101f0aa4a61d982f63

   Device Display Name: Local Cisco Disk (naa.678da6e715d760101f0aa4a61d982f63)

   Adapter: vmhba1

   Channel: 2

   Target: 2

   LUN: 0

  ... snip

This should correspond with your 3rd VD, since the target and VD#s start with 0.

Confirmed this in the lab: See below

VD0 (1st virtual drive created) does correspond with T0...and VD3 corresponds to T3.

These numbers of course are unique to each hba/controller so you want to make sure the vhba # and controller # (vmhba1 and C2 in my example) are from the same device when matching these up.

Kirk...

[balukr]

Kirk,

Thanks. Please can you verify and let me know that would be great.

[Kirk J]

Making sure you saw the lab info I updated in above post...

Kirk...

[balukr]

Thank you so much for taking time to do this in your lab. I really appreciate your help.

[balukr]

Did you had a chance to verify this? Please let me know.

Thanks.