systemd-analyze blame
╰─λ systemd-analyze blame
27.308s fstrim.service
7.253s systemd-swap.service
6.446s NetworkManager-wait-online.service
1.851s man-db.service
1.299s systemd-tmpfiles-setup.service
734ms updatedb.service
577ms linux-modules-cleanup.service
437ms lvm2-monitor.service
392ms dev-nvme0n1p2.device
273ms systemd-random-seed.service
209ms [email protected]
199ms [email protected]
139ms systemd-guest-user.service
136ms systemd-udev-trigger.service
121ms ananicy.service
120ms systemd-remount-fs.service
100ms systemd-journald.service
89ms systemd-journal-flush.service
75ms lm_sensors.service
74ms boot-efi.mount
60ms systemd-vconsole-setup.service
55ms systemd-udevd.service
54ms systemd-timesyncd.service
54ms polkit.service
53ms logrotate.service
51ms systemd-logind.service
49ms udisks2.service
46ms ModemManager.service
42ms NetworkManager.service
37ms systemd-modules-load.service
28ms avahi-daemon.service
27ms dev-zram18.swap
27ms dev-disk-by\x2duuid-9e29982b\x2de7e5\x2d40ec\x2db8e3\x2d48238c3d800f.swap
26ms sys-kernel-config.mount
26ms dev-zram16.swap
26ms dev-zram20.swap
24ms dev-zram23.swap
23ms dev-zram22.swap
23ms dev-zram11.swap
22ms dev-zram6.swap
22ms plymouth-start.service
22ms systemd-fsck@dev-disk-by\x2duuid-2DFD\x2d9830.service
22ms dev-zram7.swap
21ms dev-zram3.swap
21ms dev-zram21.swap
21ms dev-zram24.swap
20ms dev-zram9.swap
20ms dev-zram25.swap
20ms dev-zram17.swap
19ms sys-fs-fuse-connections.mount
19ms dev-zram19.swap
19ms dev-zram13.swap
19ms dev-zram0.swap
19ms dev-zram10.swap
18ms dev-zram4.swap
18ms dev-zram5.swap
18ms dev-zram15.swap
18ms dev-zram2.swap
17ms dev-zram8.swap
16ms systemd-guest-config.service
16ms dev-zram12.swap
16ms dev-zram14.swap
14ms systemd-sysctl.service
13ms plymouth-read-write.service
13ms [email protected]
13ms plymouth-quit-wait.service
13ms dev-zram1.swap
12ms accounts-daemon.service
12ms plymouth-quit.service
12ms plymouth-deactivate.service
12ms [email protected]
12ms dev-hugepages.mount
11ms dev-mqueue.mount
10ms systemd-fsck@dev-disk-by\x2duuid-5bd677bc\x2dd8c5\x2d4f82\x2da2bd\x2d0524cf6c995b.service
10ms [email protected]
10ms [email protected]
10ms [email protected]
10ms sys-kernel-debug.mount
10ms [email protected]
10ms [email protected]
10ms bluetooth.service
10ms systemd-tmpfiles-clean.service
10ms [email protected]
9ms sys-kernel-tracing.mount
9ms [email protected]
9ms [email protected]
9ms kmod-static-nodes.service
8ms home.mount
7ms [email protected]
7ms root.mount
7ms systemd-tmpfiles-setup-dev.service
7ms [email protected]
7ms [email protected]
6ms srv.mount
6ms var-cache.mount
5ms dev-zram26.swap
5ms systemd-update-utmp.service
5ms var-log.mount
4ms home-guest.mount
4ms systemd-user-sessions.service
4ms var-tmp.mount
4ms rtkit-daemon.service
4ms wpa_supplicant.service
3ms systemd-rfkill.service
2ms tmp.mount
lines 58-105/105 (END)
systemd-analyze --user
╰─λ systemd-analyze blame --user
621ms pulseaudio.service
90ms plasma-baloorunner.service
71ms plasma-kglobalaccel.service
21ms plasma-kactivitymanagerd.service
4ms obex.service
4ms dbus.socket
3ms dconf.service
1ms xdg-user-dirs-update.service
Done thanks
What the… Whats this??.
It’s the second part of a long line; fsck is being run on your drive.
10ms systemd-fsck@dev-disk-by\x2duuid-5bd677bc\x2dd8c5\x2d4f82\x2da2bd\x2d0524cf6c995b.service
1 Like
Cheers for info.
1 Like
I cant attach new info because it wont allow me to notify over 5 users