Comment 1 for bug 1718966

Additional information:

root@ubuntu:~# systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service
<email address hidden>
   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)

root@ubuntu:~# systemctl status systemd-fsck@dev-mapper-vg00\varvol.service
<email address hidden>
   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)

root@ubuntu:~# systemctl status --all | grep fsck
root@ubuntu:~#

Trusty doesn't have the full implementation of systemd like xenial has.

xenial:

$ ls -l /lib/systemd/system/systemd-fsck*
-rw-r--r-- 1 root root 551 Jul 18 19:56 /lib/systemd/system/systemd-fsckd.service
-rw-r--r-- 1 root root 540 Jul 18 19:56 /lib/systemd/system/systemd-fsckd.socket
-rw-r--r-- 1 root root 674 Jul 18 19:56 /lib/systemd/system/systemd-fsck-root.service
-rw-r--r-- 1 root root 648 Jul 18 19:56 /lib/systemd/system/systemd-fsck@.service

trusty:

# ls -l /lib/systemd/system/systemd-fsck*
ls: cannot access /lib/systemd/system/systemd-fsck*: No such file or directory

The system tries to call the fsck check but fails because the method or file doesn't exist:

Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory.

On a xenial system, that file would be this:
==========================
$ cat /lib/systemd/system/systemd-fsck@.service
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.

[Unit]
Description=File System Check on %f
Documentation=man:systemd-fsck@.service(8)
DefaultDependencies=no
BindsTo=%i.device
Wants=systemd-fsckd.socket
After=%i.device systemd-fsck-root.service local-fs-pre.target systemd-fsckd.socket
Before=shutdown.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/lib/systemd/systemd-fsck %f
TimeoutSec=0
==========================

And the systemctl services and units would be there on xenial:
==========================
$ systemctl status --all | grep fsck | grep ^●
● systemd-fsck-root.service - File System Check on Root Device
● systemd-fsck@dev-disk-by\x2duuid-0f1a47d4\x2d67c5\x2d4c18\x2d9159\x2dfd1d4409f30d.service - File System Check on /dev/disk/by-uuid/0f1a47d4-67c5-4c18-9159-fd1d4409f30d
● systemd-fsck@dev-disk-by\x2duuid-D233\x2dB0AC.service - File System Check on /dev/disk/by-uuid/D233-B0AC
● systemd-fsckd.service - File System Check Daemon to report status
● system-systemd\x2dfsck.slice
● systemd-fsckd.socket - fsck to fsckd communication Socket
==========================

But not on Trusty:

root@trustysnap:~# systemctl status --all | grep fsck
root@trustysnap:~#

I don't see any relevant logs in /var/log.