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.
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
Since this is a solution specific issue, best bet would be getting in touch with their support department.