NFS Mount fails Error : Unable to connect to NFS server
search cancel

NFS Mount fails Error : Unable to connect to NFS server

book

Article ID: 393660

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

  • Mounting of Datastore fails with below error:



  • NFS datastore mount fails, error appears -  An Error occurred during host configuration. Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.: Unable to connect to NFS server

Environment

VMware vSphere ESXi 8.x

Cause

The issue occurs due to connection failure between NFS server and ESXi host.

  • From /var/log/hostd.log: 

    2025-04-04T17:20:58.546Z info hostd[2101497] [Originator@6876 sub=Libs opID=m1x73n6h-24973346-auto-ev9k3-h5:74274300-2f-8-8493 user=vpxuser:#######\#######] VmFileSystemImpl: Probably unmounted volume. Console path not set for '#######-Storage'
    2025-04-04T17:20:58.548Z info hostd[2101497] [Originator@6876 sub=Libs opID=m1x73n6h-24973346-auto-ev9k3-h5:74274300-2f-8-8493 user=vpxuser:#######\#######] Refresh:Volume #######-Storage
    2025-04-04T17:20:58.550Z info hostd[2101497] [Originator@6876 sub=Libs opID=m1x73n6h-24973346-auto-ev9k3-h5:74274300-2f-8-8493 user=vpxuser:#######\#######] Refresh:Done. Volume Shared-Storage accessible 0 vaaiSupport 0
    2025-04-04T17:21:29.102Z error hostd[2101497] [Originator@6876 sub=Hostsvc.FSVolumeProvider opID=m1x73n6h-24973346-auto-ev9k3-h5:74274300-2f-8-8493 user=vpxuser:########/] VmkCtl mount or ProcessNas failed: Mount failed: Unable to complete Sysinfo operation.  Please see the VMkernel log file for more details.: Unable to connect to NFS server

    2025-04-04T17:21:29.113Z info hostd[2101497] [Originator@6876 sub=Solo.Vmomi opID=m1x73n6h-24973346-auto-ev9k3-h5:74274300-2f-8-8493 user=vpxuser:#######\#######] Throw vim.fault.PlatformConfigFault
    2025-04-04T17:21:29.113Z info hostd[2101497] [Originator@6876 sub=Solo.Vmomi opID=m1x73n6h-24973346-auto-ev9k3-h5:74274300-2f-8-8493 user=vpxuser:#######\#######] Result:
    --> (vim.fault.PlatformConfigFault) {
    -->    faultMessage = (vmodl.LocalizableMessage) [
    -->       (vmodl.LocalizableMessage) {
    -->          key = "com.vmware.esx.hostctl.default",
    -->          arg = (vmodl.KeyAnyValue) [
    -->             (vmodl.KeyAnyValue) {
    -->                key = "reason",
    -->                value = "Mount failed: Unable to complete Sysinfo operation.  Please see the VMkernel log file for more details.: Unable to connect to NFS server"
    -->             }
    -->          ],
    -->       }
    -->    ],
    -->    text = "",
    -->    msg = ""
    --> }
  • The vmknernel.log shows mount failure with NFS datastore.

    Log Path : less /var/run/log/vmkernel.log        
    2025-06-23T08:58:04.565Z In(182) vmkernel: cpu60:2099267 opID=##)NFS: 349: Command: (mount) Server: (###-###.bsc.####.com) IP: (10.##.###.###) Connections: (1) Vmknic: (None)  Path: (/prd_protected1) Label: (LAS-###-###-U###) Options: (None)
    2025-06-23T08:58:04.565Z In(182) vmkernel: cpu60:2099267 opID=bf2f6325)StorageApdHandler: 965: APD Handle 219f0b2a-####### Created with lock[StorageApd-0x4######]
    2025-06-23T08:58:14.955Z In(182) vmkernel: cpu60:2099267 opID=bf2f6325)SunRPC: 3615: Synchronous RPC cancel for client 0x4314e64016f0 IP 10.###.1##.####.0.## proc 3 xid 0x70733568 attempt 1 of 3
    2025-06-23T08:58:24.955Z In(182) vmkernel: cpu60:2099267 opID=##)SunRPC: 3615: Synchronous RPC cancel for client 0x4314e64016f0 IP ##.44.###.11#.0.### proc 3 xid 0x70733568 attempt 2 of 3
    2025-06-23T08:58:34.956Z In(182) vmkernel: cpu60:2099267 opID=##)SunRPC: 3615: Synchronous RPC cancel for client 0x4314e64016f0 IP 10.##.##.1##.0.1## proc 3 xid 0x70733568 attempt 3 of 3
    2025-06-23T08:58:34.956Z In(182) vmkernel: cpu60:2099267 opID=##)StorageApdHandler: 1051: Freeing APD handle 0x4315a6e03160 [219f0b2a-ebc91460]
    2025-06-23T08:58:34.956Z In(182) vmkernel: cpu60:2099267 opID=##)StorageApdHandler: 1135: APD Handle freed!
    2025-06-23T08:58:34.956Z In(182) vmkernel: cpu60:2099267 opID=##)NFS: 3500: NFS mount failed for lvebp-esx400.bsc.bscal.com:/prd_protected1 volume LAS-REP-NAS-UTIL. Status: Unable to connect to NFS server.

       Ping to NFS datastore fails:

         root@lvebp-e###:/vmfs/volumes/6210177a-#####-###-960ba###/esxlog] vmkping -I vmk3 -s 8972 172.##.##.2##
       PING 1##.26.###.###(1##.##1##.###): 8972 data bytes
       --- 1##.##.1##.2## ping statistics ---
         3 packets transmitted, 0 packets received, 100% packet loss   >>>>>>>>>>>>>>>pig failed for NFS server using dedicated vmk3 

     [root@lvebp-####:/vmfs/volumes/###-edebb9f0-###-####/esxlog] nc -zv ###.26.1##.2## 2##    
         nc: connect to 1##.26.##.###port 2049 (tcp) failed: Connection timed out                     >>>>>>>>>>>>>>>>>>>>>>>>NFS server connection failed via port 2049
        [root@lvebp-###:/vmfs/volumes/###-####-4d49-####/esxlog]
        Communication between ESXi host and NFS datastore fails.

Resolution

The current issue occurs if the network communication fails between ESXi host and NFS server. For validation using commands please efer the below article for isolation steps,

Validate Network Connectivity:
 
 Confirm that the ESXi can communicate with the NFS server.
 
  Use the following commands to check connectivity:
 
  vmkping <NFS_Server_IP>  
  nc -vz <NFS_Server_IP> 2049  

   Related KB : 310920

                        

Powered by Wolken Software