You are not logged in.
Hi,
I have two PC's running ArchLinux. One is the media center, running a video recorder software and a NFS server. The other one is more like an office PC.
Since today's update, I get the following message when I try to mount the NFS share on my office PC:
mount.nfs: requested NFS version or transport protocol is not supported
Both PC's are up to date, so it should not be a version mismatch.
I think it is a server issue, because I started the update on the server while watching a video over NFS and durig the update process, the player suddenly showed errors. Indeed, NFS was inaccessible from this moment. The client was already updated and rebooted before I started the update on the server.
Unfortunately, a reboot (both client and server) did not help. I have no journal entries on server side, and on client side only the message that NFS mount failed.
Among others, the update contained a new kernel and rpcbind. AIFAIK, the latter one is required for NFS. But I have no idea if I can do anything to fix it, not even how to troubleshoot and get more detailed info about the problem. Yes, I have read the "NFS trouubleshooting" wiki article.
Any ideas ?
Thanks and Regards,
Markus
Last edited by Markus.N2 (2014-06-30 21:35:53)
Offline
Perhaps try mounting nfs4 and not nfs?
Offline
Don't know that specific error, but did you see: https://bbs.archlinux.org/viewtopic.php?id=183444
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
Ah, this means that now I have to explicitly specify the nfs protocol ?
OK, I tried it, and there was a change. The "not supported" message is gone, but now I get a timeout. Networking in general works, I can connect the server via ping, ssh and VNC. And "exportfs" on the server says my share is exported.
Offline
Try "mount.nfs[4] -v source dest". Show us your nfs line in fstab. What nfs services are running?
Offline
OK, the verbose mount showed "connection refused", so it looks like the server is not running properly.
I checked the thread mentioned by graysky (BTW: I am a Disturbed fan, too) and when I read WonderWoofy's post about dead symlinks, I tried
systemctl stop nfs-server.service
systemctl disable nfs-server.service
systemctl enable nfs-server.service
systemctl start nfs-server.service
and that helped.
Thanks a lot to both of you. Marking thread as SOLVED.
Offline
Thanks for posting this, was driving me nuts.
Linux user #338966
Offline