You are not logged in.
Hello.
Used to work since recently, I must be missing something obvious. Client Arch 64b, up-to-date.
I have a little NAS server (arm/debian/BusyBox) which I usually connect to using 'nasup' which aliases in my .bashrc into
'alias nasup='sudo mount 192.168.4.249:/mnt/md1/public /mnt/naspas'
And since this morning, I fall into that 'mount.nfs: Protocol not supported'
I issued:
[jph@1215s ~]$ lsmod|grep nfs
nfsd 238173 11
auth_rpcgss 31196 1 nfsd
nfs_acl 2327 1 nfsd
nfs 127261 0
lockd 62843 2 nfs,nfsd
sunrpc 187776 21 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
fscache 44574 1 nfs
I've tried different versions:
[jph@1215s ~]$ sudo mount -t nfs 192.168.4.249:/mnt/md1/public /mnt/naspas
mount.nfs: Protocol not supported
[jph@1215s ~]$ sudo mount -t nfs4 192.168.4.249:/mnt/md1/public /mnt/naspas
mount.nfs4: Protocol not supported
[jph@1215s ~]$ sudo mount -t nfs 192.168.4.249:/mnt/md1/public /mnt/naspas -o vers=3
mount.nfs: Protocol not supported
less /etc/nsswitch.conf does looks for files, not something exotic:
# Begin /etc/nsswitch.conf
passwd: files
group: files
shadow: filespublickey: files
hosts: files dns myhostname
networks: filesprotocols: files
services: files
ethers: files
rpc: filesnetgroup: files
# End /etc/nsswitch.conf
And the damn machine is right there where I expect it:
[root@1215s jph]# showmount -e 192.168.4.249
Export list for 192.168.4.249:
/mnt/md1/public (everyone)
Any idea ?
Don't be afraid to make me feel stupid: I need access to this server.
Last edited by zenerve (2013-04-27 17:46:19)
Offline
sudo mount.nfs ... ?What version of NFS is the server running?
Offline
for info (first time I see this)
[root@1215s jph]# ssh root@192.168.4.249
no such identity: /root/.ssh/id_rsa: No such file or directory
no such identity: /root/.ssh/id_dsa: No such file or directory
no such identity: /root/.ssh/id_ecdsa: No such file or directory
root@192.168.4.249's password:BusyBox v1.00-rc3 (2009.02.19-03:01+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.NASPAS>
NASPAS> lsmod | grep nfs
NASPAS>
How do I know which version of nfs is the server running? BusyBox is rather limited.
Last edited by zenerve (2013-04-27 17:47:54)
Offline
Same problem:
sudo mount.nfs -v mass:/c/bak /mass
mount.nfs: timeout set for Sat Apr 27 11:59:45 2013
mount.nfs: trying text-based options 'vers=4,addr=192.168.0.80,clientaddr=192.168.0.3'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.0.80'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.0.80 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.0.80 prog 100005 vers 3 prot UDP port 59857
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
No problem mounting from same server on OSX machine:
> sudo mount -t nfs -v -overs=3 mass:/c/bak ~/tmp/mass
mass:/c/bak on /Users/<user>/tmp/mass (nfs)
Offline