NFS - Can no longer mount nfs to remote NAS.

English Network/Internet
#1

I have been unable to get nfs connection with my NAS recently although it used to work OK but both NAS and Tumbleweed have no doubt been updated many times and at some point this must have stopped working but only just noticed.
I set this up using Yast and found that the NAS only used NFS v3 so have changed my nfs mount to use Force NFSv3 and changed the firewall to allow nfs3 but still no luck.
I then frightened myself by studying the boot log to try and find the problem. Here is what I believe is the relevant part of the log:-

Oct 05 10:56:05 ibmserv2 systemd[1]: Reloading.
Oct 05 10:56:06 ibmserv2 systemd[1]: /usr/lib/systemd/system/plymouth-start.service:14: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, suc>
Oct 05 10:56:06 ibmserv2 systemd[1]: /usr/lib/systemd/system/gpm.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Oct 05 10:56:06 ibmserv2 systemd[1]: /usr/lib/systemd/system/smartd.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Oct 05 10:56:06 ibmserv2 systemd[1]: /usr/lib/systemd/system/mcelog.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Oct 05 10:56:06 ibmserv2 systemd[1]: chrony-wait.service: Main process exited, code=exited, status=1/FAILURE
Oct 05 10:56:06 ibmserv2 systemd[1]: chrony-wait.service: Failed with result 'exit-code'.
Oct 05 10:56:06 ibmserv2 systemd[1]: Failed to start Wait for chrony to synchronize system clock.
Oct 05 10:56:06 ibmserv2 mount[1303]: mount.nfs: Network is unreachable
Oct 05 10:56:06 ibmserv2 systemd[1]: home-alastair-Nas_Multimedia_NFS.mount: Mount process exited, code=exited, status=32/n/a
Oct 05 10:56:06 ibmserv2 systemd[1]: home-alastair-Nas_Multimedia_NFS.mount: Failed with result 'exit-code'.
Oct 05 10:56:06 ibmserv2 systemd[1]: Failed to mount /home/alastair/Nas_Multimedia_NFS.
Oct 05 10:56:06 ibmserv2 systemd[1]: Dependency failed for Remote File Systems.
Oct 05 10:56:06 ibmserv2 systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
Oct 05 10:56:06 ibmserv2 systemd[1]: Reached target System Time Synchronized.

Even this tiny extract from the log raises so many questions but concentrating on the NFS, I could understand a permissions problem but not dependency.
Where should I look next?

Budge.

#2 
Oct 05 10:56:06 ibmserv2 mount[1303]: mount.nfs: Network is unreachable

Did you check if the network is up at that moment?
If your system and the NAS are in the same subnet?

What about at least showing us the entry from /etc/fstab?

#3

All as it should be here, all NAS devices and this workstation on the same subnet and NAS serving data as required.
Here is the info on fstab:-

alastair@ibmserv2:/etc> cat fstab
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /                       btrfs  defaults                      0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /var                    btrfs  subvol=/@/var                 0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /usr/local              btrfs  subvol=/@/usr/local           0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /tmp                    btrfs  subvol=/@/tmp                 0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /srv                    btrfs  subvol=/@/srv                 0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /root                   btrfs  subvol=/@/root                0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /opt                    btrfs  subvol=/@/opt                 0  0
UUID=4272b75a-ea72-4068-8826-e2dfc5611fd5  /multimedia             xfs    defaults                      0  0
UUID=4ceac2e7-6bdc-40d2-9dff-da7a2099bf45  /home                   xfs    defaults                      0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /boot/grub2/i386-pc     btrfs  subvol=/@/boot/grub2/i386-pc  0  0
UUID=B738-D576                             /boot/efi               vfat   defaults                      0  0
UUID=46f191b6-7472-49c0-bd98-75824020d947  swap                    swap   defaults                      0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /.snapshots             btrfs  subvol=/@/.snapshots          0  0
192.168.xxx.xxx:/Multimedia                /home/alastair/Nas_Multimedia_NFS  nfs    nfsvers=3                     0  0
alastair@ibmserv2:/etc>

Hope this helps.

#4

