I have a Dell PE R415 that I have upgraded to ESXi v6.0 allong with adding a third drive to an array, converting from a RAID 1 to RAID 5 to increase storage from 4TB to 8TB. Upon reboot, I discovered my datastore was no longer mounted. I have dug around and the other posts I have found don't match my situation. When I list the contents of /dev/disks I see this:
[root@localhost:/dev/disks] ls -al
total 15628855120
drwxr-xr-x 2 root root 512 Oct 6 23:19 .
drwxr-xr-x 15 root root 512 Oct 6 23:19 ..
-rw------- 1 root root 2104425984 Oct 6 23:19 mpx.vmhba33:C0:T0:L0
-rw------- 1 root root 4161536 Oct 6 23:19 mpx.vmhba33:C0:T0:L0:1
-rw------- 1 root root 262127616 Oct 6 23:19 mpx.vmhba33:C0:T0:L0:5
-rw------- 1 root root 262127616 Oct 6 23:19 mpx.vmhba33:C0:T0:L0:6
-rw------- 1 root root 115326976 Oct 6 23:19 mpx.vmhba33:C0:T0:L0:7
-rw------- 1 root root 299876352 Oct 6 23:19 mpx.vmhba33:C0:T0:L0:8
-rw------- 1 root root 8000450330624 Oct 6 23:19 naa.6848f690e0274300251d715007dfd58e
-rw------- 1 root root 8000449265152 Oct 6 23:19 naa.6848f690e0274300251d715007dfd58e:1
lrwxrwxrwx 1 root root 20 Oct 6 23:19 vml.0000000000766d68626133333a303a30 -> mpx.vmhba33:C0:T0:L0
lrwxrwxrwx 1 root root 22 Oct 6 23:19 vml.0000000000766d68626133333a303a30:1 -> mpx.vmhba33:C0:T0:L0:1
lrwxrwxrwx 1 root root 22 Oct 6 23:19 vml.0000000000766d68626133333a303a30:5 -> mpx.vmhba33:C0:T0:L0:5
lrwxrwxrwx 1 root root 22 Oct 6 23:19 vml.0000000000766d68626133333a303a30:6 -> mpx.vmhba33:C0:T0:L0:6
lrwxrwxrwx 1 root root 22 Oct 6 23:19 vml.0000000000766d68626133333a303a30:7 -> mpx.vmhba33:C0:T0:L0:7
lrwxrwxrwx 1 root root 22 Oct 6 23:19 vml.0000000000766d68626133333a303a30:8 -> mpx.vmhba33:C0:T0:L0:8
lrwxrwxrwx 1 root root 36 Oct 6 23:19 vml.02000000006848f690e0274300251d715007dfd58e504552432048 -> naa.6848f690e0274300251d715007dfd58e
lrwxrwxrwx 1 root root 38 Oct 6 23:19 vml.02000000006848f690e0274300251d715007dfd58e504552432048:1 -> naa.6848f690e0274300251d715007dfd58e:1
[root@localhost:/dev/disks]
And in /vmfs/volumes:
[root@localhost:/vmfs/volumes] ls -al
total 772
drwxr-xr-x 1 root root 512 Oct 6 23:18 .
drwxr-xr-x 1 root root 512 Oct 2 00:53 ..
drwxr-xr-x 1 root root 8 Jan 1 1970 2c5318ec-8a80a8fc-523c-16e28ab50e2a
drwxr-xr-x 1 root root 8 Jan 1 1970 42508ee6-6a0fb0cc-ba22-9e19120afc17
drwxr-xr-x 1 root root 8 Jan 1 1970 5d93e381-6cf0b5f0-f37a-e89a8fd28de6
[root@localhost:/vmfs/volumes]
Running esxcli storage core path list shows:
unknown.vmhba2-unknown.2:1-naa.6848f690e0274300251d715007dfd58e
UID: unknown.vmhba2-unknown.2:1-naa.6848f690e0274300251d715007dfd58e
Runtime Name: vmhba2:C2:T1:L0
Device: naa.6848f690e0274300251d715007dfd58e
Device Display Name: Local DELL Disk (naa.6848f690e0274300251d715007dfd58e)
Adapter: vmhba2
Channel: 2
Target: 1
LUN: 0
Plugin: NMP
State: active
Transport: parallel
Adapter Identifier: unknown.vmhba2
Target Identifier: unknown.2:1
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 131072
Running esxcli storage vmfs extent list yields a blank display.
Running esxcli storage filesystem list shows:
[root@localhost:/dev/disks] esxcli storage filesystem list
Mount Point Volume Name UUID Mounted Type Size Free
------------------------------------------------- ----------- ----------------------------------- ------- ---- --------- ---------
/vmfs/volumes/5d93e381-6cf0b5f0-f37a-e89a8fd28de6 5d93e381-6cf0b5f0-f37a-e89a8fd28de6 true vfat 299712512 84189184
/vmfs/volumes/42508ee6-6a0fb0cc-ba22-9e19120afc17 42508ee6-6a0fb0cc-ba22-9e19120afc17 true vfat 261853184 261849088
/vmfs/volumes/2c5318ec-8a80a8fc-523c-16e28ab50e2a 2c5318ec-8a80a8fc-523c-16e28ab50e2a true vfat 261853184 73515008
[root@localhost:/dev/disks]
Running esxcfg-mpath -b shows:
[root@localhost:/dev/disks] esxcfg-mpath -b
naa.6848f690e0274300251d715007dfd58e : Local DELL Disk (naa.6848f690e0274300251d715007dfd58e)
vmhba2:C2:T1:L0 LUN:0 state:active Local HBA vmhba2 channel 2 target 1
mpx.vmhba33:C0:T0:L0 : Local USB Direct-Access (mpx.vmhba33:C0:T0:L0)
vmhba33:C0:T0:L0 LUN:0 state:active Local HBA vmhba33 channel 0 target 0
mpx.vmhba1:C0:T0:L0 : Local TEAC CD-ROM (mpx.vmhba1:C0:T0:L0)
vmhba1:C0:T0:L0 LUN:0 state:active Local HBA vmhba1 channel 0 target 0
t10.DP______BACKPLANE000000 : Local DP Enclosure Svc Dev (t10.DP______BACKPLANE000000)
vmhba2:C0:T32:L0 LUN:0 state:active Local HBA vmhba2 channel 0 target 32
[root@localhost:/dev/disks]
esxcfg-scsidevs -l shows:
naa.6848f690e0274300251d715007dfd58e
Device Type: Direct-Access
Size: 7629824 MB
Display Name: Local DELL Disk (naa.6848f690e0274300251d715007dfd58e)
Multipath Plugin: NMP
Console Device: /vmfs/devices/disks/naa.6848f690e0274300251d715007dfd58e
Devfs Path: /vmfs/devices/disks/naa.6848f690e0274300251d715007dfd58e
Vendor: DELL Model: PERC H700 Revis: 2.10
SCSI Level: 5 Is Pseudo: false Status: on
Is RDM Capable: false Is Removable: false
Is Local: true Is SSD: false
Other Names:
vml.02000000006848f690e0274300251d715007dfd58e504552432048
VAAI Status: unsupported
The output of esxcfg-scsidevs -m is blank.
Not so long ago, I watched a vmware support tech fix this very problem on a paid deploy, but it went too fast for me to follow, but basically she recreated the link between the vmfs on the local Dell disk and a datastore.
Can someone point me in the correct direction?
Any assistance much appreciated!
Clay
