You received this message not because the maximum mount count was reached, but because the 'Next check after' date was in the past.
Next check after Tue Jan 12 23:11:26 2016 So this is not a problem with the output of update-motd-fsck-at-reboot, at all; rather, it is a bug in your boot that is *not* checking the filesystem, given the filesystem's settings. Reassigning to systemd. ** Package changed: update-notifier (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574707 Title: update-motd-fsck-at-reboot notify checked for errors at next reboot even after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574707/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
