1

All I see is logs for pre-boot fsck, but not forced fsck via the fsck option in the recovery menu.

This is not a duplicate of Where are fsck results logged at boot time, after /forcefsck?. It mentions pre-boot fsck, not this situation where I go into recovery mode to initiate a fsck manually. I use Ubuntu GNOME 16.04, so any solutions that apply to upstart won't help either.

David Foerster
  • 36,264
  • 56
  • 94
  • 147
RoundDuckMan
  • 662
  • 1
    I wonder if you will find them in /var/log/upstart as suggested by this answer – Zanna Jun 03 '16 at 07:09
  • @DavidFoerster Not exactly, I can find fsck results logged at boot time fine, just find any instances of fsck in syslog. It doesn't seem to record fsck executions though forced via the recovery menu. As a result, it's not a duplicate. ;) – RoundDuckMan Jun 03 '16 at 12:58
  • @Zanna Nope, not there either, but I don't use upstart anyways, just systemd, I use 16.04. Thanks for trying though. – RoundDuckMan Jun 03 '16 at 12:59
  • @Zanna but yeah systemd is the default in Ubuntu since... 15.04. Just want to clarify that it wasn't my full intention to have systemd. – RoundDuckMan Jun 03 '16 at 13:08
  • Indeed... So a second round of idle speculation... Could it be in journalctl ? – Zanna Jun 03 '16 at 15:16
  • @Zanna where and how? – RoundDuckMan Jun 04 '16 at 05:05
  • er by default journalctl doesn't get logged (if you type journalctl it just gives you info from current boot like dmesg) but according to this page you can make it persistent just by making a directory for the log! sudo mkdir -p /var/log/journal or by editing /etc/systemd/journald.conf (sorry this isn't helping at all find past forced fsck data even if it works for future forced fsck!) – Zanna Jun 04 '16 at 05:47
  • crap, oh well. Maybe I can use my boot-done fscks as proof that things were fine after all, as I found out. – RoundDuckMan Jun 05 '16 at 03:28

1 Answers1

2

There won't be any, if there is filesystem damage at boot, there won't be any filesystem mounted to write the log in yet. Writing a log can make any damage worse.

user207998
  • 896
  • 7
  • 4