Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

9
  • I did try journalctl but realized that it was deconfigured NOT to log from syslog. However, syslog does show the console "clean" message. Commented Apr 6, 2018 at 17:55
  • Regarding systemctl, it only shows the the status of the systemd-fsck service, and its exit code. Commented Apr 6, 2018 at 17:57
  • Github for systemd-fsck also indicates that all fsck "progress" goes to /dev/console, with several unique exits codes. Commented Apr 6, 2018 at 18:00
  • 4
    @awoz - fsck at boot time is run from initramfs so there's no filesystem to write to, though some distros work around that and save the output to /run/initramfs/* or /var/log/fsck/* Commented Apr 6, 2018 at 18:28
  • 1
    @don_crissti a lot of distros work around it by saving the output in a ring buffer in /run/systemd/journal (and hoping they have enough space to keep all the output), which is then saved to the persistent journal if/when it becomes available. :-P. At least if they use dracut initramfs. Commented Jan 12, 2019 at 15:09