On 23/10/18 9:17 am, Ed Greshko wrote:
On 10/23/18 5:57 AM, Stephen Morris wrote:
On 23/10/18 8:06 am, Stephen Morris wrote:
Hi,
My Nas Devices are failing to mount at boot time because the
Networkmanager Wait
Online Service is failing at boot time. The following is the output from
systemctl that
the boot process recommends being run. Is there anything in that output that
would
indicate why the service is failing even though the wifi adapter is indicating
that it
is already active before the service fails? This issue happens every time I
boot.
The other thing I should have mentioned is I also have an ethernet cable from
the pc to
a powerline adapter as a failover for the wifi.
Have you tried testing with the ethernet cable disconnected at the computer end?
I haven't tried this yet, I've been using this setup for over 12 months
and the NetworkManager wait online failure has only just started
occurring in the last couple of weeks.
FWIW, I've had spotty success in using the various Networkmanager settings to
ensure my
NAS mounts
succeed at boot time. So, I've changed my fstab add the x-systemd.automount
option. One
of my entries looks
like....
ds6:/volume1/syntegra /syntegra nfs4 rw,soft,fg,x-systemd.automount
0 0
It may, or may not, mount at boot time. But as soon as I access the mount
point it will
mount and stay mounted.
I tried the x-systemd.automount parameter by adding it to the fstab
entry and then trying 'ls /mnt/nfs' which doesn't automount the
partition. Either the change requires a reboot to take effect (I've left
it present to see what happens after next boot, but the same thing also
doesn't work on the cifs mount point either) or it is an nfs4 specific
option, in which case it won't work for me as my nas doesn't support
nfs4 probably for the same reasons as it only supports cifs version 1.
Just for interest below is my fstab specifications for the partition.
The unfortunate thing with the cifs mount point is cifs doesn't support
user mounting.
192.168.0.12:/mnt/HD/HD_a2 /mnt/nfs nfs
users,noatime,nolock,bg,sec=sys,tcp,timeo=1800,_netdev,rw,x-systemd.automount
0 0
//192.168.0.12/Volume_1 /mnt/nas cifs
vers=1.0,username=********,password=********,cache=strict,_netdev,rw,x-systemd.requires=/mnt/nfs
0 0
regards,
Steve
bash-4.4$ systemctl status NetworkManager-wait-online.service
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service;
enabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2018-10-23 07:38:50 AEDT;
19min ago
Docs: man:nm-online(1)
Process: 1656 ExecStart=/usr/bin/nm-online -s -q --timeout=30 (code=exited,
status=1/FAILURE)
Main PID: 1656 (code=exited, status=1/FAILURE)
Oct 23 07:38:20 localhost.localdomain systemd[1]: Starting Network Manager Wait
Online...
Oct 23 07:38:50 localhost.localdomain systemd[1]:
NetworkManager-wait-online.service:
Main process exited, code=exited, status=1/FAILURE
Oct 23 07:38:50 localhost.localdomain systemd[1]:
NetworkManager-wait-online.service:
Failed with result 'exit-code'.
Oct 23 07:38:50 localhost.localdomain systemd[1]: Failed to start Network
Manager Wait
Online.
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
