It's a mature install, not sure exactly how old, but this issue has existed since it was first installed.
What's happening is that I am experiencing about a 2 minute delay when booting the machine. I'm watching standard out and seeing that network drives are showing mounted, but they aren't. Then I see a job start running to mount drives:
That image is cutting off the right-hand portion for some reason. The timeout on that job is 1:56 - almost 2 minutes. You can see that the job is 53 seconds in at the point that image was captured. The job simply times out and the drives have to be mounted manually (sudo mount -a) after boot completes.
My fstab has all of these drives configured like this:
- Code: Select all
adamsmdk:/backup-1 /mnt/adamsmdk/backup-1 nfs nosuid,rsize=8192,wsize=8192,_netdev 0 0
<server>:<share> <mount-point> nfs nosuid,rsize=8192,wsize=8192,_netdev 0 0
This shows up like this under the "mount" command:
- Code: Select all
adamsmdk:/backup-1 on /mnt/adamsmdk/backup-1 type nfs4 (rw,nosuid,relatime,vers=4.2,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.106,local_lock=none,addr=192.168.1.100,_netdev)
The shares are all on nfs servers and conform to this configuration in /etc/exports:
- Code: Select all
# generated by drakhosts.pl
/backup-1 *(no_all_squash,async,secure,no_subtree_check,rw)
The "_netdev" option doesn't really seem to have any effect on the process, but it doesn't hurt anything either.
Systemd-analyze blame says
- Code: Select all
# systemd-analyze blame
9.881s network-up.service
5.057s webmin.service
4.163s mandriva-everytime.service
4.035s systemd-udev-settle.service
3.514s shorewall6.service
2.962s mysqld.service
2.267s dev-sda6.device
2.023s dev-sda1.device
1.822s systemd-journal-flush.service
1.547s systemd-fsck@dev-disk-by\x2duuid-dcac9b29\x2dee71\x2d457f\x2d9750\x2dec513ad35610.service
1.430s systemd-logind.service
1.420s cpupower.service
1.419s gpm.service
1.417s rpcbind.service
1.405s rsyslog.service
1.391s gssproxy.service
1.391s partmon.service
1.390s iptables.service
1.389s ipmievd.service
1.389s mga-bg-res.service
1.389s acpid.service
1.301s systemd-fsck@dev-disk-by\x2duuid-bf27abc3\x2d578f\x2d457c\x2da26f\x2d41b36a8299b1.service
1.296s systemd-fsck@dev-disk-by\x2duuid-8e95887b\x2d58ac\x2d4d78\x2da89b\x2d2dcba7f41916.service
1.231s systemd-fsck@dev-disk-by\x2duuid-6c736e4e\x2d9257\x2d44b0\x2da1a1\x2dfb133086d3df.service
1.150s avahi-daemon.service
1.131s bluetooth.service
1.075s systemd-fsck@dev-disk-by\x2duuid-def9da8b\x2d5dff\x2d4ed3\x2dbeca\x2d6e6e64875dc3.service
1.073s systemd-fsck@dev-disk-by\x2duuid-7a73b4c4\x2d7dc6\x2d42a7\x2db249\x2ddc2e14df1e66.service
995ms httpd.service
983ms cups.service
918ms media-windows.mount
911ms systemd-fsck@dev-disk-by\x2duuid-5cc5a587\x2df5ed\x2d4a9a\x2d9d78\x2df5356bd5a6fe.service
824ms resolvconf.service
812ms fedora-storage-init.service
791ms network.service
720ms mnt-backup.mount
716ms systemd-fsck@dev-disk-by\x2duuid-7aa6f935\x2d8a3e\x2d4e87\x2d8357\x2db5c87b146b3e.service
641ms sensord.service
631ms home.mount
604ms lm_sensors.service
564ms sshd.service
563ms fedora-loadmodules.service
547ms systemd-fsck@dev-disk-by\x2duuid-f601ac26\x2da9df\x2d4627\x2dbb7a\x2d82ecee9c6bba.service
472ms usr-local.mount
428ms systemd-backlight@backlight:acpi_video0.service
428ms systemd-random-seed.service
416ms systemd-tmpfiles-setup.service
408ms systemd-vconsole-setup.service
404ms dev-disk-by\x2duuid-672d47e9\x2d0d1e\x2d4411\x2da897\x2db61b8adb51df.swap
9.881s network-up.service
5.057s webmin.service
4.163s mandriva-everytime.service
4.035s systemd-udev-settle.service
3.514s shorewall6.service
2.962s mysqld.service
2.267s dev-sda6.device
2.023s dev-sda1.device
1.822s systemd-journal-flush.service
1.547s systemd-fsck@dev-disk-by\x2duuid-dcac9b29\x2dee71\x2d457f\x2d9750\x2dec513ad35610.service
1.430s systemd-logind.service
1.420s cpupower.service
1.419s gpm.service
1.417s rpcbind.service
1.405s rsyslog.service
1.391s gssproxy.service
1.391s partmon.service
1.390s iptables.service
1.389s ipmievd.service
1.389s mga-bg-res.service
1.389s acpid.service
1.301s systemd-fsck@dev-disk-by\x2duuid-bf27abc3\x2d578f\x2d457c\x2da26f\x2d41b36a8299b1.service
1.296s systemd-fsck@dev-disk-by\x2duuid-8e95887b\x2d58ac\x2d4d78\x2da89b\x2d2dcba7f41916.service
1.231s systemd-fsck@dev-disk-by\x2duuid-6c736e4e\x2d9257\x2d44b0\x2da1a1\x2dfb133086d3df.service
1.150s avahi-daemon.service
1.131s bluetooth.service
1.075s systemd-fsck@dev-disk-by\x2duuid-def9da8b\x2d5dff\x2d4ed3\x2dbeca\x2d6e6e64875dc3.service
1.073s systemd-fsck@dev-disk-by\x2duuid-7a73b4c4\x2d7dc6\x2d42a7\x2db249\x2ddc2e14df1e66.service
995ms httpd.service
983ms cups.service
918ms media-windows.mount
911ms systemd-fsck@dev-disk-by\x2duuid-5cc5a587\x2df5ed\x2d4a9a\x2d9d78\x2df5356bd5a6fe.service
824ms resolvconf.service
812ms fedora-storage-init.service
791ms network.service
720ms mnt-backup.mount
716ms systemd-fsck@dev-disk-by\x2duuid-7aa6f935\x2d8a3e\x2d4e87\x2d8357\x2db5c87b146b3e.service
641ms sensord.service
631ms home.mount
604ms lm_sensors.service
564ms sshd.service
563ms fedora-loadmodules.service
547ms systemd-fsck@dev-disk-by\x2duuid-f601ac26\x2da9df\x2d4627\x2dbb7a\x2d82ecee9c6bba.service
472ms usr-local.mount
428ms systemd-backlight@backlight:acpi_video0.service
428ms systemd-random-seed.service
416ms systemd-tmpfiles-setup.service
408ms systemd-vconsole-setup.service
404ms dev-disk-by\x2duuid-672d47e9\x2d0d1e\x2d4411\x2da897\x2db61b8adb51df.swap
9.881s network-up.service
5.057s webmin.service
4.163s mandriva-everytime.service
4.035s systemd-udev-settle.service
3.514s shorewall6.service
2.962s mysqld.service
2.267s dev-sda6.device
2.023s dev-sda1.device
1.822s systemd-journal-flush.service
1.547s systemd-fsck@dev-disk-by\x2duuid-dcac9b29\x2dee71\x2d457f\x2d9750\x2dec513ad35610.service
1.430s systemd-logind.service
1.420s cpupower.service
1.419s gpm.service
1.417s rpcbind.service
1.405s rsyslog.service
1.391s gssproxy.service
1.391s partmon.service
1.390s iptables.service
1.389s ipmievd.service
1.389s mga-bg-res.service
1.389s acpid.service
1.301s systemd-fsck@dev-disk-by\x2duuid-bf27abc3\x2d578f\x2d457c\x2da26f\x2d41b36a8299b1.service
1.296s systemd-fsck@dev-disk-by\x2duuid-8e95887b\x2d58ac\x2d4d78\x2da89b\x2d2dcba7f41916.service
1.231s systemd-fsck@dev-disk-by\x2duuid-6c736e4e\x2d9257\x2d44b0\x2da1a1\x2dfb133086d3df.service
1.150s avahi-daemon.service
1.131s bluetooth.service
1.075s systemd-fsck@dev-disk-by\x2duuid-def9da8b\x2d5dff\x2d4ed3\x2dbeca\x2d6e6e64875dc3.service
1.073s systemd-fsck@dev-disk-by\x2duuid-7a73b4c4\x2d7dc6\x2d42a7\x2db249\x2ddc2e14df1e66.service
995ms httpd.service
983ms cups.service
918ms media-windows.mount
911ms systemd-fsck@dev-disk-by\x2duuid-5cc5a587\x2df5ed\x2d4a9a\x2d9d78\x2df5356bd5a6fe.service
824ms resolvconf.service
812ms fedora-storage-init.service
791ms network.service
720ms mnt-backup.mount
716ms systemd-fsck@dev-disk-by\x2duuid-7aa6f935\x2d8a3e\x2d4e87\x2d8357\x2db5c87b146b3e.service
641ms sensord.service
631ms home.mount
604ms lm_sensors.service
564ms sshd.service
563ms fedora-loadmodules.service
547ms systemd-fsck@dev-disk-by\x2duuid-f601ac26\x2da9df\x2d4627\x2dbb7a\x2d82ecee9c6bba.service
472ms usr-local.mount
428ms systemd-backlight@backlight:acpi_video0.service
428ms systemd-random-seed.service
416ms systemd-tmpfiles-setup.service
408ms systemd-vconsole-setup.service
404ms dev-disk-by\x2duuid-672d47e9\x2d0d1e\x2d4411\x2da897\x2db61b8adb51df.swap
393ms upower.service
390ms fedora-readonly.service
375ms systemd-fsck-root.service
333ms mandriva-save-dmesg.service
Once the shares are mounted by root with "mount -a" everything works just fine, but how do I resolve the trouble the system is having on boot? I'm starting to think I need to just go with automount, which works well on my laptops, but this is a desktop that should work better than it does.
Any ideas?