Comment 4 for bug 1619753

Thank you for the clarification Martin.

I was able to confirm that the fsck results are located in /run/initramfs/fsck.log on my test system as you described.

I found that if the /etc/default/grub file was modified to include:

GRUB_CMDLINE_LINUX="fsck.mode=force"

Then after running "sudo update grub" and rebooting, the basic result was shown in /run/initramfs/fsck.log:

Log of fsck -C -f -a -V -t ext4 /dev/mapper/ubuntu--16--04--1--vg-root
Wed Sep 7 14:42:05 2016

fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/mapper/ubuntu--16--04--1--vg-root] fsck.ext4 -f -a -C0 /dev/mapper/ubuntu--16--04--1--vg-root
/dev/mapper/ubuntu--16--04--1--vg-root: 97274/689520 files (0.1% non-contiguous), 534347/2757632 blocks

Wed Sep 7 14:42:06 2016
----------------

If I modify /etc/default/grub to include:

GRUB_CMDLINE_LINUX="fsck.mode=force fsck.repair=yes"

Then after running "sudo update grub" and rebooting, the verbose result was shown in /run/initramfs/fsck.log:

Log of fsck -C -f -y -V -t ext4 /dev/mapper/ubuntu--16--04--1--vg-root
Wed Sep 7 14:38:19 2016

fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/mapper/ubuntu--16--04--1--vg-root] fsck.ext4 -f -y -C0 /dev/mapper/ubuntu--16--04--1--vg-root
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/ubuntu--16--04--1--vg-root: 97271/689520 files (0.1% non-contiguous), 534306/2757632 blocks

Wed Sep 7 14:38:20 2016
----------------

Best regards,

-Adam