Datastore is not appering (no volumes for existing datastores)

[Brensted]

Hi everyone,

Currently we a running standalone configuration of StarWind Software with iSCSI Datastore on 2 hosts (1 storage host connected to 2 ESXi host via iSCSI)

We faced an issue:

Existing datastores are missing volumes after several reboots, all iSCSI paths are connected and devices is showing properly.

partedUtil getptbl /vmfs/devices/disks/<device-name>

Shows that partition is fine.

However esxcfg-volumes -l shows us nothing. Apparently, datastore is a missing a volume.

We cant browse a datastore and it not appearing in datastores tab.

And the question is how to restore a volume without a data loss? Is there any chance to restore the data from that partition or move it.

Appreciate for any assistance.

Thanks in advance.

[a_p_]

What you may try, is to run vmkfstools -V (note: upper-case "-V") to rescan the storage, and see whether any errors/warning show up in the vmkernel.log.

André

[Brensted]

Here is a log after running a command.

[a_p_]

Which ESXi version, and build do you currently use.

There have been known issues, see e.g. https://kb.vmware.com/s/article/2006858​

André

[Brensted]

6.7.0 (8169922)

[Brensted]

Here is what we got after running commands from your article

vmkfstools -Ph -v1 /vmfs/volumes/Storage3TB-Generic

Could not open /vmfs/volumes/Storage3TB-Generic

Error: vmkfstools failed: vmkernel is not loaded or call not implemented.

OBJLIB-LIB: ObjLib cleanup done.

WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0

vmkfstools --configATSOnly 0 /vmfs/devices/disks/eui.ea60be64c267f43d:1

Unable to get attributes of VMFS '/vmfs/volumes/Storage3TB-Generic'

Attempt to configure non-ATS locking mode on '/vmfs/volumes/Storage3TB-Generic': failed.

Error: No such file or directory

[a_p_]

Instead of trying different things, which may make things worse, please try to contact continuum​. I think he can help you in this case.

André

[lukebes1010]

Since this is a solution specific issue, best bet would be getting in touch with their support department.

[Jesus3]

It takes some time (about 10-20min) until server can see the new datastore. Perhaps there is some way to update and refresh in less time...