systemd-analyze blame?
11.905s snapd.service
11.646s systemd-journal-flush.service
8.877s dev-sda10.device
7.792s polkit.service
6.393s dev-loop11.device
5.889s dev-loop10.device
5.619s dev-loop8.device
5.060s cups.service
4.485s dev-loop7.device
4.197s dev-loop3.device
4.191s dev-loop5.device
4.031s systemd-fsck@dev-disk-by\x2duuid-6A39\x2d883B.service
3.943s dev-loop1.device
3.790s dev-loop4.device
3.775s dev-loop6.device
3.737s dev-loop9.device
3.022s dev-loop0.device
3.006s dev-loop2.device
2.723s NetworkManager.service
1.957s avahi-daemon.service
1.821s systemd-udevd.service
1.767s systemd-logind.service
1.754s var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1515.mount
1.698s apparmor.service
1.697s var-lib-snapd-snap-python38-22.mount
1.641s var-lib-snapd-snap-code-62.mount
1.602s var-lib-snapd-snap-snapd-11588.mount
1.433s var-lib-snapd-snap-teams-4.mount
1.407s systemd-backlight@backlight:intel_backlight.service
1.370s var-lib-snapd-snap-core18-1997.mount
1.272s systemd-modules-load.service
1.240s var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-145.mount
1.239s snapd.apparmor.service
1.223s var-lib-snapd-snap-spotify-46.mount
1.175s var-lib-snapd-snap-qt513-20.mount
1.159s var-lib-snapd-snap-core-10958.mount
1.142s user@1000.service
1.138s var-lib-snapd-snap-walc-19.mount
1.116s ModemManager.service
1.112s boot-efi.mount
1.102s var-lib-snapd-snap-ksuperkey-1.mount
734ms modprobe@drm.service
724ms udisks2.service
724ms systemd-tmpfiles-setup-dev.service
649ms systemd-tmpfiles-setup.service
553ms systemd-binfmt.service
539ms dev-hugepages.mount
537ms dev-mqueue.mount
535ms sys-kernel-debug.mount
533ms sys-kernel-tracing.mount
525ms bluetooth.service
504ms upower.service
431ms systemd-rfkill.service
423ms tmp.mount
419ms kmod-static-nodes.service
417ms modprobe@configfs.service
413ms modprobe@fuse.service
407ms tlp.service
381ms systemd-udev-trigger.service
333ms rtkit-daemon.service
331ms linux-module-cleanup.service
324ms sys-fs-fuse-connections.mount
320ms systemd-random-seed.service
320ms proc-sys-fs-binfmt_misc.mount
318ms sys-kernel-config.mount
288ms wpa_supplicant.service
218ms systemd-sysctl.service
141ms systemd-timesyncd.service
115ms systemd-user-sessions.service
110ms systemd-journald.service
84ms systemd-update-utmp.service
71ms systemd-remount-fs.service
8ms user-runtime-dir@1000.service
1ms snapd.socket
lines 50-74/74 (END)
hmm, systemd-journal-flush.service is back. journalctl --disk-usage?
[amartyasinha918@amartya-hp ~]$ journalctl --disk-usage
Archived and active journals take up 48.0M in the file system.
That’s weird,
ls -lah /var/log/
?
[amartyasinha918@amartya-hp ~]$ ls -lah /var/log/
total 440K
drwxr-xr-x 10 root root 4.0K May 7 01:07 .
drwxr-xr-x 13 root root 4.0K May 7 00:57 …
drwx------ 2 root root 4.0K Feb 14 00:16 audit
-rw-rw---- 1 root utmp 768 May 7 00:07 btmp
-rw-rw---- 1 root utmp 384 May 2 11:44 btmp.1
drwxr-xr-x 2 root root 4.0K May 7 00:00 cups
drwxr-xr-x 2 root root 4.0K Jan 14 11:51 gssproxy
drwxr-sr-x+ 4 root systemd-journal 4.0K Apr 30 01:08 journal
-rw-rw-r-- 1 root utmp 0 Apr 30 01:09 lastlog
drwxr-xr-x 2 root root 4.0K Jan 20 22:03 old
-rw-r–r-- 1 root root 137K May 7 00:48 pacman.log
drwx------ 2 root root 4.0K Apr 28 15:11 private
drwxr-xr-x 2 root root 4.0K Apr 20 17:53 samba
drwxr-xr-x 2 root root 4.0K Apr 30 00:53 timeshift
-rw-rw-r-- 1 root utmp 175K May 7 01:14 wtmp
-rw-r–r-- 1 root root 26K May 7 01:07 Xorg.0.log
-rw-r–r-- 1 root root 26K May 7 01:07 Xorg.0.log.old
-rw-r–r-- 1 root root 5.6K May 2 21:37 Xorg.1.log
-rw-r–r-- 1 root root 0 May 2 19:37 Xorg.1.log.old
You can try rebooting and checking if it will be still there. Other than that, you can go through the things listed in systemd-analyze blame and checking if it’s something abnormal or searching for ways to reduce time spend on them. You should be able to shave at least 5 seconds off of your boot time, but obviously buying an SSD will help a lot more (on my PC with HDD, graphical target reached after: 18 sec, on my laptop with an SSD: 2.2 sec). Hope I helped somewhat 
2 Likes
Thanks for you help. I just masked snapd and rebooted. I think that it is now fine for HDD.
[amartyasinha918@amartya-hp ~]$ systemd-analyze
Startup finished in 3.516s (firmware) + 2.885s (loader) + 3.860s (kernel) + 21.746s (userspace) = 32.009s
graphical.target reached after 20.473s in userspace
1 Like
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.