"Conflicting VMFS datastores ... one is backed by local disk" error reconnecting ESXi host to vCenter Server
search cancel

"Conflicting VMFS datastores ... one is backed by local disk" error reconnecting ESXi host to vCenter Server


Article ID: 341652


Updated On:


VMware vCenter Server VMware vSphere ESXi


This article provides information on how to detect and resolve the issue of spurious conflicting datastore error not allowing ESXi hosts to be updated.


A ESXi host is disconnected from vCenter sever upon reconnection with the following error message.

"Conflicting VMFS datastores (url ds:///vmfs/volumes/xxxxxxxx/) - one is backed by local disk"

This issue occurs in one of the following scenarios:

  • vCenter Server Appliance is  is upgraded from (VCSA) 6.7 U2 series to VCSA 6.7 U3 series
  • ESXi host is reconnected to vCenter server after the host is upgraded from ESXi 6.7 U2 to ESXi 6.7 U3
  • An ESXi host running 6.7 U2 host is manually disconnected from a vCenter server, and then connected again to the vCenter server.
  • /var/log/vmware/vpxd.log has following messages when this issue occurs.
YYYY-MM-DDTHH:MM:SS.417Z info vpxd[04124] [Originator@6876 sub=Vmomi opID=lro-699321-407d264a] [ClientAdapterBase] Retry SOAP call after exception; host: hostname.domainname, method: vpxapi.VpxaService.setServer, exception: N6Vpxapi5Fault16NotAuthenticated9ExceptionE('Fault cause: vpxapi.fault.NotAuthenticated
--> ')
YYYY-MM-DDTHH:MM:SS.417Z info vpxd[04124] [Originator@6876 sub=Vmomi opID=lro-699321-407d264a] Stale SOAP session to host hostname.domainname; reinitializing
YYYY-MM-DDTHH:MM:SS.488Z info vpxd[04124] [Originator@6876 sub=MoHost opID=lro-699321-407d264a] host [vim.HostSystem:host-25,hostname.domainname] connection state changed to DISCONNECTED
YYYY-MM-DDTHH:MM:SS.496Z warning vpxd[04124] [Originator@6876 sub=MoCluster opID=lro-699321-407d264a] Deprecated property ClusterComputeResource.configuration read
YYYY-MM-DDTHH:MM:SS.553Z error vpxd[04124] [Originator@6876 sub=HostAccess opID=lro-699321-407d264a] Conflicting VMFS datastores (url ds:///vmfs/volumes/01234567-89abcdef-0123-456789abcdef/) - one is backed by local disk
YYYY-MM-DDTHH:MM:SS.555Z info vpxd[04124] [Originator@6876 sub=vpxLro opID=lro-699321-407d264a-02] [VpxLRO] -- BEGIN lro-699325 --  -- DasConfig.UnconfigureHost --
YYYY-MM-DDTHH:MM:SS.557Z info vpxd[04124] [Originator@6876 sub=vpxLro opID=lro-699321-407d264a-02] [VpxLRO] -- FINISH lro-699325
YYYY-MM-DDTHH:MM:SS.557Z warning vpxd[04124] [Originator@6876 sub=MoHost opID=lro-699321-407d264a] Failed to Disconnect and Reconnect host [vim.HostSystem:host-25,hostname.domainname]: N3Vim5Fault25ConflictingDatastoreFound9ExceptionE(Fault cause: vim.fault.ConflictingDatastoreFound
YYYY-MM-DDTHH:MM:SS.590Z info vpxd[04028] [Originator@6876 sub=Default opID=7cc9145] [VpxLRO] -- ERROR task-1229559 -- host-25 -- vim.HostSystem.reconnect: vim.fault.ConflictingDatastoreFound:
--> Result:
--> (vim.fault.ConflictingDatastoreFound) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    name = "datastore-01",
-->    url = "ds:///vmfs/volumes/01234567-89abcdef-0123-456789abcdef/"
-->    msg = ""
--> }
--> Args:
--> /
--> Arg cnxSpec:
--> Arg reconnectSpec:


VMware vSphere ESXi 7.x
VMware vSphere ESXi 6.7
VMware vCenter Server 6.7.x


This issue occurs if vCenter updates /etc/hosts file with incorrect or out of order entries when the ESXi hosts are reconnected.


There is no resolution, this is due to individual DNS configuration.


Connect to the vCenter Server and correct the /etc/hosts file.

1. Connect to the VCSA through SSH or its virtual machine console and authenticate as the root user.
2. Examine the /etc/hosts file entry for the affected host(s).

# cd /etc/
# cat hosts |less

Generally, for each device entry, the IP address is first, followed by the Fully Qualified Domain Name (FQDN), followed by the shortname.
192.168.x.x myhost01.mydomain.com myhost01
  • In most environments, having entries in /etc/hosts to resolve device IPs is unnecessary as DNS performs this function -- however, it might be used more frequently in VXRail environments. If there is any question about this in a VXRail environment, please contact Dell/EMC for support.

  • Cases have been seen where the order of the hosts FQDN/shortname entries have gotten reversed or are showing a different FQDN than previously.

3. If you see that the entry for the affected host is incorrect, edit the hosts file to fix the entry.

Note: Make a backup copy of the hosts file then edit the file  (# cp hosts hosts.bak)

# vi hosts
Use the INSERT key to go into edit mode.
Fix the entries
Use ESC key to exit edit mode.
Use :wq to save
Use :q! if you've made a mistake and decided you want to start fresh.

If the work-around does not work due to a different cause of the issue, contact VMware Support and note this Article ID (78403) in the problem description. For more information, see How to Submit a Support Request.

Additional Information


Affected ESXi hosts may not be able to be reconnected and managed by vCenter or are not able to be updated following the error.