ESXi

 View Only
Back to discussions
Expand all | Collapse all

nfs mount

  • 1.  nfs mount

    Posted Sep 29, 2020 09:22 PM

    I'm trying to remote a NFS datastore in ESXi 6.5, but it keeps failing.  I tailed the vmkernel.log file and here is the output.  Any idea whats failing?

    i can mount this share on other machines without problem(s), this is a share on Synology NAS (if that matters?)

    2020-09-29T15:12:32.437Z cpu1:67570 opID=d3a85b95)World: 12230: VC opID esxui-21fa-967a maps to vmkernel opID d3a85b95

    2020-09-29T15:12:32.437Z cpu1:67570 opID=d3a85b95)NFS41: NFS41_VSIMountSet:423: Mount server: 10.1.1.31, port: 2049, path: esxi, label: nas, security: 1 user: , options: <none>

    2020-09-29T15:12:32.437Z cpu1:67570 opID=d3a85b95)StorageApdHandler: 977: APD Handle  Created with lock[StorageApd-0x4306f58bed70]

    2020-09-29T15:13:02.436Z cpu2:67570 opID=d3a85b95)WARNING: NFS41: NFS41FSWaitForCluster:3637: Failed to wait for the cluster to be located: Timeout

    2020-09-29T15:13:02.436Z cpu2:67570 opID=d3a85b95)WARNING: NFS41: NFS41_FSMount:4683: NFS41FSDoMount failed: Timeout

    2020-09-29T15:13:02.436Z cpu2:67570 opID=d3a85b95)StorageApdHandler: 1062: Freeing APD handle 0x4306f58bed70 []

    2020-09-29T15:13:02.436Z cpu2:67570 opID=d3a85b95)StorageApdHandler: 1147: APD Handle freed!

    2020-09-29T15:13:02.436Z cpu2:67570 opID=d3a85b95)WARNING: NFS41: NFS41_VSIMountSet:431: NFS41_FSMount failed: Timeout

    2020-09-29T15:13:02.438Z cpu3:66344)SunRPC: 1116: Destroying world 0x75966



  • 2.  RE: nfs mount

    Posted Sep 29, 2020 09:26 PM

    If you log in to the host, are you able to ping the NFS server?



  • 3.  RE: nfs mount

    Posted Sep 29, 2020 09:29 PM

    yes, I can ping it no problem there.  The synology NAS is running version:

    DSM 6.2.3-25426 Update 2

    if that mattters



  • 4.  RE: nfs mount

    Posted Sep 30, 2020 07:53 AM

    Can you try switching to NFS v3 ?



  • 5.  RE: nfs mount

    Posted Sep 30, 2020 09:28 PM

    no go either on v3:

    From the UI:

    Failed to mount NFS datastore nas - NFS mount 10.1.1.31:esxi failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it. - dismiss

    from vmkernel.log:

    2020-09-30T21:26:20.973Z cpu0:65934)nhpsa: hpsa_FillCmd:2604: Failed to allocate command.

    2020-09-30T21:26:20.973Z cpu0:65934)nhpsa: hpsa_RuntimeDevScanPhysical:13428: Failed to fillCmd to execute report physical lun.

    2020-09-30T21:26:20.973Z cpu0:65934)nhpsa: hpsa_FillCmd:2604: Failed to allocate command.

    2020-09-30T21:26:20.973Z cpu0:65934)nhpsa: hpsa_RuntimeDevScanLogical:13489: Failed to fillCmd to execute report logical lun.



  • 6.  RE: nfs mount

    Posted Sep 30, 2020 10:26 PM

    Hey, I have two options:
    a) Is it possible that the NFS server has some kind of whitelist that allows or denies access from ESXi server?

    b) are you sure that the credentials are right?



  • 7.  RE: nfs mount

    Posted Sep 30, 2020 11:50 PM

    making progress, but still not there, new/different error messages now

    from vmkernel.log:

    2020-09-30T23:48:25.697Z cpu4:67569 opID=8ac87db1)World: 12230: VC opID esxui-cd3a-1143 maps to vmkernel opID 8ac87db1

    2020-09-30T23:48:25.697Z cpu4:67569 opID=8ac87db1)NFS41: NFS41_VSIMountSet:423: Mount server: 10.1.1.31, port: 2049, path: esxi, label: nas, security: 1 user: , options: <none>

    2020-09-30T23:48:25.697Z cpu4:67569 opID=8ac87db1)StorageApdHandler: 977: APD Handle  Created with lock[StorageApd-0x4306f58bed70]

    2020-09-30T23:48:25.698Z cpu4:66344)WARNING: NFS41: NFS41ExidPathProcess:2126: Server doesn't support the NFS 4.1 SunRPC program

    2020-09-30T23:48:35.700Z cpu4:66344)WARNING: NFS41: NFS41ExidPathProcess:2126: Server doesn't support the NFS 4.1 SunRPC program

    2020-09-30T23:48:45.700Z cpu4:66344)WARNING: NFS41: NFS41ExidPathProcess:2126: Server doesn't support the NFS 4.1 SunRPC program

    2020-09-30T23:48:55.697Z cpu4:67569 opID=8ac87db1)WARNING: NFS41: NFS41FSWaitForCluster:3637: Failed to wait for the cluster to be located: Timeout

    2020-09-30T23:48:55.697Z cpu4:67569 opID=8ac87db1)WARNING: NFS41: NFS41_FSMount:4683: NFS41FSDoMount failed: Timeout

    2020-09-30T23:48:55.697Z cpu4:67569 opID=8ac87db1)StorageApdHandler: 1062: Freeing APD handle 0x4306f58bed70 []

    2020-09-30T23:48:55.697Z cpu4:67569 opID=8ac87db1)StorageApdHandler: 1147: APD Handle freed!

    2020-09-30T23:48:55.697Z cpu4:67569 opID=8ac87db1)WARNING: NFS41: NFS41_VSIMountSet:431: NFS41_FSMount failed: Timeout

    2020-09-30T23:48:55.698Z cpu5:66344)SunRPC: 1116: Destroying world 0x7af79



  • 8.  RE: nfs mount

    Posted Oct 01, 2020 05:04 PM

    Hi

    It looks like you switched to NFS v3 on your synology box, but the host is still trying to mount volume using nfs v4.1.

    Please try to mount volume using NFS v3 on the ESXi

    The previous error is related to the fact that when you export NFS on the datastore unit with v3 you should provide export policy that mentions IP range of hosts that are allowed to access the volume.

    Please check this guide:

    https://miketabor.com/setup-nfs-on-synology-nas-for-vmware-esxi-lab/

    It might be able to help you



  • 9.  RE: nfs mount

    Posted Oct 01, 2020 07:43 PM

    vmkernel.log here when trying v3:

    2020-10-01T19:41:41.809Z cpu6:67571 opID=fcc265db)World: 12230: VC opID esxui-35b8-6715 maps to vmkernel opID fcc265db

    2020-10-01T19:41:41.809Z cpu6:67571 opID=fcc265db)NFS: 157: Command: (mount) Server: (10.1.1.31) IP: (10.1.1.31) Path: (esxi) Label: (nas) Options: (None)

    2020-10-01T19:41:41.809Z cpu6:67571 opID=fcc265db)StorageApdHandler: 977: APD Handle a42df7cb-f67b0e12 Created with lock[StorageApd-0x430745c09e90]

    2020-10-01T19:41:41.811Z cpu6:67571 opID=fcc265db)SunRPC: 1116: Destroying world 0x7ed1f

    2020-10-01T19:41:41.812Z cpu6:66130)WARNING: NFS: 221: Got error 13 from mount call

    2020-10-01T19:41:41.812Z cpu6:67571 opID=fcc265db)SunRPC: 1116: Destroying world 0x7ed20

    2020-10-01T19:41:41.812Z cpu6:67571 opID=fcc265db)StorageApdHandler: 1062: Freeing APD handle 0x430745c09e90 [a42df7cb-f67b0e12]

    2020-10-01T19:41:41.812Z cpu6:67571 opID=fcc265db)StorageApdHandler: 1147: APD Handle freed!

    2020-10-01T19:41:41.812Z cpu6:67571 opID=fcc265db)NFS: 190: NFS mount 10.1.1.31:esxi failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it.

    I don't see on the Synology where I can specify the NFS version, but will investigate this

    thanks



  • 10.  RE: nfs mount

    Posted Sep 03, 2023 10:21 PM
     wrote:

     

    I don't see on the Synology where I can specify the NFS version, but will investigate this

    Hi  - Have a look at the screenshot below from my Synology. The NFS version is specified by going to Control Panel>File Services. I have mine set to NFS v3, and the read/write host access list set to * (meaning all hosts), as this is a homelab environment, and this just makes things easier. Obviously you can start with the basics just to get things working, then refine as needed later.

    markey165_1-1693779112171.png

     

    HTH

     

     



  • 11.  RE: nfs mount

    Posted Sep 03, 2023 07:32 PM

    The log messages you provided indicate that there's a timeout issue when attempting to mount an NFS datastore in ESXi 6.5. This error message suggests that ESXi is unable to establish a connection or complete the mount operation to your Synology NAS NFS share within the expected time frame.

    The most common reasons for NFS mount timeouts in ESXi are:

    1. Network Issues: Ensure that there are no network problems between your ESXi host and the Synology NAS. Check for connectivity issues, firewalls, and routing problems.

    2. NFS Server Configuration: Verify that the NFS server (your Synology NAS) is correctly configured to allow ESXi to access the share. Ensure that NFS services are running and that the share is properly exported with the correct permissions.

    3. NFS Server Load: Check the load on your Synology NAS. If the NAS is heavily loaded or experiencing resource constraints, it may not respond in a timely manner to NFS mount requests.

    4. Firewall Settings: Ensure that there are no firewall rules blocking NFS traffic between the ESXi host and the Synology NAS.

    5. NAS Access Control: Check that the NAS allows access from the ESXi host. This includes checking the NAS's access control lists (ACLs) and ensuring that the ESXi host has the necessary permissions.

    6. NFS Version Compatibility: Verify that the NFS version being used (NFSv3, NFSv4, etc.) is supported by both ESXi and the Synology NAS. You may need to specify the NFS version in the ESXi mount options.

    7. ESXi Configuration: Check the ESXi NFS client settings, including firewall settings on ESXi itself.

    8. NAS Logs: Review the logs on your Synology NAS to see if there are any NFS-related error messages or access denied messages that might provide additional clues.

    By investigating these areas, you should be able to identify and resolve the NFS mount timeout issue on your ESXi host when connecting to the Synology NAS NFS share.

     

    You can also take help from these resources.

    https://communities.vmware.com/t5/ESXi-Discussions/Invisible-NFS-mount-problem/m-p/485872 

    https://communities.vmware.com/t5/ESXi-Discussions/NFS-datastore-mounted-as-read-only/m-p/2980987 

    https://communities.vmware.com/t5/ESXi-Discussions/Unable-to-Mount-NFS-Datastore/m-p/462356 https://oldrollmodapk.com 

    https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-0-NFS-v4-1-Not-mounting/m-p/1851023 



  • 12.  RE: nfs mount

    Posted Jan 12, 2024 02:57 AM

    The log messages you provided indicate a timeout issue when attempting to mount an NFS datastore in ESXi 6.5. This error implies that ESXi cannot establish a connection or complete the mount operation to your Synology NAS NFS share within the expected time.

    Common reasons for NFS mount timeouts in ESXi include:

    1. Network Issues: Ensure there are no network problems between your ESXi host and the Synology NAS. Check for connectivity issues, firewalls, and routing problems.

    2. NFS Server Configuration: Verify that the NFS server (Synology NAS) is correctly configured to allow ESXi to access the share. Ensure NFS services are running and the share is properly exported with the correct permissions.

    3. NFS Server Load: Check the load on your Synology NAS. If it's heavily loaded or experiencing resource constraints, it may not respond timely to NFS mount requests.

    4. Firewall Settings: Ensure there are no firewall rules blocking NFS traffic between the ESXi host and the Synology NAS.

    5. NAS Access Control: Confirm that the NAS allows access from the ESXi host. This includes checking NAS access control lists (ACLs) and ensuring the ESXi host has the necessary permissions.

    6. NFS Version Compatibility: Verify that the NFS version in use (NFSv3, NFSv4, etc.) is supported by both ESXi and the Synology NAS. You might need to specify the NFS version in the ESXi mount options.

    7. ESXi Configuration: Check ESXi NFS client settings, including firewall settings on ESXi itself.

    8. NAS Logs: Review Synology NAS logs for any NFS-related error messages or access denied messages that might provide additional clues.

    By investigating these areas, you should identify and resolve the NFS mount timeout issue on your ESXi host when connecting to the Synology NAS NFS share.

    For additional assistance, you can refer to these resources:
    https://communities.vmware.com/t5/ESXi-Discussions/Invisible-NFS-mount-problem/m-p/485872

    https://communities.vmware.com/t5/ESXi-Discussions/NFS-datastore-mounted-as-read-only/m-p/2980987

    https://communities.vmware.com/t5/ESXi-Discussions/Unable-to-Mount-NFS-Datastore/m-p/462356 https://teraboxmodapk.io/

    https://communities.vmware.com/t5/ESXi-Discussions/ESXi-7-0-NFS-v4-1-Not-mounting/m-p/1851023