Help with Booting time


New Member
May 2, 2019
Reaction score
I had installed Pop OS in my laptop (dual booted with Windows). However the booting took too long and I decided to reinstall Pop OS. Even now it takes a long time. I have attached a screenshot of the "systemd-analyze blame" command output. Please tell me how I can improve it. (I have an 8GB Ram with 8GB Swap, no SSD)


  • Boot time.png
    Boot time.png
    178.6 KB · Views: 830
Last edited:

G'day @Aditya1999 and welcome to :)

To help us a little to help you, you could try copying and pasting output from Terminal into your Reply Pane here. You can do that with the Toolbar above where you type here - under the + sign are options including "Code" and "Spoiler".

So for example if I issue a command

cat /etc/fstab

I can then issue its output, by in Terminal choosing Edit - Select All, and then right-clicking choose Copy

chris@BeaverMATEdot1-SSD:~$ cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>

UUID=e3161b45-fa4a-413d-b4b4-2ddd2348bee2    /    ext4    errors=remount-ro    0    1
UUID=C802-1F4A    /boot/efi    vfat    umask=0077    0    1
#/swapfile    none    swap    sw    0    0

For something long such as log output or your systemd command, the Spoiler is good and you can give it a Title or not

chris@BeaverMATEdot1-SSD:~$ systemd-analyze blame
7.417s NetworkManager-wait-online.service
4.701s udisks2.service
1.482s systemd-rfkill.service
1.257s dev-loop0.device
1.244s dev-loop2.device
1.224s dev-loop1.device
1.211s dev-loop4.device
1.203s dev-loop3.device
1.187s dev-loop6.device
1.178s dev-loop5.device
1.171s dev-loop7.device
1.136s dev-loop8.device
801ms ufw.service
769ms keyboard-setup.service
609ms snapd.service
598ms dev-sdb5.device
230ms NetworkManager.service
186ms systemd-resolved.service
175ms snap-core-6673.mount
165ms systemd-timesyncd.service
163ms ModemManager.service
152ms systemd-journal-flush.service
146ms systemd-udev-trigger.service
138ms systemd-udevd.service
129ms snap-core-6531.mount
120ms networkd-dispatcher.service
113ms snap-pulsemixer-23.mount
111ms gpu-manager.service
108ms snap-core-6818.mount
92ms upower.service
88ms loadcpufreq.service
80ms snap-ubuntu\x2dmate\x2dwelcome-220.mount
76ms motd-news.service
70ms snap-software\x2dboutique-31.mount
67ms accounts-daemon.service
64ms grub-common.service
58ms apparmor.service
56ms thermald.service
54ms snap-software\x2dboutique-39.mount
51ms apport.service
50ms avahi-daemon.service
49ms speech-dispatcher.service
49ms [email protected]
47ms lm-sensors.service
43ms systemd-logind.service
39ms systemd-fsck@dev-disk-by\x2duuid-C802\x2d1F4A.service
39ms wpa_supplicant.service
36ms rsyslog.service
35ms ssh.service
35ms systemd-tmpfiles-setup-dev.service
33ms systemd-journald.service
30ms snap-ubuntu\x2dmate\x2dwelcome-319.mount
28ms snap-ubuntu\x2dmate\x2dwelcome-242.mount
26ms binfmt-support.service
26ms systemd-modules-load.service
25ms lightdm.service
25ms polkit.service
25ms pppd-dns.service
21ms networking.service
20ms sys-kernel-debug.mount
20ms systemd-sysctl.service
19ms dev-hugepages.mount
19ms dev-mqueue.mount
17ms kmod-static-nodes.service
15ms systemd-remount-fs.service
15ms cpufrequtils.service
13ms systemd-update-utmp.service
13ms snapd.seeded.service
13ms snapd.socket
12ms plymouth-read-write.service
11ms qemu-kvm.service
10ms kerneloops.service
10ms hddtemp.service
10ms proc-sys-fs-binfmt_misc.mount
9ms systemd-random-seed.service
9ms bluetooth.service
9ms ureadahead-stop.service
9ms console-setup.service
8ms systemd-tmpfiles-setup.service
8ms systemd-tmpfiles-clean.service
8ms openvpn.service
7ms systemd-user-sessions.service
6ms sys-fs-fuse-connections.mount
5ms systemd-backlight@backlight:intel_backlight.service
5ms systemd-update-utmp-runlevel.service
4ms sys-kernel-config.mount
3ms boot-efi.mount
3ms setvtrgb.service
3ms rtkit-daemon.service
2ms systemd-backlight@leds:dell::kbd_backlight.service
2ms plymouth-quit-wait.service

