0

We have a NAS server in the lab and I can reach it through the web interface at 192.168.1.100, and I have enabled NFS on the admin's panel.

enter image description here

After that I did

sudo aptitude install nfs-common
sudo mount -t nfs4 192.168.2.254:/gwas_data /media/thecus

Result:

mount.nfs4: Connection timed out

OS is Ubuntu 14.04. Any ideas?

4
  • 4
    Tried replacing the IP address with your NAS's actual IP?
    – Mat
    Commented Dec 11, 2014 at 13:24
  • Possibly your firewall blocks the ports necessary for NFS (and maybe also rpcbind). Have a look at dmesg | tail right after trying the mount command.
    – Ned64
    Commented Apr 28, 2017 at 10:00
  • thecus OS5 or 6- slight changes to os7. hope it helps.
    – jmazzmans9
    Commented Jun 6, 2019 at 2:53
  • 1
    Also check the NFS version supported by the NAS. Sometimes they don't do NFSv4 so you may need to enable NFSv3 support client-side.
    – Ned64
    Commented Aug 3, 2020 at 15:05

2 Answers 2

0
  1. Create a public folder (FMBData in this example)
  2. Click on NFS to share it
  3. Set the hostname to the IP of the linux machine (e.g. 192.168.1.111)
  4. On the linux machine, sudo apt-get install nfs-common, sudo mkdir /media/thecus, then sudo mount -t nfs4 192.168.1.100:FMBData /media/thecus. You can get the WAN IP of the server on the front screen.

Screenshots:

enter image description here

enter image description here

1
  • 1
    Maybe you could detail which NAS this is for - there are several brands and firmware revisions and thiis question and answer is very specific.
    – Ned64
    Commented Apr 28, 2017 at 10:57
0

Asked 9 years, 9 months ago

per the comment.. Maybe you could detail which NAS this is for... this is often an important thing.

in regards to Synology NAS and their DSM 6 or 7 (whatever they are up to now) here is what I can share that may be helpful:

  • the following is with RHEL-8 Linux
  • check the /etc/nfs.conf and /etc/nfsmount.conf files in Linux, and also on the NAS assuming the NAS has an underlying Linux operating system (which Synology does, debian I believe, so you will find a familiar /etc folder structure).
    • recommend in RHEL 7 & 8 all items in nfs.conf and nfsmount.conf are commented out which is the default setup as it comes from redhat
    • if there is a mismatch between any parameter between nfsserver and nfsclient regarding nfs.conf and nfsmount.conf then that will cause the mount to fail; so this is the first place you should look
  • second place to look is firewall settings between both the nfsserver (the NAS) and the nfsclient (your Linux system). Simply disable both as a first diagnostic step to identify if the firewall is one of the culprits.
  • all you should need to do for mounting is mount nasserveripaddress://folder /folder
  • with Synology that is often something like mount 192.168.1.1:/Volume1/data nas_data for example
    • point here is Synology as it does its volumes and stuff, that shared folder syntax that is NFS exported can become tricky, so you want to identify that export syntax on the nfsserver (the NAS) and should be able to be identified in /etc/exports there. If the mount path is not correct then the mount will not happen.
  • Like was said the NAS make/model and it's operating system should be mentioned as things change; as of today it should default to NFS4, version 4.2 specifically with RHEL-8 or later and with RHEL-7.9 it was version 4.1. Regarding the mount syntax you should not specifically try to specify a version via the -t just let it auto choose and get a valid mount working first, then if the version is a problem go from there once you've successfully fixed any problems preventing the mount from happening in the first place.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .