Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 4/20/2023Categories: TroubleshootingTotal Views: 8252Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

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:
-->

Purpose

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

Cause

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

Impact / Risks

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

Resolution

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

Workaround

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.

Example:

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.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere ESXi

VMware vCenter Server

Related Versions:

VMware vSphere ESXi 7.x

VMware vSphere ESXi 6.7

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant