There’s your culprit. 
WOW!
One minute five and a half seconds of watching white dots
turn green and back to white again, and again, and again!
This same system on Mint 18.3, took but half that time.
charlie@OptiPlex-740 ~ $ systemd
Startup finished in 19.666s (kernel) + 46.126s (userspace) = 1min 5.792s
graphical.target reached after 46.110s in userspace
charlie@OptiPlex-740 ~ $ systemd-analyze blame
30.428s dev-sda1.device
27.447s systemd-journal-flush.service
24.009s ufw.service
23.126s lvm2-monitor.service
22.667s systemd-tmpfiles-setup-dev.service
19.985s systemd-sysctl.service
9.893s udisks2.service
9.005s snapd.service
7.278s ModemManager.service
7.245s ubuntu-system-adjustments.service
7.014s accounts-daemon.service
6.872s grub-common.service
6.286s ntp.service
6.272s avahi-daemon.service
6.214s loadcpufreq.service
6.190s NetworkManager.service
6.164s apport.service
5.659s wpa_supplicant.service
4.926s thermald.service
3.162s systemd-modules-load.service
3.099s keyboard-setup.service
1.751s apt-daily-upgrade.service
1.648s apt-daily.service
1.594s apparmor.service
Are all these 19 + second services really necessary?
AND… I Don’t even have a modem!!
( I’m hardwired to a Router and then WiFi, to my ISP)
1 Like
I have 82 processes starting up, most of which are 100MS or more. I use KDE which is a good portion of the 82, didn’t count. I’m not smart enough to know what I can do without, sorry. Though you have themaid.service which I didn’t see in my list.
Here’s the list for you to compare:
:# systemd-analyze blame
36.823s backup-rpmdb.service
30.197s mandb.service
23.085s btrfsmaintenance-refresh.service
19.237s wicked.service
11.333s plymouth-quit-wait.service
9.370s display-manager.service
6.579s postfix.service
3.504s lvm2-monitor.service
2.887s initrd-switch-root.service
2.879s firewalld.service
2.588s apache2.service
2.221s rsyslog.service
1.858s mariadb.service
1.768s apparmor.service
1.405s ModemManager.service
1.259s mcelog.service
1.256s kbdsettings.service
1.255s nscd.service
1.183s home.mount
1.005s upower.service
798ms wickedd-dhcp6.service
784ms wickedd-auto4.service
766ms wickedd-dhcp4.service
653ms polkit.service
620ms systemd-tmpfiles-clean.service
587ms udisks2.service
575ms systemd-udevd.service
482ms logrotate.service
363ms systemd-tmpfiles-setup-dev.service
337ms var.mount
333ms sysroot.mount
326ms user@1000.service
302ms klog.service
256ms auditd.service
253ms systemd-tmpfiles-setup.service
241ms systemd-rfkill.service
200ms avahi-daemon.service
190ms plymouth-switch-root.service
179ms dev-disk-by\x2duuid-edcf79ef\x2db878\x2d4470\x2d9777\x2dd221f4ee6fd5.swap
150ms plymouth-start.service
147ms chronyd.service
144ms systemd-journal-flush.service
140ms systemd-random-seed.service
133ms systemd-modules-load.service
129ms wickedd.service
111ms systemd-vconsole-setup.service
107ms initrd-parse-etc.service
107ms wpa_supplicant.service
103ms opt.mount
99ms boot-grub2-i386\x2dpc.mount
96ms srv.mount
92ms systemd-sysctl.service
88ms systemd-udev-trigger.service
85ms iscsi.service
85ms backup-sysconfig.service
81ms plymouth-read-write.service
75ms systemd-logind.service
70ms root.mount
68ms boot-grub2-x86_64\x2defi.mount
63ms systemd-remount-fs.service
61ms systemd-update-utmp.service
55ms wickedd-nanny.service
54ms systemd-timesyncd.service
50ms systemd-fsck-root.service
45ms sys-kernel-debug.mount
45ms dev-hugepages.mount
44ms dev-mqueue.mount
40ms dracut-cmdline.service
34ms dracut-shutdown.service
32ms tmp.mount
29ms usr-local.mount
26ms systemd-user-sessions.service
21ms rtkit-daemon.service
20ms systemd-update-utmp-runlevel.service
20ms systemd-journald.service
15ms initrd-cleanup.service
14ms check-battery.service
12ms dracut-pre-trigger.service
11ms \x2esnapshots.mount
8ms sys-fs-fuse-connections.mount
6ms kmod-static-nodes.service
3ms initrd-udevadm-cleanup-db.service
1 Like
@cliffsloane, I’m not sure there is a “normal” boot time given all the possible combinations of hardware and software. But to me, your boot time is way too high. My wife’s laptop is a Dell-E6410, Intel i5-m560 at 2.6 GHz and 4 GB Ram, It has a regular Hitachi 160 BG HDD at 5400 RPM, built in 2009.
Her stats: “Startup finished in 4.736s (kernel) + 20.300s (userspace) = 25.037s”
This was after a clean install of Linux Mint Cinnamon 18.3.
I don’t know what is causing your long boot time, but I don’t believe it is the HDD. Twice I had long boot times after relocating the swap file. I found out that fstab in /etc did not match where the swap was moved to. After I updated fstab, boot time was back to “normal”,
Absolutely necessary.
Yes.
Apparently something for LVM, so if you use it, apparently it is needed.
Firewall.
30 seconds just for your HDD. 
I doubt it is the hard drive too. When I had Mint (weeping for that hard drive!!), the time was half. THere is something in my Ubuntu install that takes time. I suspect it is that I have three DEs installed, although I chose to switch over to Maté. But hell if I’m gonna try to uninstall a DE!!
But am I gonna complain about a 3-minute boot when it takes me 3 minutes to clear space off my desk?
1 Like
Nice command.
Sure, as geeks, we have to compare our results…
edi@MintBox-Mini2:~$ systemd-analyze
Startup finished in 6.557s (firmware) + 5.065s (loader) + 5.484s (kernel) + 2.777s (userspace) = 19.886s
graphical.target reached after 2.765s in userspace
By the way, @abhishek wrote a nice little article for this… Find Out How Long Does it Take To Boot Your Linux System
1 Like
Switched to Mint Mate 19.2 from Ubu Mate 19.04 and my system got nearly twice as fast now?
Startup finished in 4.250s (kernel) + 1.415s (userspace) = 5.665s
graphical.target reached after 1.411s in userspace
2 Likes
All boot times performed on the same X220 ThinkPad using different DASD (disks).
Linux Mint Cinnamon 18.3 on a SSD.
Startup finished in 5.803s (kernel) + 1.432s (userspace) = 7.235s (Who could complain?)
Linux Mint Cinnamon 19.1 on a SSD
Startup finished in 38.394s (kernel) + 3.001s (userspace) = 41.395s (The teckie in me - Why?)
graphical.target reached after 2.993s in userspace
easyt50@X220:~$ systemd-blame
systemd-blame: command not found
easyt50@X220:~$ systemd-analyze blame
997ms keyboard-setup.service
859ms ufw.service
685ms systemd-resolved.service
664ms dev-sda1.device
622ms systemd-timesyncd.service
474ms systemd-fsck@dev-disk-by\x2duuid-2CCB\x2d0935.service
329ms lightdm.service
328ms plymouth-quit-wait.service
316ms NetworkManager.service
Linux Mint Cinnamon 19.2 on a HDD
easyt50@X220:~$ systemd-analyze
Startup finished in 8.374s (kernel) + 20.148s (userspace) = 28.523s (Not bad for a HDD.)
graphical.target reached after 20.142s in userspace
19.2 on a HHD is faster booting then 19.1 on a SSD! Doesn’t sound right.
Nice command and what a surprise to be so fast:
polleke@polleke-Akoya-P4130-D-MD8302-2469:~$ sudo systemd-analyze
[sudo] wachtwoord voor polleke:
Startup finished in 4.680s (kernel) + 1min 31.406s (userspace) = 1min 36.087s
graphical.target reached after 5.461s in userspace
New Linux kernels probably have some patch, making the boot too slow.
I do not have the minor patience with it, and recently returned for Win 10.
( Using a lite version specially prepared ) without any bullshit M$ 
Boot in 27 secs, aproximatelly 
Probably or certainly? Because if you are uncertain, your suggestions are pure shots into the dark.
I bought an SSD drive and put / on it and cut my boot up time in half:
Startup finished in 2.862s (kernel) + 1.715s (initrd) + 22.103s (userspace) = 26.681s
Mint 19.3 Cinnamon. Kernel 5.0.0-37. 10 yr-old laptop w/ SSD.
1 Like
This is mine on laptop:
Startup finished in 5.113s (firmware) + 2.091s (loader) + 7.627s (kernel) + 1min 8.196s (userspace) = 1min 23.028s
graphical.target reached after 10.935s in userspace
I’m not even going to post mine. I cleaned it up and it’s over 4 minutes! However, my desktop is up and ready long before that, and my desktop also acts as a server. It maps to drives on other computers, copies data to a large local drive, and runs CrashPlan Pro for an offsite backup. It is also my local time server for my network, and many many other things.
Just my two cents :
Startup finished in 5.031s (kernel) + 47.149s (userspace) = 52.181s
graphical.target reached after 47.142s in userspace
Is this good or slow ?
slower than if you had your user space on an SSD drive
Check out this article:
It gives you some hints to what might take that long.
My desktop (8 i7 cores/64GB RAM Kubuntu) has:
Startup finished in 3.1s (kernel) + 9.8s (userspace) = 13.0s graphical.target reached after 9.1s in userspace
My laptop (4 i3 cores/4GB RAM Garuda Linux) has:
Startup finished in 3.9s (kernel) + 13.0s (userspace) = 16.9s graphical.target reached after 13.0s in userspace
As far as to the hard drive issue:
From my experience, the performance benefits of SSDs are usually grossly overrated when it comes to boot times. SSDs are really great when it comes to read or write huge files but with many small files, they tend to be hardly faster than HDDs.
If your system is ready in a minute, using a SSD might save you 10-15 seconds. It will still be annoying. If it takes 10 seconds, the 1 or 2 seconds you might save are not really an issue.
3 Likes
First time, but from my own experience, I would respectfully dis-agree. This was one of the most noticeable benefits of a SSD to me. It may be over rated, but I was impress.
Of course you are correct about big files esp doing the copy / write to the same physical disk. My memory is not 100%, but a Win backup went from about 12 minutes to about 4 or 5 minutes when the HDD was replaced with a SSD.
2 Likes