I'm working on my homelab server and trying to replace the drives in one of my datastores with some that have a higher capacity. I need to move the VMDK files off this datastore prior to removing the drives and I'm having some issues connecting it to my NAS to do so. The NAS is a Synology DS 214 and I've gone through the setup on it and can successfully connect to the NFS share using my Mac. When I try to add the NFS datastore though it always errors out. I've tried doing this with NFS 3 and 4 but get the same result with both.
Export from NFS share
/volume1/vmNFS01 *(rw,async,no_wdelay,crossmnt,insecure,root_squash,insecure_locks,sec=sys,anonuid=1024,anongid=100)
VMKernel.log
2018-09-20T16:40:20.381Z cpu10:67593 opID=ea1fafab)NFS: 157: Command: (mount) Server: (192.168.1.200) IP: (192.168.1.200) Path: (/volume/vmNFS01) Label: (vmNFS) Options: (None)
2018-09-20T16:40:20.381Z cpu10:67593 opID=ea1fafab)StorageApdHandler: 977: APD Handle 0596ba14-9a61641f Created with lock[StorageApd-0x4309197f7ea0]
2018-09-20T16:40:20.381Z cpu10:67593 opID=ea1fafab)CpuSched: 692: user latency of 68339 RPC-tx-192.168.1.200.0.111 0 changed by 67593 hostd-worker -6
2018-09-20T16:40:50.628Z cpu15:67593 opID=ea1fafab)SunRPC: 1116: Destroying world 0x10af3
2018-09-20T16:40:50.628Z cpu15:67593 opID=ea1fafab)StorageApdHandler: 1062: Freeing APD handle 0x4309197f7ea0 [0596ba14-9a61641f]
2018-09-20T16:40:50.628Z cpu15:67593 opID=ea1fafab)StorageApdHandler: 1147: APD Handle freed!
2018-09-20T16:40:50.628Z cpu15:67593 opID=ea1fafab)NFS: 168: NFS mount 192.168.1.200:/volume/vmNFS01 failed: Unable to connect to NFS server.
Anyone have any ideas what's going on?
Message says server is unable to connect to the NAS server
Ensure you can use the command vmkping <nfs server ip address> to check you can ping the nfs server.
Since this is a very generic error, try isolating the problem with the help of the KB - VMware Knowledge Base
Cheers,
Supreet
I'm not familiar with Synology systems, but I think that "root_squash", should be changed to "no_root_squash".
André
Yes I receive a response.
I'm working through this checklist. For the netcat test, what is the storage array IP of the host? Is that the IP of my NAS? IF so I've tried that and get no response from that command.
I think you are correct. I changed that when testing connectivty on the Mac. I changed it back to no_root_squash and receive the same issue.
Yes, it is the NAS IP. If the connection did not succeed, then the port might not be open. Is there a firewall between the host and the NAS box? Any other chances of the port being blocked in the route?
Cheers,
Supreet
OK so I did some testing on the ports. I know the port is open on the Synology as I can run netcat from another device on the network and that is successful. I have port mirroring on one of the switch ports and can see this traffic in Wireshark. When I attempt the netcat from the ESXi host, I don't see any traffic in Wireshark using port 2049. So it seems to me that something is stopping the traffic from leaving the ESXi server?
I just disabled the firewall on the ESXi server and that allowed the netcat test to succeed but I'm still unable to mount the NFS share. When I view the attempt in Wireshark, all I see is Syn packets from the ESXi server to the NAS and then retransmissions. No packets from the NAS to the ESXi server. I also tried disabling the Firewall on the NAS but that didn't change anything.
Hi grayfold3d,
Did you fix your issue? i am facing the similar issue Strange Issue : NFS datastore can't be mounted only to several ESXi hosts
Please help to share the resolution if you already fixed the issue
Thanks alot
Nope sorry. I just needed it temporarily and ended up using iSCSi LUN.
Hehh, I have the same problem. Question is about account that ESXi uses to access NFS. And this account is "root". But usually in NAS storage "root" is disabled and you cant create new root account for ESXi. You can by SSH hack NAS box and enable root account, but it still have different password and then you must also make passwords the same. It goes little crazy administration. Root sqash dont help, because account is still wrong. Squash simple reduces remote "root" user privileges in local NAS box. But username "root" and password must still fit before login. Officially VMWare uses new 4.1 NFS in newer ESXi and this allows authentication through AD domain. But this also goes too crazy, because I dont have domain and little strange is to put up AD just for NFS. But I was needed NFS because it allows shared storage. Some other software need shared storage. iSCSI cant be shared because its SAN. But NFS is usual filesharing and can be shared between ESXi-s. So, also is possible to put up some other NFS server. Even it can be done in Windows if activated Linux stuff. I once tried it with windows and it worked. But its also not good scenario - I have NAS hardware storage and still must make some software hack, its depressing. Maybe for Synology or Qnap have some 3rd-party NFS server software that accepts "root" user.
