I also have this problem. I have no LVM, no RAID, no graphical boot,
just a plain old disk partition.
The "mount count" has passed "maximum mount count", systemd runs fsck
but it never finishes, it gets interrupted by SIGPIPE. It all starts
again next boot.
Output from cat /proc/cmdline is:
BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64
root=UUID=491b60dd-2eb2-428e-880d-8e411009938d ro quiet
Output of
$ sudo journalctl -u systemd-fsckd.service
is not useful, just like message #110.
Like him, I will test the command
systemctl mask systemd-fsckd.service systemd-fsckd.socket
once I understand it. Please explain that.
--
Bruno Schneider
