[Solved] Slow boot/shutdown on a new installation of 18.1

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
MyNameIsUndefined
Level 1
Level 1
Posts: 2
Joined: Wed Jun 28, 2017 12:47 pm

[Solved] Slow boot/shutdown on a new installation of 18.1

Post by MyNameIsUndefined »

First of all, please forgive me if I did anything wrong writing this. First time posting

My problem is quite simple : the system takes 30+ seconds to boot or shutdown. This isn't a new issue and I've tried to reinstall Mint today, without success.
Running :

Code: Select all

systemd-analyze blame
systemd-analyze critical-chain
I get :

Code: Select all

940ms lvm2-monitor.service
           252ms dev-sda5.device
           130ms ModemManager.service
           117ms networking.service
           113ms accounts-daemon.service
           108ms systemd-modules-load.service
           105ms systemd-logind.service
            88ms avahi-daemon.service
            88ms NetworkManager.service
            87ms thermald.service
            80ms grub-common.service
            72ms console-setup.service
            71ms upower.service
            65ms loadcpufreq.service
            59ms speech-dispatcher.service
            58ms irqbalance.service
            58ms systemd-rfkill.service
            55ms virtualbox-guest-utils.service
            50ms ondemand.service
            43ms hddtemp.service
            38ms systemd-udev-trigger.service
            35ms keyboard-setup.service
            29ms systemd-journald.service
            28ms console-kit-log-system-start.service
            27ms iio-sensor-proxy.service
            27ms lm-sensors.service
            26ms rsyslog.service
            24ms pppd-dns.service
            23ms cpufrequtils.service
            23ms plymouth-quit.service
            23ms plymouth-quit-wait.service
            22ms udisks2.service
            18ms systemd-hostnamed.service
            17ms alsa-restore.service
            16ms systemd-udevd.service
            15ms user@1000.service
            15ms ntp.service
            12ms systemd-fsck@dev-disk-by\x2duuid-d93b27fc\x2db694\x2d4355\x2d8b
            12ms systemd-update-utmp.service
            11ms plymouth-start.service
            11ms plymouth-read-write.service
            10ms sys-kernel-debug.mount
            10ms polkitd.service
            10ms systemd-user-sessions.service
             9ms binfmt-support.service
             9ms dev-hugepages.mount
             7ms dns-clean.service
             7ms dev-disk-by\x2duuid-c486ec2c\x2d7840\x2d4af4\x2db05f\x2d3bd0a3b
             7ms ufw.service
             7ms home.mount
             7ms console-kit-daemon.service
             6ms kmod-static-nodes.service
             6ms wpa_supplicant.service
             6ms systemd-journal-flush.service
             6ms colord.service
             6ms systemd-tmpfiles-setup-dev.service
             6ms systemd-tmpfiles-setup.service
             5ms systemd-update-utmp-runlevel.service
             5ms dev-mqueue.mount
             4ms proc-sys-fs-binfmt_misc.mount
             3ms systemd-sysctl.service
             3ms resolvconf.service
             3ms systemd-remount-fs.service
             2ms systemd-random-seed.service
             2ms ureadahead-stop.service
             2ms rtkit-daemon.service
             2ms setvtrgb.service
             2ms sys-fs-fuse-connections.mount
             1ms openvpn.service
             1ms rc-local.service
             1ms systemd-backlight@backlight:acpi_video0.service
             1ms nvidia-persistenced.service
and

Code: Select all

graphical.target @35.109s
└─multi-user.target @35.109s
  └─getty.target @35.108s
    └─getty@tty1.service @35.108s
      └─rc-local.service @35.078s +1ms
        └─network.target @35.078s
          └─networking.service @34.957s +117ms
            └─resolvconf.service @34.917s +3ms
              └─system.slice @74ms
                └─-.slice @66ms
As you can see, it's resolvconf.service which is taking such a long time. So I understand where the problem is coming from, but I don't know how to solve it. Which is why I am here.
If it can help, here's the system configuration :
https://gist.github.com/anonymous/94378 ... 519cbc9f84
(hardware shouldn't be the problem imo)

I apologize if someone already posted a solution to this that I've been unable to find.
Thank you for reading

Edit :
Here's boot.log :

Code: Select all

Scanning for Btrfs filesystems
/dev/sda5: clean, 265564/1954064 files, 1907516/7812352 blocks
[FAILED] Failed to start Raise network interfaces.
See 'systemctl status networking.service' for details.
[  OK  ] Started Modem Manager.
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[  OK  ] Started LSB: set CPUFreq kernel parameters.
         Stopping NVIDIA Persistence Daemon...
         Starting Hostname Service...
[  OK  ] Reached target Network.
         Starting /etc/rc.local Compatibility...
         Starting OpenVPN service...
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started OpenVPN service.
[  OK  ] Stopped NVIDIA Persistence Daemon.
         Starting Terminate Plymouth Boot Screen...
         Starting Hold until boot process finishes up...
and

Code: Select all

systemctl status networking.service
gives me :

Code: Select all

networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/generator/networking.service.d
           └─50-insserv.conf-$network.conf
   Active: failed (Result: exit-code) since Thu 2017-06-29 13:18:25 CEST; 13min ago
     Docs: man:interfaces(5)
  Process: 877 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
  Process: 761 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --lis
 Main PID: 877 (code=exited, status=1/FAILURE)

Jun 29 13:17:51 PC-linux systemd[1]: Starting Raise network interfaces...
Jun 29 13:18:25 PC-linux ifup[877]: run-parts: /etc/network/if-up.d/upstart exited with return code 1
Jun 29 13:18:25 PC-linux ifup[877]: /sbin/ifup: post-up script failed.
Jun 29 13:18:25 PC-linux systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Jun 29 13:18:25 PC-linux systemd[1]: Failed to start Raise network interfaces.
Jun 29 13:18:25 PC-linux systemd[1]: networking.service: Unit entered failed state.
Jun 29 13:18:25 PC-linux systemd[1]: networking.service: Failed with result 'exit-code'.
However. interfaces seem to be configured correctly :

Code: Select all

# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
Any help would be appreciated
Last edited by MyNameIsUndefined on Sun Jul 02, 2017 11:53 am, edited 1 time in total.

User avatar
kukamuumuka
Level 16
Level 16
Posts: 6560
Joined: Tue Sep 03, 2013 4:51 am
Location: Finland
Contact:

Re: Slow boot/shutdown on a new installation of 18.1

Post by kukamuumuka »

A dirty fix is to comment out sleeps in the /etc/init/failsafe.conf

Code: Select all

$PLYMOUTH message --text="Waiting for network configuration..." || :
###	sleep 40

MyNameIsUndefined
Level 1
Level 1
Posts: 2
Joined: Wed Jun 28, 2017 12:47 pm

Re: Slow boot/shutdown on a new installation of 18.1

Post by MyNameIsUndefined »

Thank you for your reply :D

I'll do that for now but I would prefer a clean and definitive solution. Anyway, it's better than nothing.
I can't actually test it now but I'll be able to in a few hours, so I'll keep this thread updated.
I will also wait a few more days before marking this as solved, just in case someone comes up with a better fix.

User avatar
Spearmint2
Level 16
Level 16
Posts: 6880
Joined: Sat May 04, 2013 1:41 pm
Location: Maryland, USA

Re: [Solved] Slow boot/shutdown on a new installation of 18.1

Post by Spearmint2 »

Good help. I've been sitting there for 2 minutes before boot continues. thanks.
All things go better with Mint. Mint julep, mint jelly, mint gum, candy mints, pillow mints, peppermint, chocolate mints, spearmint,....

Post Reply

Return to “Installation & Boot”