wilman
February 27, 2022, 2:31am
1
Friends I hope you are well, Someone knows how I can improve the time that starts manjaro, started well but once the power went out in the house and now takes longer than normal to start. in advance thank you very much.
this is how long it takes:
Startup finished in 13.972s (firmware) + 5.257s (loader) + 4.607s (kernel) + 1min 32.362s (userspace) = 1min 56.200s
graphical.target reached after 50.263s in userspace
39.089s pkgfile-update.service
11.668s upower.service
8.938s man-db.service
7.670s udisks2.service
5.931s polkit.service
5.555s systemd-journal-flush.service
5.342s dev-sdb2.device
5.158s NetworkManager-wait-online.service
3.362s NetworkManager.service
1.945s systemd-fsck@dev-disk-by\x2duuid-0C45\x2d3241.service
1.508s avahi-daemon.service
1.493s systemd-logind.service
1.429s ldconfig.service
1.422s systemd-udevd.service
1.304s logrotate.service
1.233s lvm2-monitor.service
1.021s systemd-backlight@backlight:acpi_video0.service
916ms systemd-sysusers.service
872ms packagekit.service
779ms systemd-journal-catalog-update.service
733ms ModemManager.service
683ms systemd-random-seed.service
669ms boot-efi.mount
666ms user@1000.service
349ms systemd-tmpfiles-setup.service
307ms systemd-timesyncd.service
264ms systemd-tmpfiles-clean.service
247ms systemd-tmpfiles-setup-dev.service
235ms dev-hugepages.mount
234ms dev-mqueue.mount
234ms sys-kernel-debug.mount
233ms sys-kernel-tracing.mount
233ms kmod-static-nodes.service
232ms modprobe@configfs.service
231ms modprobe@drm.service
231ms modprobe@fuse.service
207ms systemd-sysctl.service
144ms systemd-update-utmp.service
136ms systemd-udev-trigger.service
133ms systemd-journald.service
122ms pamac-daemon.service
115ms systemd-user-sessions.service
111ms systemd-modules-load.service
100ms dev-disk-by\x2duuid-4df516a1\x2dadca\x2d4691\x2db544\x2d0170c88563a2.swap
70ms rtkit-daemon.service
53ms systemd-remount-fs.service
26ms sys-kernel-config.mount
16ms user-runtime-dir@1000.service
16ms alsa-restore.service
14ms systemd-update-done.service
I am new to linux
39s is a lot of time. Try updating your mirrors and reboot:
sudo pacman-mirrors -f 5 && sudo pacman -Syyu
If it still takes that much time then share the output of these commands:
systemctl status pkgfile-update.service
systemctl status pkgfile-update.timer
1 Like
wilman
February 27, 2022, 5:47pm
3
I am very grateful to you for your help, you are a crack, you are the best, thank you for your help.
This is the time it takes after the command you told me.
~ systemd-analyze
Startup finished in 13.710s (firmware) + 3.015s (loader) + 4.697s (kernel) + 18.809s (userspace) = 40.232s
graphical.target reached after 18.808s in userspace
~ systemd-analyze blame
6.445s systemd-journal-flush.service
6.242s polkit.service
6.014s udisks2.service
5.012s dev-sdb2.device
3.560s upower.service
3.133s NetworkManager.service
2.726s ldconfig.service
1.319s avahi-daemon.service
1.304s systemd-logind.service
1.264s systemd-udevd.service
1.261s lvm2-monitor.service
893ms ModemManager.service
859ms systemd-fsck@dev-disk-by\x2duuid-0C45\x2d3241.service
838ms boot-efi.mount
785ms user@1000.service
717ms systemd-random-seed.service
717ms systemd-sysusers.service
666ms systemd-journal-catalog-update.service
390ms systemd-tmpfiles-setup-dev.service
375ms systemd-tmpfiles-setup.service
358ms systemd-timesyncd.service
285ms modprobe@drm.service
280ms systemd-udev-trigger.service
251ms systemd-backlight@backlight:acpi_video0.service
237ms dev-disk-by\x2duuid-4df516a1\x2dadca\x2d4691\x2db544\x2d0170c88563a2.swap
167ms systemd-journald.service
157ms dev-hugepages.mount
156ms dev-mqueue.mount
155ms sys-kernel-debug.mount
155ms sys-kernel-tracing.mount
154ms kmod-static-nodes.service
153ms modprobe@configfs.service
152ms modprobe@fuse.service
133ms systemd-update-utmp.service
95ms systemd-modules-load.service
94ms systemd-sysctl.service
89ms sys-kernel-config.mount
84ms systemd-binfmt.service
65ms systemd-user-sessions.service
35ms tmp.mount
28ms systemd-remount-fs.service
27ms systemd-update-done.service
26ms rtkit-daemon.service
18ms user-runtime-dir@1000.service
16ms alsa-restore.service
3ms proc-sys-fs-binfmt_misc.mount
1ms sys-fs-fuse-connections.mount
and this is the result of the last 2 commands you told me to use.
systemctl status pkgfile-update.service
○ pkgfile-update.service - pkgfile database update
Loaded: loaded (/usr/lib/systemd/system/pkgfile-update.service; static)
Active: inactive (dead)
TriggeredBy: ● pkgfile-update.timer
~ systemctl status pkgfile-update.timer 3 ✘
● pkgfile-update.timer - pkgfile database update timer
Loaded: loaded (/usr/lib/systemd/system/pkgfile-update.timer; enabled; vendor preset: disabled)
Active: active (waiting) since Sun 2022-02-27 12:40:08 -05; 5min ago
Until: Sun 2022-02-27 12:40:08 -05; 5min ago
Trigger: Mon 2022-02-28 00:00:00 -05; 11h left
Triggers: ● pkgfile-update.service
feb 27 12:40:08 wilman-ms7b84 systemd[1]: Started pkgfile database update timer.
1 Like
system
Closed
March 2, 2022, 7:47am
4
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.