[Bug 1619753] [NEW] systemd-fsck does not show results of rootfs filesystem check in logs or journald

[Adam Blomberg]

Public bug reported:

Prior to the systemd paradigm shift, Ubuntu versions provided mechanisms
to be able to see the results of a filesystem check performed on the
root filesystem either in boot.log in 12.04 or in mountall.log in 14.04.

As of 16.04, there is no way to see the output of systemd-fsck when it
is run on the root filesystem.

root at ubuntu-16-04-1:~# lsb_release -rd
Description:    Ubuntu 16.04.1 LTS
Release:        16.04

root at ubuntu-16-04-1:~# apt-cache policy systemd
systemd:
  Installed: 229-4ubuntu7
  Candidate: 229-4ubuntu7
  Version table:
 *** 229-4ubuntu7 500
        500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     229-4ubuntu4 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages


Steps to reproduce:

1) Force fsck on next reboot by altering linux boot commandline:
   Edit /etc/default/grub and add "fsck.mode=force" to the GRUB_CMDLINE_LINUX variable. 
   If you also want to force repair behavior, also add "fsck.repair=yes" to the same variable. 

# example: 
GRUB_CMDLINE_LINUX="fsck.mode=force fsck.repair=yes" 

Once the changes have been made, run "sudo update-grub" to update the
boot info, then reboot.

2) After boot, journalctl does not report any filesystem repair details
for the root fs, only for secondary filesystems such as /boot or others
designated in /etc/fstab.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

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

Title:
  systemd-fsck does not show results of rootfs filesystem check in logs
  or journald

Status in systemd package in Ubuntu:
  New

Bug description:
  Prior to the systemd paradigm shift, Ubuntu versions provided
  mechanisms to be able to see the results of a filesystem check
  performed on the root filesystem either in boot.log in 12.04 or in
  mountall.log in 14.04.

  As of 16.04, there is no way to see the output of systemd-fsck when it
  is run on the root filesystem.

  root at ubuntu-16-04-1:~# lsb_release -rd
  Description:    Ubuntu 16.04.1 LTS
  Release:        16.04

  root at ubuntu-16-04-1:~# apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu7
    Candidate: 229-4ubuntu7
    Version table:
   *** 229-4ubuntu7 500
          500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
          100 /var/lib/dpkg/status
       229-4ubuntu4 500
          500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  Steps to reproduce:

  1) Force fsck on next reboot by altering linux boot commandline:
     Edit /etc/default/grub and add "fsck.mode=force" to the GRUB_CMDLINE_LINUX variable. 
     If you also want to force repair behavior, also add "fsck.repair=yes" to the same variable. 

  # example: 
  GRUB_CMDLINE_LINUX="fsck.mode=force fsck.repair=yes" 

  Once the changes have been made, run "sudo update-grub" to update the
  boot info, then reboot.

  2) After boot, journalctl does not report any filesystem repair
  details for the root fs, only for secondary filesystems such as /boot
  or others designated in /etc/fstab.

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