Hi all,
*Apologies for bad formatting. I am not sure why I can't get this post to format correctly!*
This little issue feels like it is costing me a good chunk of my sanity and a few years of my life.
I am simply trying to mount some NFS3/4 shares from another system onto my Cubox-i (ARMv7l, kernel 6.2.10-1-ARCH) and I just can't get it to work:
NFS v4
[code]
[root@cubox etc]# mount -v -t nfs micro.lan:/mnt/sg2 /mnt/sg2
mount.nfs: timeout set for Fri Oct 27 10:27:35 2023
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.6,clientaddr=192.168.1.2'
mount.nfs: mount(2): Protocol error
mount.nfs: Protocol error for micro.lan:/mnt/sg2 on /mnt/sg2
[/code]
NFS v3
[code]
[root@cubox etc]# mount -v -t nfs -o nfsvers=3 micro.lan:/mnt/sg2 /mnt/sg2
mount.nfs: timeout set for Fri Oct 27 10:29:25 2023
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.1.6'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.6 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.6 prog 100005 vers 3 prot UDP port 20048
mount.nfs: mount(2): Connection timed out
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.1.6'
mount.nfs: prog 100003, trying vers=3, prot=6[/code]
By contrast if I run the same commands on an x86_64 system (kernel 6.5.8-arch1-1) it works perfectly:
NFSv4
[code][root@archlinux ~]# mount -v -t nfs micro.lan:/mnt/sg2 /mnt/sg2
mount.nfs: timeout set for Thu Oct 26 23:31:31 2023
mount.nfs: trying text-based options 'vers=4.2,addr=192.168.1.6,clientaddr=192.168.7.186'
[root@archlinux ~]# mount | grep micro
micro.lan:/mnt/sg2 on /mnt/sg2 type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,)
[root@archlinux ~]#
[/code]
NFSv3
[code]
[root@archlinux ~]# mount -v -t nfs -o nfsvers=3 micro.lan:/mnt/sg2 /mnt/sg2
mount.nfs: timeout set for Thu Oct 26 23:32:00 2023
mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.1.6'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.6 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.6 prog 100005 vers 3 prot UDP port 20048
[root@archlinux ~]# mount | grep micro
micro.lan:/mnt/sg2 on /mnt/sg2 type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mou)
[root@archlinux ~]#
[/code]
The only other information I have found that somebody has published relates to enabling APPARMOR in a kernel parameter, but I do not have apparmor installed on my system at all. Here are the posts for reference:
make_clickable_callback(MAGIC_URL_LOCAL, '
', 'https://archlinuxarm.org/forum', 'viewtopic.php?f=15&t=16263', ' class="postlink-local"') posted by @arepusmake_clickable_callback(MAGIC_URL_FULL, '
', 'https://wiki.archlinux.org/title/Talk:NFS#NFS_Mounts_on_armv7h', '', ' class="postlink"')
If anybody can point me in the right direction for troubleshooting I would be very grateful. I have absolutely no issue mounting this share (or others) anywhere other than on this specific device.