[Bug 513644] Re: Does not log fsck invocations in /var/log/fsck/

[Adam Blomberg]

Thank you k-doug for placing the suggested workaround here!

I would also like to mention that with regards to Xenial (16.04) and any
Ubuntu release using systemd, the mechanism for forcing filesystem
checks on startup is presently unable to display the results of the
filesystem check on the rootfs in any logs or in journald, and I have
recently opened a defect against systemd [1].  If you would agree with
me that systemd-based Ubuntu's should have this visibility, please have
a look at this new defect and upvote it if it is also effecting you.

Best regards,
-Adam (paradox606)

[1] - https://bugs.launchpad.net/bugs/1619753

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/513644

Title:
  Does not log fsck invocations in /var/log/fsck/

Status in mountall package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mountall

  This concerns mountall 1.0 in Karmic.

  After fsck is invoked at boot time, the two log files in
  /var/log/fsck/ remain empty. In Jaunty, the
  /etc/init.d/check{fs,root}.sh scripts saved the output of the commands
  to that directory ("A log is being saved in ${FSCK_LOGFILE} if that
  location is writable") but mountall has yet to do this.

  As this would have to be newly implemented, I'd like to request a
  slight change from the Jaunty behavior, and have entries be appended
  to the log files rather than the files being overwritten each time
  with the latest (single) entry. Log rotation on these files may be
  good, too, although I'm not sure which package would/should be
  responsible for that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/513644/+subscriptions