drbpn
17.278s systemd-fsck@dev-disk-by\x2duuid-a40b01dc\x2d67c8\x2d4f2a\x2da>
16.982s systemd-journal-flush.service
As @kyrios mentioned, you should really run an fsck against your drive as there may be drive corruption that is being repaired on boot. Use a live ISO and run fsck as root (sudo fsck) against the non-USB drives / partitions shown in lsblk that are ext4 (so by Solus).
Example (there are mounted so it may be different for you, and I also have Windows installed, gasp):
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 450M 0 part
├─sda2 8:2 0 99M 0 part
├─sda3 8:3 0 16M 0 part
├─sda4 8:4 0 136.1G 0 part
├─sda5 8:5 0 7.8G 0 part [SWAP]
├─sda6 8:6 0 78.6G 0 part /
└─sda7 8:7 0 537M 0 part
sdb 8:16 0 1.8T 0 disk
├─sdb1 8:17 0 1.4T 0 part /run/media/joshua/pool
└─sdb2 8:18 0 398.2G 0 part
sdc 8:32 0 2.7T 0 disk
├─sdc1 8:33 0 16M 0 part
├─sdc2 8:34 0 2.5T 0 part
└─sdc3 8:35 0 243.6G 0 part
For me I typically need to target /dev/sdb1, /dev/sdc3, and /dev/sda6 when I'm doing fscks since those are my ext4 partitions used on Solus (sdc3 being sorta a temporary dump for files).
In terms of the journal flushing, I'd suggest putting a hard cap on your journal size or few last boots to reduce the flush times. This can be done by modifying the /etc/systemd/journald.conf and changing one of the following items (I have some recommended numbers below). Examples:
SystemMaxFiles=10 (10 journals)
SystemMaxUse=100M (100mb journal)
You'll need to remove the # before those lines in the log since they're commented out by default. You can also manually clear out your logs by doing something like sudo journalctl --vacuum-size=10M, just keep in mind we may need systemd logs at times to debug issues you may have, so keep the size reasonable.
