Hello. Anybody have a suggested fix?
I did a fresh alarm install on a Chromebook and installed nfs using the same steps I have for many other alarm installs.
$this->bbcode_second_pass_code('', '
[root@alarm ~]# pacman -S nfs-utils
[root@alarm ~]# systemctl enable rpcbind.service
Created symlink /etc/systemd/system/sockets.target.wants/rpcbind.socket → /usr/lib/systemd/system/rpcbind.socket.
[root@alarm ~]# systemctl enable nfs-client.target
Created symlink /etc/systemd/system/multi-user.target.wants/nfs-client.target → /usr/lib/systemd/system/nfs-client.target.
Created symlink /etc/systemd/system/remote-fs.target.wants/nfs-client.target → /usr/lib/systemd/system/nfs-client.target.
[root@alarm ~]# systemctl enable remote-fs.target
')
I then restart and attempt to mount.
$this->bbcode_second_pass_code('', '
[krovetz@chrome bin]$ sudo mount gaia.ecs.csus.edu:/home/faculty/krovetz /home/krovetz/gaia
mount.nfs: No such device
')
I double-checked my work and with my IT people that the server was configured correctly. A search in dmesg for anything NFS related gives
$this->bbcode_second_pass_code('', '
[ 9.055643] systemd[1]: proc-fs-nfsd.mount: Mount process exited, code=exited status=32
[ 9.106994] systemd[1]: Failed to mount NFSD configuration filesystem.
[ 9.113497] systemd[1]: Dependency failed for GSSAPI Proxy Daemon.
[ 9.118706] systemd[1]: gssproxy.service: Job gssproxy.service/start failed with result 'dependency'.
[ 9.123495] systemd[1]: proc-fs-nfsd.mount: Unit entered failed state.
')
I have several other arch installs running off of the same switch that mount this NFS share just fine.