How can I troubleshoot when I'm unable to mount my Storage Gateway NFS file share on my NFS client?
Last updated: 2020-10-05
I created a Network File System (NFS) file share on AWS Storage Gateway. I want to mount the NFS file share on my NFS client, but it's not working. How can I troubleshoot this?
1. Confirm that your NFS client is among the supported NFS clients for a file gateway.
2. Use the Storage Gateway console to check if your file share is in the unavailable state. If the file share is in the unavailable state, then check if the file gateway can reach the Amazon Simple Storage Service (Amazon S3) endpoint. To do this, run a telnet command using an Amazon Elastic Compute Cloud (Amazon EC2) instance with the same network configuration as the gateway. The instance must also be in the same subnet as the gateway.
telnet s3.amazonaws.com 443 telnet AWSDOC-EXAMPLE-BUCKET.s3.us-west-2.amazonaws.com 443
3. Confirm that the NFS client is installed on your client. On a Windows Server client, navigate to the Server Manager. Choose Add roles and features, and then choose Next until you reach the Features page. Select Client for NFS, choose Next, and then choose Install.
On a Linux client, you can run the following command:
yum -y install nfs-utils
To check that the NFS service is running, run this command:
service nfs status
If the NFS service isn't running, run this command to start the service:
service nfs start
4. Review your network configuration to confirm that the required ports are open between the client and the Storage Gateway host or appliance. NFS version 3 clients require ports 111 and 20048. NFS version 4 clients require port 2049. To check if the required ports are open, run the telnet command from your client to the Storage Gateway host:
Important: Replace 192.0.2.0 with the IP address of your file gateway.
telnet 192.0.2.0 2049 telnet 192.0.2.0 20048 telnet 192.0.2.0 111