[Solved] Fsck Maximum mount count set to -1

Question

I just noticed that fsck has not been running on my system and found the following:
dumpe2fs -h /dev/sda2 | grep -i 'mount count'
dumpe2fs 1.42.12 (29-Aug-2014)
Mount count: 110
Maximum mount count: -1
and
dumpe2fs -h /dev/sda3 | grep -i 'mount count'
dumpe2fs 1.42.12 (29-Aug-2014)
Mount count: 110
Maximum mount count: -1
My fstab is as follows:
/ ext4 rw,noatime,data=ordered,discard 0 1
/home ext4 rw,noatime,data=ordered,discard 0 2
My understanding is that the "-1" for the maximum mount count means the file system doesn't get checked at all.
What would cause the maximum mount count to be set to -1?
One thing that I did do in the past was to remove the fsck hook from mkinitcpio and copy the appropriate systemd files per the wiki on quiet boot.
Last edited by Gumper (2014-11-23 15:01:28)

Answer 1

I marked this post as solved, but I'm seeing this when I check my boot partition.
dumpe2fs -h /dev/sda1 | grep -i 'mount count'
dumpe2fs 1.42.12 (29-Aug-2014)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sda1
NAME FSTYPE SIZE LABEL
sda 477G
├─sda1 vfat 512M
├─sda2 ext4 25G
└─sda3 ext4 451.4G
Do I need to be concerned with this, or is this normal for an EFI system boot partition?