Hello, for some reason, after an unexpected shutdown (caused for example, by a power outage) fsck does not run at the next boot. Corrupted inodes/data is detected and shown on the console at boot, however fsck doesn’t run, and i’ll have to reboot a second time to actually make it run and repair the filesystem. What could be causing this?
put this in your kernel command line fsck.repair=yes fsck.mode=force, this will force fsck
This is really not what i’m looking for, since it will run fsck at EVERY boot, no matter if there’s actually corrupt data or not.
What filesystem are you currently using?
ext4 on all of my partitions (except for the EFI one, obviously)
if the filesystem is working again, simple remove fsck.repair=yes fsck.mode=force from the kcmd 
i have fsck.repair=yes fsck.mode=force for the kernel-fallback image
man systemd-fsck