When booting previous releases of oS, If I pressed any arrow key when boot I could see a nice detailed log of all the services being started (the classic OK/FAIL screen), now I can’t see anything, maybe this could be because I have an SSD and the system boots too fast in order to actually see the log but I’m not sure.
Another thing related to this is that /var/log/boot.log is not being populated anymore, the only logs I see here are from udev and plymouth, I used to see here the exact same screen from boot.
Is this related to systemd and the way that systemd stores logs?
I used to force an fsck check by creating a file /forcefsck, but I think this does not work anymore. I read somewhere that now I have to force it via kernel parameters in grub.
Now, how can I see the fsck logs at boot? or later in some log?
Does putting fsck.mode=force in the kernel parameters executes the file system check for both BTRFS and XFS?
Is oS configured to execute an fsck when something went wrong? for instance, after a power outage.