Cubiebaord: NFS problem

[krovetz]

I have a new installation, with no significant configuration yet.

According to the arch NFS wiki, "Clients need nfs-utils to connect, but no special setup is required". I have nfs-utils installed, but get no joy trying to connect. I can connect to the target server using other machines, but both my alarm NSA320 and cubieboard fail as follows.
$this->bbcode_second_pass_code('', '
cubie> pacman -Q nfs-utils
nfs-utils 1.2.7-1
cubie> showmount -e 192.168.1.162
Export list for 192.168.1.162:
/Users/krovetz 192.168.0.0
cubie> mount 192.168.1.162:/Users/krovetz /home/krovetz/imac/
mount.nfs: No such device
cubie> dmesg | grep nfs
cubie> lsmod | grep nfs
cubie> modprobe nfs
cubie> lsmod | grep nfs
cubie>
')
Is this the right place to ask for help and/or report such issues?

[WarheadsSE]

So to confirm, you are trying to mount a remote NFS share to your cubie's fs?

[krovetz]

Yes. That's right.

My cubox running arch can do it, but my NSA320 and cubieboard running arch cannot.

I'm trying to mount my home directory from my Mac into my cubie. I've done this for years using various debian and alarm installs. It is only recently that new alarm installs have been giving me trouble.

[pepedog]

I just put a big effort into cubox config, maybe compare cubox config with kirkwood and see if you can spot anything amiss
https://github.com/archlinuxarm/PKGBUILDs

[krovetz]

I don't really know what I'm looking for, but I grabbed the sun4i and cubox configs and here are the NFS-related entries.


cubox
$this->bbcode_second_pass_code('', '
CONFIG_NFS_FS=y
CONFIG_NFS_V2=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_NFS_V4_1=y
CONFIG_PNFS_FILE_LAYOUT=y
CONFIG_PNFS_BLOCK=m
CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="y"
CONFIG_ROOT_NFS=y
CONFIG_NFS_USE_LEGACY_DNS=y
CONFIG_NFSD=m
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_FAULT_INJECTION=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
')

sun4i
$this->bbcode_second_pass_code('', '
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_V4_1 is not set
CONFIG_NFS_FSCACHE=y
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
# CONFIG_NFS_USE_NEW_IDMAPPER is not set
CONFIG_NFSD=m
CONFIG_NFSD_DEPRECATED=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=m
CONFIG_NFS_COMMON=y
')

[pepedog]

I made this for you to see if zyxel can work
http://myplugbox.com/adam/
If it works it could be added to cubieboard

[krovetz]

Thanks pepedog! I gave it a try.

$this->bbcode_second_pass_code('', '
server> ssh root@192.168.1.10
root@192.168.1.10's password:
Last login: Fri May 17 13:57:37 2013 from 192.168.1.162
nsa> cp /boot/uImage /boot/uImage.bak
nsa> tar xpf linux-headers-kirkwood-3.8.11-2-arm.pkg.tar.xz -C /
nsa> tar xpf linux-kirkwood-3.8.11-2-arm.pkg.tar.xz -C /
nsa> ls -l /boot
total 6256
-rw-r--r-- 1 root root 3522840 May 8 08:29 uImage
-rw-r--r-- 1 root root 2869580 May 17 13:59 uImage.bak
nsa> ls /usr/lib/modules
3.1.10-19-ARCH extramodules-3.1-ARCH
3.8.11-2-ARCH extramodules-3.8.11--kirkwood
nsa> reboot
Connection to 192.168.1.10 closed by remote host.
Connection to 192.168.1.10 closed.
server> ssh krovetz@192.168.1.10
krovetz@192.168.1.10's password:
Last login: Tue May 7 17:59:46 2013 from 192.168.1.162
nsa> sudo mount -v -s -o nfsvers=3 192.168.1.162:/Users/krovetz /home/krovetz/imac/
[sudo] password for krovetz:
mount.nfs: timeout set for Fri May 17 14:12:25 2013
mount.nfs: trying text-based options 'nfsvers=3,sloppy,addr=192.168.1.162'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.162 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.162 prog 100005 vers 3 prot UDP port 628
mount.nfs: mount(2): No such device
mount.nfs: No such device
')

I'm able to nfs mount this volume on alarm cubox, x86 Arch and several Debian machines, so I know the share is working.

[krovetz]

I ran pacman -Syu today on my cubieboard and NSA320, both of which couldn't nfs mount my Mac's volumes. Both included an update to the kernel and nfs-utils, and both can now mount the volume. Don't know which update fixed the problem, but thanks to whoever fixed it.

[skooman]

I'm running an up to date arch linux arm install on the cubieboard and (still) unable to mount a nfs share:

[root@cubie ~]# pacman -Q linux-sun4i
linux-sun4i 3.0.57-5
[root@cubie ~]# pacman -Q nfs-utils
nfs-utils 1.2.8-9
[root@cubie ~]# mount -a
mount.nfs4: No such device

mounting with "nfs -o vers=3" gives: mount.nfs: No such device. I'm able to mount this share on other (arm) hosts in the same network, however.