•A datastore has become inaccessible.

•A VMFS partition table is missing.


The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.

This article provides information on: • Determining whether this is the same problem. • Resolving the problem.


This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.


Since this question is related to the VMware mostly, we prefer to provide the link to the original article:

Additional Information

In VMware Sphere 5.x and later, newly-created VMFS datastores use GPT partition tables instead of MBR partition tables.

The benefit of using GPT partition tables is thatmore than one copy of the partition table is kept on the LUN. If a physical Windows host has access to the LUN on the SAN, it, by default, automatically assigns a drive letter to the LUN, which destroys an MBR partition table. This type of problem does not occur with GPT, since vSphere uses the backup partition table.

Request a Product Feature

To request a new product feature or to provide feedback on a StarWind product, please email to our support at and put “Request a Product Feature” as the subject.

Back to Knowledge Base