Last update:
Using VMFSrecovery tool I found that starting sector (I don't know why) on this datastore set at sector 36864.
Just used partedUtil to change starting offset from 2048 to 36864.
Then ran vmkfstools -V
And finally I can see missing datastore in "Datastores" view, but cannot mount it due to following error:
Call "HostStorageSystem.MountVmfsVolume" for object "storageSystem" on ESXi "<ESXI_HOST_IP_Address>" failed.
Operation failed, diagnostics report: Unable to find volume uuid[58df616b-d5203334-2c9c-3ca82aa0cf20] lvm [] devices
I am now able to see metadata info:
# vmkfstools -P -h /vmfs/volumes/Datastore/
VMFS-5.61 file system spanning 1 partitions.
File system label (if any): Datastore
Mode: public
Capacity 7.3 TB, 1.7 TB available, file block size 1 MB, max supported file size 62.9 TB
UUID: 58df616b-d5203334-2c9c-3ca82aa0cf20
Partitions spanned (on "disks"):
naa.600605b003b170f020721bf665b2d1c2:1
Is Native Snapshot Capable: YES
In addition to that I am able to see datastore and also can browse all VMDK files on it using SSH
ls -la /vmfs/volumes/Datastore
lrwxr-xr-x | 1 root | root | 35 Sep 26 19:36 Datastore -> 58df616b-d5203334-2c9c-3ca82aa0cf20 |
Guys, do you know how this can be fixed?
What should be done to allow datastore mount?