Re: How to get a log of fsck on boot partition when using systemd-sysv
On 2014-05-10 23:49 +0200, Jape Person wrote:
> In various logs on these systems I see an indication that "touch
> /forcefsck" doesn't work with systemd running the show, and that
> adding
>
> fsck.mode=force
>
> to the linux boot line in Grub is now the proper way to force fsck to
> run at boot time.
It is true that fsck.mode=force is the recommended way, but the methods
used by the checkfs.sh initscript are still supported despite the
warning systemd-fsck prints when you use them.
> However, though I see that fsck is running when I boot the system
> after altering the boot process, there is still no output from the
> operation written to the checkroot file. I presume this is part of the
> rhubarb I've noticed on various lists concerning the logging of the
> boot process when using systemd.
Those messages end up in the journal. The initscript captures them with
logsave(8) which is a kludge to work around the problem that syslog is
not yet available when it runs.
> This is hardly a huge problem for me, but I'd like to keep practicing
> this slightly OCD behavior if I can on a couple of the more critical
> machines.
>
> Would anyone have thoughts on how I can get a record of the file
> system check on the boot drive when using systemd?
Something like "journalctl -b | grep systemd-fsck". I haven't figured
out how to get "journalctl -u" to work here.
Cheers,
Sven
Reply to: