Help! Extremely slow boot times

Thanks for the info!

It’s kinda weird because I was able to edit the “DefaultTimeoutStartSec=
DefaultTimeoutStopSec=” values but the “TimeoutSec=” value was non existent .Very peculiar… must be the important one because the workaround didn’t work :frowning:

I’ve had systemd Shutdown on non-Ubuntu systems in less than three seconds (no SSD). It should be faster, this must be a bug.

I do not have that one either, only the start/stop was needed. Those two lines should read:

DefaultTimeoutStartSec=10S
DefaultTimeoutStopSec=10S

1 Like

Oh thank you I didn’t put the S’s. Problem solved you rock.

Okay this still doesn’t work for me. Not sure what’s wrong. Any other kind of work arounds?

Try to see witch service is cousing the slow boot time by systemd-analyze blame .

1 Like

Do what @IvCHo said. Have you setup Samba or NFS mounts in /etc/fstab?

I'm still kind of a newb so I don't quite know what that means, but I ran systemd-analyze blame and the output is really long but doesn't really help me lol

Hi Justin,

try running “dpkg” per the update guide (a network cable connection is required!) and it may/may not solve the issue you are having!:

I searched for this startup problems . I found an interesting solution . Do not know if it work for you . If your pc is in warrenty you will void it . Trie to remove your RAMs and plug them in to see if it has a change in systemd-analyze blame . Link to the topic here .

Thanks everyone for the suggestions… I’m getting extremely irritated by this. I’m trying to convert multiple people to linux right now and it doesn’t help my case when my computer is taking an incredibly long time to restart. It literally takes 4 minutes to reboot when it used to take like 8 seconds… doesn’t make linux look very good. Of course I can explain that it’s just a bug with systemd, but that will only be met by blank stares and head nods.

I’ve edited the default timeout values, updated 8,000 times, and I don’t feel comfortable taking my RAM out right now as I’m on vacation in Minnesota.

Sorry for the rant guys but this is just a pointless issue that shouldn’t exist and I can’t fix it. face palm

1 Like

Hi
Did you try adding the TimeoutSec= value in the end?
I know it’s not in the default file but I’ve added it without breaking anything.
Cheers

Edit: oh and I’ve used lower case “s” for the “Seconds” suffix, no idea if that matters.

Hi @Justin,

I had to re-install completely on 2 PC’s due to multiple problems, once everything was re-installed, the problems went away!, just a suggestion!. :smiley: (Happy holidays (vacation) btw! :smiley: )

3 Likes

Thanks man. I’m still having issues and I’m on vacation so It’s not very simple for me to do a fresh install right now. has anyone else figured anything out for this???

That is realy strange man . Not yet started . Some service can’t be started and hangs the system . Trie to disable the topmost 3 services with systemctl disable (nameofservice) . To see if it loads faster . If not trie to systemd-analyze verify

2 Likes

It’s really weird because when I use systemd-analyze the output says that it took 3min 6sec for startup which is correct because it’s PAINFULLY slow, but when I use the blame argument there are no lagging processes. I’m pulling my hair out here. I wish I was at home so I could just do a fresh install and be done with it.

Edit: Wait, I just noticed that Lines 1-23…skipping… Won’t let me click on it though.

[email protected]:~$ systemd-analyze
Startup finished in 6.433s (kernel) + 3min 538ms (userspace) = 3min 6.972s
[email protected]:~$ systemd-analyze blame
          2.124s apt-daily.service
           515ms NetworkManager-wait-online.service
           379ms dev-sda2.device
           201ms ModemManager.service
           170ms gpu-manager.service
           165ms accounts-daemon.service
           148ms libvirt-bin.service
           138ms apparmor.service
           133ms systemd-logind.service
           123ms grub-common.service
           118ms apport.service
           115ms NetworkManager.service
           111ms ebtables.service
           107ms irqbalance.service
           104ms ondemand.service
            96ms speech-dispatcher.service
            95ms ufw.service
            87ms lightdm.service
            86ms upower.service
            85ms qemu-kvm.service
            81ms systemd-udev-trigger.service
            81ms alsa-restore.service
            64ms binfmt-support.service
lines 1-23...skipping...
          2.124s apt-daily.service
          2.124s apt-daily.service
          2.124s apt-daily.service
           515ms NetworkManager-wait-online.service
           379ms dev-sda2.device
           201ms ModemManager.service
           170ms gpu-manager.service
           165ms accounts-daemon.service
           148ms libvirt-bin.service
           138ms apparmor.service
           133ms systemd-logind.service
           123ms grub-common.service
           118ms apport.service
           115ms NetworkManager.service
           111ms ebtables.service
           107ms irqbalance.service
           104ms ondemand.service
            96ms speech-dispatcher.service
            95ms ufw.service
            87ms lightdm.service
          2.124s apt-daily.service
          2.124s apt-daily.service
           515ms NetworkManager-wait-online.service
           379ms dev-sda2.device
           201ms ModemManager.service
          2.124s apt-daily.service
           515ms NetworkManager-wait-online.service
           379ms dev-sda2.device
           201ms ModemManager.service
           170ms gpu-manager.service
           165ms accounts-daemon.service
           148ms libvirt-bin.service
           138ms apparmor.service
           133ms systemd-logind.service
           123ms grub-common.service
           118ms apport.service
           115ms NetworkManager.service
           111ms ebtables.service
           107ms irqbalance.service
           104ms ondemand.service
            96ms speech-dispatcher.service
            95ms ufw.service
            87ms lightdm.service
            86ms upower.service
            85ms qemu-kvm.service
            81ms systemd-udev-trigger.service
            81ms alsa-restore.service
            64ms binfmt-support.service
            52ms console-setup.service
            46ms ntp.service
            45ms rsyslog.service
            44ms systemd-journal-flush.service
            40ms boot.mount
            38ms avahi-daemon.service
            37ms networking.service
            37ms systemd-rfkill.service
            36ms udisks2.service
            35ms systemd-journald.service
            33ms wpa_supplicant.service
            32ms systemd-modules-load.service
            30ms bluetooth.service
            30ms [email protected]\x2duuid-f7265437\x2d7235\x2d4a75\x2d88ae\x2de99c3c304d9d.service
            29ms systemd-user-sessions.service
            28ms snap-ubuntu\x2dcore-109.mount
            21ms plymouth-start.service
            17ms polkitd.service
            17ms hddtemp.service
            16ms home.mount
            15ms [email protected]
            14ms systemd-udevd.service
            11ms systemd-tmpfiles-setup.service
            11ms plymouth-read-write.service
            11ms [email protected]\x2duuid-bb329b49\x2d4a19\x2d494f\x2d8235\x2d65597cf42540.service
            11ms libvirt-guests.service
            10ms resolvconf.service
             8ms sys-kernel-debug.mount
             8ms systemd-remount-fs.service
             8ms dev-mqueue.mount
             7ms pppd-dns.service
             7ms rc-local.service
             6ms systemd-update-utmp.service
             6ms dev-hugepages.mount
             6ms systemd-random-seed.service
             6ms proc-sys-fs-binfmt_misc.mount
             5ms kmod-static-nodes.service
             5ms [email protected]:intel_backlight.service
             5ms systemd-update-utmp-runlevel.service
             4ms rtkit-daemon.service
             4ms systemd-tmpfiles-setup-dev.service
             4ms ureadahead-stop.service
             3ms sys-fs-fuse-connections.mount
             3ms systemd-sysctl.service
             1ms dev-loop0.device
             1ms plymouth-quit-wait.service
           780us snapd.socket

Try running the following commands?:

sudo apt-get --fix-missing install

The above command downloads and installs any missing packages on your system.

sudo apt-get --fix-broken install

The above command downloads and installs any broken dependencies on your system.

Restart if anything updates!. :thumbsup:

Thanks for the suggestions as always, my friend. Unfortunately, nothing I’ve tried has worked. Looks like a fresh install is in my future. :dizzy_face:

UPDATE: A fresh install fixed this issue. I was able to keep my home folder intact which was nice.

3 Likes

This isn’t ubuntu mate, but it’s still fun (if you aren’t me)

[email protected] ~ $ systemd-analyze blame
34.675s lightdm.service
34.563s ntp.service
26.178s nmbd.service
25.661s winbind.service
25.157s samba-ad-dc.service
24.739s hddtemp.service
24.615s plymouth-quit-wait.service
12.533s dev-sda1.device
11.741s ufw.service
10.426s grub-common.service
9.419s apparmor.service
9.168s loadcpufreq.service
8.065s NetworkManager-wait-online.service
7.667s ModemManager.service
7.310s NetworkManager.service
6.741s snapd.service
6.038s accounts-daemon.service
5.304s gpu-manager.service
4.230s rsyslog.service
4.135s console-setup.service
4.122s thermald.service
4.086s avahi-daemon.service
3.182s ondemand.service
lines 1-23