[SOLVED] nfs Mount doesn't work

[MiB07]

mount 192.168.5.10:/share/HDA_DATA/Public
mount: wrong fs type, bad option, bad superblock on 192.168.5.10:/share/HDA_DATA/Public,

everytime i try i get this message. Does anyone know the reason?

my fstab-entry looks like this:

192.168.5.10:/share/HDA_DATA/Public /public nfs user,auto 0 0
or
192.168.5.10:/Public /public nfs user,auto 0 0

intr,noauto etc. didn't

with smbfs it doesn't work as well

the mount command directly has the same response

[AndyChuo]

just to make sure, did u enable it from teh admin back end?

[MiB07]

just to make sure, did u enable it from teh admin back end?

Yes for sure - the access- settings seem to be ok to. IP / Domain *
and no restriction enabled

it's a 109pro - with version 1.1.4 / 1.1.3 was the same situation

[TheEnvoy]

your commands are missformed, you need to use the shares as they are exported...

so it is: mount -t nfs IP:/Public /public
or in fstab: IP:/Public /public nfs user,auto 0 0

on commandline you can also use tab completition to see if your on the right path, after the
IP and the colon you should get a list of available shares by hitting the TAB key

furthermore the command to mount a smb share would be:
mount -t smb //IP/Public /public
or better, because newer and under ongoing development
mount -t cifs //IP/Public /public

this should work out, if not, come again

regards
TheEnvoy

[MiB07]

I'm sorry - my form was / is the same - ok the tabspaces are maybe missing -
Just to be sure - i tryed your entry - the same thing happens -

mount -t nfs 192.168.5.10:/Public /public
mount: wrong fs type, bad option, bad superblock on 192.168.5.10:/Public,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

i believe it should be smbfs ...

the response doesn't change

IP:/Public /public nfs user,auto 0 0
IP:/share/HDA_DATA/Public /public nfs user,auto 0 0
//IP/Public smbfs user,auto 0 0
did i forget one?

i hope so ... i don't know how to go on

[Leatherman]

Did anyone find a solution for this? I appear to have the same issue on my 109 Pro. I have just installed Ubuntu. NFS is activated on the device and I am using sudo mount -t nfs 192.168.X.X:/Public /mnt/Public. I get this same message. Thanks in advance.

[MiB07]

I thougth i was the only one - hmm. In the next few days i'll reinstall my pc - a disk is crashed - nothing important - maybe that will solve the problem.
If not :-/ I don't like to think about it.

[cute_l]

Hi,
I had the same problem here (mount: wrong fs type ...), also on Ubuntu (Gutsy).
Installing the package nfs-common solved this, now nfs works fine !

Cmd line :
sudo mount -t nfs 192.168.X.X:/Public /X/Public/

Hope this helps !

L.

[Leatherman]

I was just coming in to post the same thing, it worked for me, after some help from a friend. Thanks for the help...

[MiB07]

It worked! - i had to update it - don't know why - but now it works (Debian etch)

[AndyChuo]

It worked! - i had to update it - don't know why - but now it works (Debian etch)

I was just coming in to post the same thing, it worked for me, after some help from a friend. Thanks for the help...

Hi Guys, can you provide how you solved the problem?

or the complete command that works for you.

I wanna sticky it for other users having the same issues.

Thanks

[cute_l]

Hi,

to install the package under Ubuntu Gutsy :

Code: Select all

sudo aptitude install nfs-common

Or just search for nfs-common in the Synaptic package manager and install it.

L.

[MiB07]

Yes I did the same on a debian - the funny thing is - it was installed allready :-/ - now it works the way it should - SMB 4mbyte/s NFS 11 mbyte/s - with a 100 mbit- net

[tonskidutch]

Hi Guys, can you provide how you solved the problem?

or the complete command that works for you.

I wanna sticky it for other users having the same issues.

Thanks

I might add the related info i read in topic of nfs-server in kernel and installing nfsutil for better performance there i guess you'll find the basic issue with nfs-versions as well

could it be similar that (here OpenSuse) it mounts when you ad the option version3
with kde4.3 suse11.2 it can't mount with default which is version4 as nfs-client
when added the option version3 it mounts perfectly.

maybe that is the issue
ciao

[OnEmAnArMy]

now it works the way it should - SMB 4mbyte/s NFS 11 mbyte/s - with a 100 mbit- net

i have better performance with smb... let's say something like 7mbyte/s... but NFS is really SOOOO fast!