Linux NFS Mount: wrong fs type, bad option, bad superblock on fs2:/data3 Error And Solution

by on June 12, 2010 · 4 comments· LAST UPDATED June 12, 2010

in , ,

I've netapp NFS server with /data3 as shared directory. I type the following command at Ubuntu Linux to mount the NFS server:

mount fs2:/data3 /nfs/
OR
mount 192.168.1.100:/data3 /nfs/

But I'm getting an error which read as follows:

mount: wrong fs type, bad option, bad superblock on fs2:/data3,
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount. helper program)
In some cases useful info is found in syslog - try
dmesg | tail or so

How do I fix this problem?

NFS client needs portmap service, simply install nfs-comman package as follows to fix this problem:
$ sudo apt-get install nfs-common
Make sure portmap service is running:
sudo service portmap status
Sample outputs:
portmap start/running, process 4193
If not just start it:
$ sudo service portmap start
One installed you can see all shared NFS directories as follows:
showmount -e fs2
Sample outputs:

Export list for fs2:
/Sales
/Web
/Accounting
/Recordings
/Public
/Network Recycle Bin 1
/Music
/Download
/Games
/Family

Simply run mount command again:
$ sudo mkdir /nfs
$ sudo mount fs2:/data3 /nfs/
$ ls /nfs

See also:

TwitterFacebookGoogle+PDF versionFound an error/typo on this page? Help us!

{ 4 comments… read them below or add one }

1 Meisterschaft June 13, 2010 at 2:25 pm

You should also make sure that the portmapper service is actually running properly and listening to its assigned port. (described previously by Vivek). Here is the command:
#netstat -an | grep LISTEN
In the output of the command you should look for the port 111, which is the default port of portmapper (a.k.a. rpc.bind). This port makes sure that services that run on Linux can communicate with one another using pre-defined ports (for example you contact your filer from your machine using the port 2049, which is the default NFS port).

Also, make sure that the important daemons that ensure a successful NFS connection (mountd, nfsd, nlockm) are also active. You can do that with the command:
#/etc/init.d/nfs status (it’s true, this is for RedHat-based distros, I’m not very Debian-oriented…). If they are not running execute an /etc/init.d/nfs start

Also, on your server-side (you filer) you should verify the integrity of the disks connected to your client-machine, using the disk scrubbing options offered by NetApp (disk scrub start)

Reply

2 qt2r June 14, 2010 at 11:42 am

Thanks for posting information about disk scrubbing.

Reply

3 Nanda July 26, 2011 at 10:51 am

Thanks, this saved a headache…

Reply

4 Carsten March 19, 2013 at 2:29 pm

Make sure to have nfs-common installed on the client side :)

Reply

Leave a Comment

Tagged as: , , , , , , , , , , , , ,

Previous Faq:

Next Faq: