Ridiculous boot time

DataDrake done, but the problem stills

[deleted] You need to run sudo clr-boot-manager update to have the change take effect.
@dbarron ^^

DataDrake nice it's works ... but now i got another problem.

if i make a systemd-analyze i got this:
Startup finished in 4.905s (firmware) + 2.591s (loader) + 1.191s (kernel) + 3.080s (initrd) + 24.581s (userspace) = 36.351s
graphical.target reached after 24.571s in userspace

it's so many time only for userspace i want to reduce that. And if i make a systemd-analyze blame i get this:

11.487s systemd-journal-flush.service
5.278s ModemManager.service
5.047s lvm2-pvscan@8:2.service
4.885s udisks2.service
4.653s systemd-tmpfiles-setup.service
3.587s NetworkManager.service
2.957s systemd-udevd.service
2.287s bluetooth.service
2.283s avahi-daemon.service
2.283s clr-boot-manager-booted.service
2.273s systemd-logind.service
2.237s systemd-modules-load.service
2.151s systemd-tmpfiles-setup-dev.service
1.992s initrd-switch-root.service
1.819s org.cups.cupsd.service
1.242s systemd-rfkill.service
1.164s auditd.service
1.033s polkit.service
929ms upower.service
851ms dev-disk-by\x2duuid-a070020b\x2df326\x2d43a8\x2dbe2c\x2da26e46b4927f.swap
821ms accounts-daemon.service
679ms gdm.service
592ms dev-mqueue.mount
566ms user@21.service
544ms colord.service
493ms systemd-sysctl.service
478ms systemd-random-seed.service
476ms systemd-backlight@backlight:intel_backlight.service
454ms dev-hugepages.mount
453ms sys-kernel-debug.mount
453ms systemd-remount-fs.service
439ms systemd-udev-trigger.service
385ms systemd-journald.service
262ms systemd-resolved.service
244ms kmod-static-nodes.service
181ms wpa_supplicant.service
142ms initrd-parse-etc.service
131ms systemd-fsck-root.service
102ms systemd-hostnamed.service
60ms systemd-update-utmp.service
44ms user@1000.service
16ms snapd.socket
16ms systemd-user-sessions.service
13ms initrd-cleanup.service
7ms systemd-update-utmp-runlevel.service
5ms aa-lsm-hook.service
4ms initrd-udevadm-cleanup-db.service
3ms sys-fs-fuse-connections.mount
2ms tmp.mount

I dont know why the systemd-journal-flush.service take so many time, any idea?

PD: I would like to ask the following: which services can i deactivate to get a 5 seconds or less boot?

Any that you don't use (for instance bluetooth) (ie we don't know what services you use), but I doubt you're going to shave off 5 seconds. Spend your time buying a very fast SSD instead.

dbarron I ask because I previously had Windows 8 and it was very fast. Why Solus will be different if it is supposed is faster than Windows?
I don't think my pc is the problem

PD: I mean which services are not necessary to boot like password interface or modemManager.

PD2: Sorry about that of 5 seconds or less i think 15 or 10 it's ok ¯_(ツ)_/¯

PD3: Anyway i just want to now why the systemd-journal-flush.service spends 15 seconds

DataDrake no, i dont make the encryptation step.

i follow this tutorial to reduce the the time of journal:
https://askubuntu.com/questions/1094389/what-is-the-use-of-systemd-journal-flush-service

but now if i make (again) systemd-analyze blame got this:
13.505s lvm2-pvscan@8:2.service
10.928s systemd-journal-flush.service
10.373s systemd-tmpfiles-setup.service
5.432s ModemManager.service
3.879s systemd-udevd.service
3.849s NetworkManager.service
2.477s bluetooth.service
2.475s avahi-daemon.service
2.474s clr-boot-manager-booted.service
2.469s systemd-logind.service
2.389s systemd-modules-load.service
2.002s initrd-switch-root.service
1.973s systemd-tmpfiles-setup-dev.service
1.770s org.cups.cupsd.service
1.160s auditd.service
944ms polkit.service
897ms dev-disk-by\x2duuid-a070020b\x2df326\x2d43a8\x2dbe2c\x2da26e46>
888ms accounts-daemon.service
795ms upower.service
704ms sys-kernel-debug.mount
683ms systemd-rfkill.service
632ms systemd-udev-trigger.service
629ms udisks2.service
623ms systemd-remount-fs.service
621ms gdm.service
599ms systemd-backlight@backlight:intel_backlight.service
562ms wpa_supplicant.service
505ms systemd-random-seed.service
495ms user@21.service
463ms systemd-sysctl.service
359ms dev-hugepages.mount
358ms dev-mqueue.mount
350ms systemd-journald.service
325ms systemd-resolved.service
156ms colord.service
151ms systemd-tmpfiles-clean.service
135ms systemd-fsck-root.service
120ms initrd-parse-etc.service
111ms kmod-static-nodes.service
73ms systemd-user-sessions.service
71ms systemd-update-utmp.service
64ms user@1000.service
14ms initrd-cleanup.service
7ms systemd-update-utmp-runlevel.service
5ms aa-lsm-hook.service
4ms sys-fs-fuse-connections.mount
3ms tmp.mount
3ms initrd-udevadm-cleanup-db.service
685us snapd.socket

so i succesfully lose 1 second from systemd-journal-flush but i win 20 seconds more in lvm2pvscan@8:2.service and systemd-tmpfiles-setup.service

:') i wanna cry