Arch Linux

sevk

Member

From: CN

Registered: 2017-02-09

Posts: 37

boot time too long , how to find the reason ?

➜  ~ systemd-analyze
Startup finished in 3.129s (kernel) + 1min 37.094s (userspace) = 1min 40.223s
graphical.target reached after 1min 37.031s in userspace.

➜  ~ systemd-analyze blame
10.359s systemd-tmpfiles-clean.service
5.690s dev-sdc1.device
2.531s udisks2.service
2.466s systemd-journal-flush.service
2.185s systemd-sysusers.service
1.695s ldconfig.service
1.325s systemd-tmpfiles-setup.service
1.323s mnt-b6.mount
1.084s packagekit.service
1.081s dbus.service
992ms lvm2-monitor.service
957ms iptables.service
817ms user@1000.service
686ms mnt-a1.mount
629ms systemd-tmpfiles-setup-dev.service
596ms systemd-udevd.service
569ms NetworkManager.service
563ms mnt-a2.mount
438ms systemd-modules-load.service
400ms cpupower.service
373ms mnt-a4.mount
365ms mnt-t1.mount
349ms systemd-random-seed.service
306ms systemd-udev-trigger.service
273ms kmod-static-nodes.service
256ms systemd-journal-catalog-update.service
246ms systemd-journald.service
244ms mnt-b3.mount
241ms mnt-b5.mount
219ms systemd-sysctl.service
206ms sys-kernel-config.mount
197ms alsa-restore.service
190ms sys-fs-fuse-connections.mount
181ms mnt-t3.mount
180ms mnt-b2.mount
177ms power-profiles-daemon.service
167ms upower.service
167ms mnt-t2.mount
167ms systemd-timesyncd.service
148ms polkit.service
145ms dev-disk-by\x2duuid-8ac6d424\x2de89d\x2d4991\x2d89d9\x2d56e66db29b77.swap
140ms systemd-update-utmp.service
114ms systemd-logind.service
81ms modprobe@fuse.service
69ms systemd-binfmt.service
62ms modprobe@drm.service
61ms systemd-user-sessions.service
48ms modprobe@configfs.service
36ms cron-root-root-8.service
36ms systemd-update-done.service
36ms user-runtime-dir@1000.service
33ms dev-hugepages.mount
32ms dev-mqueue.mount
32ms sys-kernel-tracing.mount
32ms sys-kernel-debug.mount
31ms rtkit-daemon.service
24ms systemd-remount-fs.service
22ms modprobe@loop.service
16ms cron-kk-kk-0.service
3ms cron-root-root-9.service
3ms proc-sys-fs-binfmt_misc.mount
3ms tmp.mount
1ms modprobe@dm_mod.service

sevk

Member

From: CN

Registered: 2017-02-09

Posts: 37

Re: boot time too long , how to find the reason ?

 

➜  ~ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 37.031s
└─sddm.service @1min 37.031s
└─systemd-user-sessions.service @1min 36.955s +61ms
└─network.target @1min 36.937s
└─NetworkManager.service @1min 36.366s +569ms
└─dbus.service @1min 35.264s +1.081s
└─basic.target @1min 35.231s
└─sockets.target @1min 35.230s
└─dbus.socket @1min 35.229s
└─sysinit.target @1min 35.197s
└─systemd-update-done.service @1min 35.160s +36ms
└─systemd-journal-catalog-update.service @1min 34.866s +256ms
└─systemd-tmpfiles-setup.service @1min 33.484s +1.325s
└─local-fs.target @1min 33.406s
└─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @1min 33.487s
└─local-fs-pre.target @6.281s
└─systemd-tmpfiles-setup-dev.service @5.633s +629ms
└─systemd-sysusers.service @3.404s +2.185s
└─systemd-remount-fs.service @3.175s +24ms
└─systemd-journald.socket @3.143s
└─-.mount @2.980s
└─-.slice @2.972s

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,349

Re: boot time too long , how to find the reason ?

└─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @1min 33.487s
└─local-fs-pre.target @6.281s

One of your mounts is slow? (It might even be bogus and fail, we're close to the 90s systemd standard timeout)
If you don't boot "quiet" (and maybe even then) or with a  stupid splash screen, you might actually see a big fat red line during the boot.
Also check your system journal.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc