Hi Everyone,
We have just noticed that our datastore is missing and we cannot see it under the ESXi webpage.
Not sure when did this happen, but maybe after we have updated the Esxi to 6.7.
The VMs are running fine.
We can see the Adapter under Storage -> Adapters.
We can see the hard drive under Storage -> Devices.
But the Datastore is empty and we cannot change any settings of the VMs as it throws an error
When I try to browse: "There are no browsable datastores. Currently, only vSAN and local VMFS datastores can be browsed."
I have tried to figure it out and run a few commands under SSH, but I cannot see what could be the issue or how to fix it.
Could you please let me know how to get back the datastore?
esxcli storage vmfs extent list
Volume Name VMFS UUID Extent Number Device Name Partition
----------- ----------------------------------- ------------- ------------------------------------ ---------
datastore1 5c8a7789-1a4c3a5c-0a47-b083fec42bdd 0 naa.6b083fe0cfb8ba002400ee74143fdef7 3
esxcfg-mpath -l
sas.5b083fe0cfb8ba00-sas.6000ee74143fdef7-naa.6b083fe0cfb8ba002400ee74143fdef7
Runtime Name: vmhba0:C2:T0:L0
Device: naa.6b083fe0cfb8ba002400ee74143fdef7
Device Display Name: Local DELL Disk (naa.6b083fe0cfb8ba002400ee74143fdef7)
Adapter: vmhba0 Channel: 2 Target: 0 LUN: 0
Adapter Identifier: sas.5b083fe0cfb8ba00
Target Identifier: sas.6000ee74143fdef7
Plugin: NMP
State: active
Transport: sas
Adapter Transport Details: 5b083fe0cfb8ba00
Target Transport Details: 6000ee74143fdef7
esxcfg-scsidevs -c
Device UID Device Type Console Device Size Multipath PluginDisplay Name
naa.6b083fe0cfb8ba002400ee74143fdef7 Direct-Access /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7 3814400MB NMP Local DELL Disk (naa.6b083fe0cfb8ba002400ee74143fdef7)
esxcli storage vmfs snapshot list
This returns nothing...
esxcli system coredump partition list
Name Path Active Configured
-------------------------------------- ---------------------------------------------------------- ------ ----------
naa.6b083fe0cfb8ba002400ee74143fdef7:7 /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7:7 false false
naa.6b083fe0cfb8ba002400ee74143fdef7:9 /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7:9 true true
partedUtil getptbl /vmfs/devices/disks/naa.6b083fe0cfb8ba002400ee74143fdef7
gpt
486267 255 63 7811891200
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
2 7086080 15472639 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
3 15472640 7811891166 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
If I run a rescan on the device the kernel log shows this:
2019-04-11T16:47:15.591Z cpu6:2099152 opID=b3571b7d)World: 11943: VC opID 24fae6e5 maps to vmkernel opID b3571b7d
2019-04-11T16:47:15.591Z cpu6:2099152 opID=b3571b7d)NVDManagement: 1461: No nvdimms found on the system
2019-04-11T16:47:25.437Z cpu2:2097756)ScsiDeviceIO: 3068: Cmd(0x459a41156c40) 0x1a, CmdSN 0x11be from world 0 to dev "naa.6b083fe0cfb8ba002400ee74143fdef7" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)World: 11943: VC opID 24fae6ee maps to vmkernel opID bf5b1e18
2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)VC: 4616: Device rescan time 16 msec (total number of devices 5)
2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)VC: 4619: Filesystem probe time 30 msec (devices probed 3 of 5)
2019-04-11T16:47:25.466Z cpu2:2099150 opID=bf5b1e18)VC: 4621: Refresh open volume time 1 msec