Troubleshooting NFS mounts under Linux/Unix.

Document Details

Article ID
T4133-1015

Last Review
July 23, 2007

Products
Wired NAS
Server Appliance
Web Server

Firmware Versions
1.43a

Related Articles

Related How-To Videos

 

When mounting a NAS shared folder from a Linux or Unix machine, the mount command may appear to “hang” or you may receive the following error message:

mount: wrong fs type, bad option, bad superblock on 172.16.1.150:/Backups,
or too many mounted file systems

 

There are three known issues that may cause this. You may have either created the NFS mapping incorrectly on the NAS, your Linux/Unix machine will not support NFSv2, or your mount version is set to lock the NFS mount. Our unit currently only supports NFSv2, and NFS versions are not backwards compatible with each other.

 

 

Step 1.

Make sure that you have correctly setup the NFS mapping on the NAS. The information you enter is found on the mapping machine. This is an example:

Remote UUID: 0
Remote IP: 192.168.1.50/24
Mapping User: root

You must make sure the remote UUID and mapping user match on the Linux/Unix machine. If you are on a 255.255.255.0 subnet, the “24” is the number entered after the <remote IP>/.

You must also make sure you have created the mapping user on the NAS and assigned that user rights to the folder you want mounted on the Linux/Unix machine.

Step 2.

While logged on as the mapping user on the Linux/Unix machine, type the following command to mount the NAS (you may use other mounting options, but this is the typical mount command):

mount –t nfs 192.168.1.50:/SharedFolderName LocalFolderName

If you receive no error message, you can type in “mount” to check the mounts you have on the machine.

If you receive an error message about “wrong fs type,” try the following command:

mount –o vers=2 192.168.1.50:/SharedFolderName LocalFolderName

The above command option “vers=2” should force the mount to use NFSv2. Note that some mount commands may differ, so if the aboce command does not work, do a help on the mount command to find the proper command.

Step 3.

If you still receive the above error, try the following command to disable locking on the NFS mount:

mount –o nolock 192.168.1.50:/SharedFolderName LocalFolderName

Note that some mount commands may differ, so if the aboce command does not work, do a help on the mount command to find the proper command.