So it worked earlier, but you failed to notice what happened that broke it :(. I am afraid we then have to do our bug search as if it never worked.

My idea is to still go on based on the “Network unreachable” message. You did not answer my first question btw.

Are you using Wicked or NM?
And when using NM, is this a configured as “system” connection?

#5

Hi
If wicked, then could be the update to wicked 0.6.64, it broke my qemu tap0 so rolled back both wicked and wicked-service to 0.6.63…

Ref: https://bugzilla.suse.com/show_bug.cgi?id=1177273

#6

Hi Henk,
Sorry if my reply was a bit oblique but did reply. For clarity, the NAS is up and running and is on the same subnet as this workstation on which I am typing.

I am using NM but do not know what you mean by “system.” I can confirm that as far as I know it is a system connection working through the first NIC on my workstation on the same physical subnet.

I am confused by the Network unreachable because when I go through the Yast process for the NFS client it allows me to browse the directories on the NAS and select the required directory for creating the NFS. I believe this confirms that the NAS is not only running but available over the network. Of course I could be wrong but the other clues in the log may be more instructive.

#7

Hi Malcolm,
Many thanks for the thought which might have been the problem but I have already switched back to NM to facilitate setting up the VPN. That is what prompted all my earlier posts which started out with VPN and moved rapidly to a network problem or rather; two connected problems. These have all been sorted and NM is working but I could try switching back to Wicked just in case. I simply do not know when the NFS failed.

#8

OK, but the network will be up when you log in and thus when you use YaSt it will certainly be up.
We are talking about the network being up on boot when the mount takes place.

I forget to ask, but can you mount it now?

mount -a
#9

Hi Henk,
I am away from my workstation so cannot run your command until morning but all NAS boxes run all the time and no failures have been reported so I must assume that the NAS was running when throughout and during boots.

I tried switching to Wicked just to see if that made any difference but no, so have switched back to NM.
Will pick up tomorrow.

#10

You could share the /etc/fstab entry you have for the share. The issue may well be that the network is not up before the mount is attempted.

The following wiki page may be of value…
https://wiki.archlinux.org/index.php/NFS#Mount_using_/etc/fstab_with_systemd

#11

See post #3 the last line of the code.

#12

Sorry missed that, but my other comments should be checked.

#13

I think Henk’s instruction was right. Running

mount -a

has given me back the NFS so the issue is the timing of when the network is up.
On a previous thread I spent some time trying to sort out the

chrony-wait.service

. This had been disabled and then put at 2 seconds. This was because of the NM problem which Deano’s suggestion fixed it. I am not sure what this service was left at and why and when it is called as I am out of my depth again. It would be sensible however to wait until the network connections were running before attempting to mount the NFS and suspect this was meant to happen.
Will increase the service time to 60 seconds and reboot.

#14

Consider using the x-systemd.automount option (mounting only takes place on demand as opposed to at boot) as explained in the archwiki page I linked to already.

#15

Well the boot still dos not mount the NFS. Here are some of the warnings from the boot log:-

Oct 06 09:45:24 ibmserv2 systemd[1]: /usr/lib/systemd/system/plymouth-start.service:14: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, suc>
Oct 06 09:45:24 ibmserv2 systemd[1]: /usr/lib/systemd/system/gpm.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Oct 06 09:45:24 ibmserv2 systemd[1]: /usr/lib/systemd/system/smartd.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Oct 06 09:45:24 ibmserv2 systemd[1]: /usr/lib/systemd/system/mcelog.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
Oct 06 09:45:25 ibmserv2 mount[1294]: mount.nfs: Network is unreachable
Oct 06 09:45:25 ibmserv2 systemd[1]: home-alastair-Nas_Multimedia_NFS.mount: Mount process exited, code=exited, status=32/n/a
Oct 06 09:45:25 ibmserv2 systemd[1]: home-alastair-Nas_Multimedia_NFS.mount: Failed with result 'exit-code'.
Oct 06 09:45:25 ibmserv2 systemd[1]: Failed to mount /home/alastair/Nas_Multimedia_NFS.
Oct 06 09:45:25 ibmserv2 systemd[1]: Dependency failed for Remote File Systems.
Oct 06 09:45:25 ibmserv2 systemd[1]: remote-fs.target: Job remote-fs.target/start failed with result 'dependency'.
Oct 06 09:45:25 ibmserv2 systemd[1]: Starting Permit User Sessions...
Oct 06 09:45:25 ibmserv2 systemd[1]: Finished Permit User Sessions.
Oct 06 09:45:25 ibmserv2 systemd[1]: Starting Hold until boot process finishes up...
Oct 06 09:45:27 ibmserv2 nscd[1141]: 1141 checking for monitored file `/etc/services': No such file or directory
Oct 06 09:45:28 ibmserv2 systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Oct 06 09:45:42 ibmserv2 nscd[1141]: 1141 checking for monitored file `/etc/services': No such file or directory
Oct 06 09:45:47 ibmserv2 systemd[1]: systemd-hostnamed.service: Succeeded.
Oct 06 09:45:57 ibmserv2 nscd[1141]: 1141 checking for monitored file `/etc/services': No such file or directory
Oct 06 09:46:16 ibmserv2 systemd[1]: chrony-wait.service: Main process exited, code=exited, status=1/FAILURE
Oct 06 09:46:16 ibmserv2 systemd[1]: chrony-wait.service: Failed with result 'exit-code'.
Oct 06 09:46:16 ibmserv2 systemd[1]: Failed to start Wait for chrony to synchronize system clock.
Oct 06 09:46:16 ibmserv2 systemd[1]: Reached target System Time Synchronized.
Oct 06 09:46:16 ibmserv2 systemd[1]: Started Backup of RPM database.

Now definitely out of my depth. It could be that my messing with the chrony-wait.service has messed things up but running

sudo mount -a

fixes it so there is a clue here.

#16

The ‘mount -a’ command just causes all that is listed in /etc/fstab to be mounted (if not already). It fails at boot for the reasons already explained. Refer to my previous post for autmounting instead.

#17

Hi Deano,

Very many thanks and sorry I didn’t immediately go to the automount.x-systemd.mount as I was trying to understand what was happening, and still don’t know why the system didn’t work before once I had sorted out the NM “bug” on my system.

A couple of question on your wiki quote please.
My fstab line is as follows:-

192.168.xxx.xxx:/Multimedia                /home/alastair/Nas_Multimedia_NFS  nfs    nfsvers=3                     0  0

The wiki suggests:-

servername:/home   */mountpoint/on/client*  nfs  _netdev,noauto,x-systemd.automount,x-systemd.mount-timeout=10,timeo=14,x-systemd.idle-timeout=1min 0 0

So this is what I propose:-

192.168.xxx.xxx:/Multimedia                /home/alastair/Nas_Multimedia_NFS  nfs    nfsvers=3    _netdev,noauto,x-systemd.automount,x-systemd.mount-timeout=10,timeo=14,x-systemd.idle-timeout=1min 0 0

Is this right?
What is the underscore as in _netdev?
Are the commas correct or should there be spaces?
I had some trouble editing as the last zero changed to red and was underscored. Might be a Kate syntax correction but wish to check.

Budge

#18

I have one in use with the followig options:

noauto,nofail,x-systemd.automount,x-systemd.mount-timeout=10,_netdev,x-systemd.idle-timeout=5min

In another thread we found out that the _netdev (indeed a strange name) is not needed because the system already takes into account that it is network dependent. But it does no harm either.

#19

Well here is my edited /etc/fstab:-

alastair@ibmserv2:~> cat /etc/fstab
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /                       btrfs  defaults                      0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /var                    btrfs  subvol=/@/var                 0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /usr/local              btrfs  subvol=/@/usr/local           0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /tmp                    btrfs  subvol=/@/tmp                 0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /srv                    btrfs  subvol=/@/srv                 0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /root                   btrfs  subvol=/@/root                0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /opt                    btrfs  subvol=/@/opt                 0  0
UUID=4272b75a-ea72-4068-8826-e2dfc5611fd5  /multimedia             xfs    defaults                      0  0
UUID=4ceac2e7-6bdc-40d2-9dff-da7a2099bf45  /home                   xfs    defaults                      0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /boot/grub2/i386-pc     btrfs  subvol=/@/boot/grub2/i386-pc  0  0
UUID=B738-D576                             /boot/efi               vfat   defaults                      0  0
UUID=46f191b6-7472-49c0-bd98-75824020d947  swap                    swap   defaults                      0  0
UUID=18ac0db8-9da6-48f7-8bf0-9eab0def1de1  /.snapshots             btrfs  subvol=/@/.snapshots          0  0
192.168.169.130:/Multimedia                /home/alastair/Nas_Multimedia_NFS  nfs  nfsvers=3 _netdev,noauto,x-systemd.automount,x-systemd.mount-timeout=10,timeo=14,x-systemd.idle-timeout=1min   0  0
alastair@ibmserv2:~>

Sad to report that after re-booting my NFS was still not mounted as I am getting a parse error on line 15 which is the line I edited. Have I screwed up my syntax?

#20

That is clear.

You have white space between the nfsvers=3 and the other options.

All options should be in one field (the 4th), white space separated from the others and options should be separated between themselves using the ,