Then it is easy for us to copy a line and say "No, this should read that", better than a screenshot of Terminal.

That being said :D

Can you give us the output of

cat /etc/fstab


Chris Turner
Sure, I'll keep that in mind. Here's the output :

[adityapc@aditya-pc ~]$ cat /etc/fstab
# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=7223-33A6                            /boot/efi      vfat    defaults,noatime 0 2
UUID=c4ae677c-23a8-46b4-881f-0ea6dc3600bb swap           swap    defaults,noatime 0 2
UUID=31871a6b-5129-4bfc-b738-f305d74e858d /              ext4    defaults,noatime 0 1
I have to go for my Aussie evening, momentarily, but to keep you going, and given you have 8GB RAM, I would first try editing fstab to "comment out" swap.

I don't have Pop OS, but being Ubuntu-based you could likely do it with gedit if you prefer GUI, or nano if you prefer Terminal.

For gedit

sudo gedit /etc/fstab

Change the line with swap in it to place a comment (#) at the start, so it becomes

#UUID=c4ae677c-23a8-46b4-881f-0ea6dc3600bb swap           swap    defaults,noatime 0 2

Save, reboot and report back.


Thanks a lot, man! Booting time is certainly down. Here's the breakdown :
Startup finished in 6.711s (firmware) + 7.585s (loader) + 9.276s (kernel) + 20.901s (userspace) = 44.475s reached after 20.309s in userspace
adityapc@pop-os:~$ systemd-analyze blame
8.533s udisks2.service
5.757s accounts-daemon.service
5.726s systemd-udev-settle.service
5.512s networkd-dispatcher.service
5.373s ModemManager.service
5.044s dev-sda7.device
4.049s grub-common.service
3.663s NetworkManager.service
3.610s apport.service
3.120s switcheroo-control.service
3.049s gpu-manager.service
2.910s rsyslog.service
2.899s wpa_supplicant.service
2.891s thermald.service
2.884s bluetooth.service
2.848s systemd-logind.service
2.836s pppd-dns.service
2.634s avahi-daemon.service
2.388s systemd-resolved.service
1.706s packagekit.service
1.557s [email protected]
1.491s polkit.service
1.451s systemd-timesyncd.service

I was also wondering if this is okay for a system like mine, ie, with an 8GB RAM and no SSD? Or is it still too long?
I'm also having the same problem with my newly installed pop os. Please help me out
# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# <file system>  <mount point>  <type>  <options>  <dump>  <pass>
/dev/mapper/cryptswap  none  swap  defaults  0  0
PARTUUID=20a0faa6-6630-4941-8989-1161ae9708f4  /boot/efi  vfat  umask=0077  0  0
UUID=d316e73c-edc2-4a9b-b110-476de9177579  /  ext4  noatime,errors=remount-ro  0  0
G'day @Raju1990 and welcome to :)

The line

/dev/mapper/cryptswap none swap defaults 0 0

1. ... indicates to me that you have likely chosen at install to encrypt your Home partition. Is that the case?

2. How much RAM do you have?

3. What size is your Swap partition?

4. Can you print us the output, as was done above, of

systemd-analyze blame


Chris Turner
Thanks for your response
I have 4 GB of DDR4 ram and the processor is AMD A6
The swap partition consists of 3.91 GB
Screenshot from 2020-07-05 20-54-54.png

Screenshot from 2020-07-05 20-55-15.png
@Raju1990 thanks for the prompt response and the information.

plymouth-quit-wait.service is obviously the greatest consumer of time, on the face of it.

I am working on Kali issues at the moment, and then have to answer some questions and post a Thread on Linux Mint 20 changes, but I will come back to pop-os next 48 hours with more information.

Thanks for your patience.

In the meantime, if you have not already made the acquaintance of Timeshift, I would suggest you do.

You can read about it at my Thread here

or Linux Lite have a good guide here

Before we implement any changes to your system addressing the boot time issues, I would advocate taking a full, on demand, screenshot with Timeshift, so that if anything goes wrong, we can roll back to where you were.



Members online

Latest posts