Enthusiast
Enthusiast

nfs mount

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

0 Kudos
8 Replies

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

0 Kudos
Enthusiast
Enthusiast

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

DSM 6.2.3-25426 Update 2

if that mattters

0 Kudos
Enthusiast
Enthusiast

Can you try switching to NFS v3 ?

0 Kudos
Enthusiast
Enthusiast

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.

0 Kudos

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?

0 Kudos
Enthusiast
Enthusiast

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

0 Kudos
Enthusiast
Enthusiast

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

0 Kudos
Enthusiast
Enthusiast

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

0 Kudos