Loading

×Sorry to interrupt
CSS Error

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

Skip to main content

My Subscriptions

Loading

Knowledge Base

Migration or power on operations fail in VMware environments using NFS datastores (1005930)

Last Updated: 12/12/2013Categories: Total Views: 12539Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

While conducting a Live Migration or while trying to power on a virtual machine after a migration, you may experience one of the following symptoms:

VMware Infrastructure (VI) Client generates the error:

Failed to open the swap file.

VI Client generates the error:

A general system error occurred. Source detected that destination failed to resume

While using the Migration wizard, you receive the warning:

The virtual machine must be powered off to perform this function

Resolution

Cause

Migration or power on operations may fail due to a mismatch in the datastore UUID. If two ESX hosts represent that datastore using a different UUID in /vmfs/volumes you may experience issues performing power on or migration operations.

Identifying the issue

To verify if you have a mismatch between UUIDs:

Log into the ESX host which is successfully running the virtual machine as root via SSH or at the console.

Run the command:

ls -l /vmfs/volumes

The output appears similar to:

drwxrwxrwt 1 root root 980 May 29 09:25 8687c82b-3e59cbae
lrwxr-xr-x 1 root root 17 Jun 11 12:51 vm_nfs_disk -> 8687c82b-3e59cbae

Make note of the UUID (highlighted in red).

Log into the ESX host which cannot power on or accept migration of the virtual machine as root via SSH or at the console.

Run the command:

ls -l /vmfs/volumes

The output appears similar to:

drwxrwxrwt 1 root root 980 May 29 09:25 fef0f955-dceeecfc
lrwxr-xr-x 1 root root 17 Jun 11 12:51 vm_nfs_disk -> fef0f955-dceeecfc

Make note of the UUID (highlighted in blue).

If the values recorded in step 3 and in step 6 are not the same, then you have a UUID mismatch.

Solution

A UUID mismatch between two datastores occurs because the UUID is based on a hash of the NFS Server and Path, as seen by running esxcfg-nas. If you have specified the NFS server information using different methods on different hosts, then the hash value, and ultimately the UUIDs will be different.

To resolve the mismatch:

Log into the ESX host which is successfully running the virtual machine as root via SSH or at the console.

Run the command:

esxcfg-nas -l

The output appears similar to:

nfs_datastore is /vol/nfs_datastore from nfs-server.private.example.com mounted

Note: The UUID is based on /vol/nfs_datastore and the DNS name nfs-server.private.example.com.

Make note of the method being used to identify the NFS server highlighted in red.

Log into the ESX host which cannot power on or accept migration of the virtual machine as root via SSH or at the console.

Run the command:

esxcfg-nas -l

The output appears similar to:

nfs_datastore is /vol/nfs_datastore from 192.168.1.150 mounted

Note: The UUID is based on /vol/nfs_datastore and the IP address 192.168.1.150.

Make note of the method being used to identify the NFS server highlighted in blue.

Choose one method to identify the NFS server (DNS or IP).

Select the host which is not using the method selected in step 7.

Connect to the host using VI Client with the appropriate permissions.

Power off (or relocate if possible) the virtual machines residing on the NFS datastore which has the mismatch.

Remove the NFS datastore.

Add the same datastore using the method selected in step 7. For more information, see Creating an NFS-Based Datastore documentation for the applicable version of VMware product in the ESX Configuration Guide.

Repeat the operation until all ESX hosts reference the same NFS server in the same method selected in step 7.

Related Information

Note: If the two hosts with mismatched NFS datastore mounts are managed by vCenter Server, one of the NFS datastore mounts may be renamed with a (1) suffix to differentiate them. To prevent this issue from occurring, ensure that the NFS mount has been unmounted from all ESX/ESXi hosts before mounting using the IP address.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

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 ESX Server

Related Versions:

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant