You are experiencing these issues:
/var/log/vmkernel
log file, you see entries similar to:Partition vmhbax:x:x is active: partition table was not updated
Aug 7 10:17:52 esx1 vmkernel: 3:23:17:21.756 cpu9:4119)WARNING: Partition: 806: Partition 1 is active, failure to update partition table for naa.60a9800057396d4b566f4b356e48774b
[10:17:48.626 F59A1B90 verbose 'FSVolumeProvider'] RefreshVMFSVolumes called
[10:17:48.626 F59A1B90 verbose 'FSVolumeProvider'] RescanVmfs called
[10:17:49.425 F59A1B90 verbose 'FSVolumeProvider'] LookupVmfs: Cannot find VMFS volume with id <unset>, path, /vmfs/volumes/4926c7f4-########-####-##########0b, or name <unset>
[10:17:49.425 F59A1B90 verbose 'Hostsvc::DatastoreSystem'] ExpungeMissingDatastore: Removing datastore DSNAME.
[10:17:49.425 F59A1B90 verbose 'DatastoreBrowser'] 4926c7f4-########-####-##########0b-datastorebrowser::Destroy
[10:17:49.425 F59A1B90 verbose 'Hostsvc::Datastore'] DatastoreImpl 4926c7f4-########-####-##########0b Stopped
These errors occur when partition tables for VMFS volumes are removed while ESX/ESXi is using them. This can result from other systems clearing partition tables from visible LUNs to prepare them for use.
For example:
These or similar situations may accidentally occur if LUNs are presented to a mixture of ESX/ESXi and non-ESX/ESXi servers. To prevent against the above situations, restrict LUN visibility to only servers which are trusted and which require access to the VMFS Datastores.
To recreate a partition table, see:
Warning: If changes beyond the compromised partition table are made to a disk, data may not be recoverable and need to be restored from backup.