Failed to start File System Check by version 1.12.0 (systemd-service)
We require a lot more information before we can do anything with your bug report. Like, what happened? What system are you using? Can you show us your `emerge --info` output?
Created attachment 556412 [details] emerge-info
journalctl-dump: Nov 25 12:19:55 Gentoo-Desktop systemd-fsck[1449]: Error: Failed to open the device! Nov 25 12:19:55 Gentoo-Desktop systemd-fsck[1449]: Info: Check FS only due to RO Nov 25 12:19:55 Gentoo-Desktop systemd-fsck[1449]: Info: Mounted device! Nov 25 12:19:55 Gentoo-Desktop systemd-fsck[1449]: Info: Fix the reported corruption. Nov 25 12:19:55 Gentoo-Desktop systemd-sysctl[1453]: Couldn't write '1' to 'kernel/sysrq', ignoring: No such file or directory Nov 25 12:19:55 Gentoo-Desktop systemd-sysctl[1453]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Nov 25 12:19:55 Gentoo-Desktop systemd-fsck[1449]: Running request reboot.target/start/replace Nov 25 12:19:55 Gentoo-Desktop systemd-fsck[1449]: fsck failed with exit status 255.
This is a bug tracker, not a support forum. Please seek help in support channels and re-open this if you determine this is actually a bug in systemd-fsck.
I think it's a bug, because by change from sys-fs/f2fs-tool 1.11.0-r1βto 1.12.0 the attached error appear. Move back to 1.11.0-r1 it disappear.
This is the first time you have mentioned "sys-fs/f2fs-tool". That seems pretty important. You really need to provide sufficient information to diagnose the issue. We are not going to drag it out of you bit by bit. I don't see any evidence that this is a bug in systemd-fsck; it's either an issue with the fsck command provided by f2fs-tools or your filesystem is corrupted in some way.
*** This bug has been marked as a duplicate of bug 671786 ***