Slow system boot time

Hi, unfortunately my English is poor
I have a problem, thank you for your help
The system manjaro takes 5:38 seconds. It goes up very slowly. What can I do?
Laptop hardware specifications
ASUS X541uj dm651
CPU Intel CORE i7 7500U 2.7 Ghz 3.5 Ghz 2 Core
RAM 12 GB ON BOARD
INTERNAL HDD 1 TB
Graphics card Nvidia GEFORCE GT920MX 2 GB

Welcome to the forum! :wink:

Try installing haveged and see whether it makes a difference.

sudo pacman-mirrors -f 5 && sudo pacman -Syyu haveged
sudo systemctl enable --now haveged

See it if speeds up the boot process. :wink:

1 Like

With thanks for your attention :leaves: :tulip:
The speed increased
1:38
But considering the hardware, I expect more
Come up sooner
I used to use Windows 10, it takes less than 30 seconds, but now it works very slowly inside Linux

See if the following might be helpful… :arrow_down:

1 Like

sudo systemd-analyze blame

2 Likes

I took the password
How can I disable additional services that are not required?

11.837s systemd-journal-flush.service
9.211s upower.service
8.162s udisks2.service
6.273s lvm2-monitor.service
5.982s dev-sda1.device
4.869s systemd-tmpfiles-clean.service
3.890s polkit.service
3.407s systemd-random-seed.service
2.587s lightdm.service
2.112s NetworkManager.service
1.876s avahi-daemon.service
1.872s bluetooth.service
1.536s accounts-daemon.service
1.388s ModemManager.service
1.304s systemd-udevd.service
1.136s ufw.service
1.128s systemd-rfkill.service
1.072s systemd-logind.service
896ms colord.service
854ms systemd-modules-load.service
829ms user@1000.service
769ms systemd-backlight@backlight:intel_backlight.service
736ms tlp.service
lines 1-23…skipping…
11.837s systemd-journal-flush.service
9.211s upower.service
8.162s udisks2.service
6.273s lvm2-monitor.service
5.982s dev-sda1.device
4.869s systemd-tmpfiles-clean.service
3.890s polkit.service
3.407s systemd-random-seed.service
2.587s lightdm.service
2.112s NetworkManager.service
1.876s avahi-daemon.service
1.872s bluetooth.service
1.536s accounts-daemon.service
1.388s ModemManager.service
1.304s systemd-udevd.service
1.136s ufw.service
1.128s systemd-rfkill.service
1.072s systemd-logind.service
896ms colord.service
854ms systemd-modules-load.service
829ms user@1000.service
769ms systemd-backlight@backlight:intel_backlight.service
736ms tlp.service
726ms systemd-tmpfiles-setup-dev.service
454ms modprobe@drm.service
313ms systemd-tmpfiles-setup.service
221ms systemd-udev-trigger.service
218ms wpa_supplicant.service
203ms kmod-static-nodes.service
168ms systemd-binfmt.service
137ms dev-hugepages.mount
137ms dev-mqueue.mount
136ms sys-kernel-debug.mount
135ms sys-kernel-tracing.mount
128ms systemd-sysctl.service
104ms rtkit-daemon.service
91ms systemd-update-utmp.service
48ms systemd-remount-fs.service
41ms tmp.mount
22ms user-runtime-dir@1000.service
6ms systemd-user-sessions.service
2ms sys-fs-fuse-connections.mount
2ms sys-kernel-config.mount
2ms proc-sys-fs-binfmt_misc.mount

That’s not bad. My system boots up from the GRUB menu to the SDDM login screen in about 10 seconds.

1 Like

i prefer

systemd-analyze plot > plot.svg

and then open in a browser.

2 Likes

Following are the steps to solve this:
  1. Do a flush journalctl --flush
  2. Remove/Move the directory /var/log/journal
  3. Set Storage=auto in /etc/systemd/journald.conf
  4. Reboot the machine

You should see an improvement in the boot time.

2 Likes

The speed of the system changed a lot, the speed improved. Thank you :tulip: :tulip: :tulip:

1 Like

Failed to connect to /run/systemd/journal/io.systemd.journal: Permission denied

Hi, I did
Thank you for your attention
systemd-analyze plot

You need root privileges to execute that command. Open up a terminal and type… :arrow_down:

sudo journalctl --flush
1 Like

Failed to execute varlink call: Connection reset by peer
:pensive:

Thanks, I just realized

I’ve used haveged for a ton of stuff but why would it diminish boot times?
Is that because:
1.244s systemd-random-seed.service

1 Like

Yes. haveged is a random number generator, and some processors are not capable of generating enough entropy at boot time. This entropy is needed for cryptographic purposes, such as the login procedure and the mounting of encrypted volumes.

2 Likes