troubleshooting Question

Linux NFS share not mounting from vSphere 4.1 host

Avatar of lhrslsshahi
lhrslsshahi asked on
LinuxLinux SecurityVMware
16 Comments2 Solutions981 ViewsLast Modified:
When trying to mount a NFS Linux  share from the vSphere 4.1 host I get the below.

NFS Errors 149, 946, 160

The same NFS shares are accessible from the another host.

I can ping the NFS server from the host. Netcat reaches the NFS server from the host.

The NFS server can also ping the VMware host and resolve DNS.


Dec 22 10:07:19 vmkernel: 1143:21:50:57.036 cpu2:4310573)NFS: 149: Command: (mount) Server: (192.168.20.10) IP: (192.168.30.10) Path: (/finkdr) Label: (backup) Options: (None)
Dec 22 10:07:49 vmkernel: 1143:21:51:27.089 cpu3:4310573)WARNING: NFS: 946: MOUNT RPC failed with RPC status 13 (RPC was aborted due to timeout) trying to mount Server (192.168.20.10) Path (/finkdr)
Dec 22 10:07:49 vobd: Dec 22 10:07:49.956: 98833888868410us: [esx.problem.vmfs.nfs.mount.connect.failed] Failed to mount to server 192.168.20.10 mount point /finkdr. Error: Unable to connect to NFS server.
Dec 22 10:07:49 vmkernel: 1143:21:51:27.089 cpu3:4310573)NFS: 160: NFS mount 192.168.30.10:/finkdr failed: Unable to connect to NFS server
ASKER CERTIFIED SOLUTION
Join our community to see this answer!
Unlock 2 Answers and 16 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 16 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros