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

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

Troubleshooting NFS datastore connectivity issues (1003967)

Last Updated: 6/14/2023Categories: TroubleshootingTotal Views: 325236Language:
Chinese (Simplified)JapaneseEnglish

14 like this article

Subscribe to get an email
newsletter with new updates

14 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

The NFS share cannot be mounted by the ESXi host.

The NFS share is mounted, but nothing can be written to it.

The NFS datastore is inaccessible.

You see entries similar to:

NFS Error: Unable to connect to NFS server

WARNING: NFS: 983: Connect failed for client 0xb613340 sock 184683088: I/O error

WARNING: NFS: 898: RPC error 12 (RPC failed) trying to get port for Mount Program (100005) Version (3) Protocol (TCP) on Server (xxx.xxx.xxx.xxx)

Network cable is unplugged

Resolution

To resolve this issue, validate that these steps are true for your VMware environment:

Caution: Do not skip a step. The steps provide instructions or a link to a document for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution.

Check the MTU size configuration on the port group which is designated as the NFS VMkernel port group. If it is set to anything other than 1500 or 9000, test the connectivity using the vmkping command:

# vmkping -I vmkN -s nnnn xxx.xxx.xxx.xxx

Where:

vmkN is vmk0, vmk1, etc, depending on which vmknic is assigned to NFS.
nnnn is the MTU size minus 28 bytes for overhead. For example, for an MTU size of 9000, use 8972.

xxx.xxx.xxx.xxx is the IP address of the target NFS storage.

To reveal the vmknics, run the command:

esxcfg-vmknic -l

Check the output for the vmk_ interface associated with NFS.

Verify connectivity to the NFS server and ensure that it is accessible through the firewalls. For more information, see Cannot connect to NFS network share (1007352).

Run the netcat (nc) command to see if you can reach the NFS server nfsd TCP/UDP port (default 2049) on the storage array from the host:

# nc -z array-IP 2049

Example output:

Connection to 10.1.10.100 2049 port [tcp/http] succeeded!

Verify that the ESXi host can vmkping the NFS server. For more information, see Testing VMkernel network connectivity with the vmkping command (1003728).

Verify that the NFS host can ping the VMkernel IP of the ESXi host.

Verify that the virtual switch being used for storage is configured correctly.

Note: Ensure that there are enough available ports on the virtual switch.

Verify that the storage array is listed in the VMware Hardware Compatibility Guide. For more information, see the VMware Compatibility Guide. Consult your hardware vendor to ensure that the array is configured properly.

Note: Some array vendors have a minimum microcode/firmware version that is required to work with the ESXi host.

Verify that the physical hardware functions correctly. Consult your hardware vendor for more details.

If this is a Windows server, verify that it is correctly configured for NFS. For more information, see Troubleshooting the failed process of adding a datastore from a Windows Services NFS device (1004490).

To troubleshoot a mount being read-only:

Verify that the permissions of the NFS server have not been set to read-only for this ESXi host.

Verify that the NFS share was not mounted with the read-only box selected.

In addition please see: Remounting a disconnected NFS datastore from the ESXi command line (1005057)

If the above troubleshooting has not resolved the issue and there are still locked files, e.g. attempting to unmount the NAS volume may fail with an error similar to:

WARNING: NFS: 1797: 8564d0cc-58f6-4573-886f-693fa721098c has open files, cannot be unmounted

To troubleshoot the lock:

Identify the ESXi host holding the lock. For more information, see Investigating virtual machine file locks on ESXi host (10051).

Restart the management agents on the host. For more information, see Restarting the Management agents in ESXi (1003490).

If the lock remains, a host reboot is required to break the lock.

Note: If you wish to investigate the cause of the locking issue further, ensure to capture the host logs before rebooting.

Related Information

VMware Skyline Health Diagnostics for vSphere - FAQ

"An error occurred while consolidating disks:" deleting one or more snapshots or consolidate disks

If an attempt is made to mount NFS share over UDP, in the /var/log/vmkernel.log file, you see an error similar to:

WARNING: NFS: 918: Server (10.x.x.x) does not support Mount Program (100005) Version (3) Protocol (TCP)

Testing VMkernel network connectivity with the vmkping command

Troubleshooting the failed process of adding a datastore from a Windows Services NFS device

Network cable of a virtual machine appears unplugged

Cannot connect to NFS network share

Collecting diagnostic information for VMware products

No network connectivity if all ports are in use

Deleting a large file on the NFS datastore succeeds, but reports the error: Error caused by file /vmfs/volumes/<datastore-uuid>/<filename>

Troubleshooting VMDK and RDM dedupe datastore issues in VMware Data Recovery

Using nfsstat3 to troubleshoot NFS error: Failed to get object: No connection

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 8.0.x

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

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