On Tue, Nov 12, 2019 at 3:52 AM Belisko Marek <marek.beli...@gmail.com> wrote: > > On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering > <lenn...@poettering.net> wrote: > > > > On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gmail.com) wrote: > > 65;5802;1c > > > Hi, > > > > > > I'm using systemd 234 (build by yocto) and I've setup automount of > > > sdcard in fstab. This works perfectly fine. But I have seen from time > > > to time when system goes to emergency mode because sdcard filesystem > > > (ext4) have an issue and cannot be mounted. I was thinking about > > > forcing fsck for every boot. Reading manual it should be enough to set > > > passno (6th column in fstab) to anything higher then 0. I set ti to 2 > > > but inspecting logs it doesn't seems fsck is performed. Am I still > > > missing something? Thanks. > > > > Well, note that ext4's fsck only does an actual file system check > > every now and then. Hence: how did you determine fsck wasn't started? > > > > Do you see the relevant fsck in "systemctl -t service | grep > > systemd-fsck@"? > I just saw in log: > [ OK ] Found device /dev/mmcblk1p1. > Mounting /mnt/sdcard... > [ 8.339072] EXT4-fs (mmcblk1p1): VFS: Found ext4 filesystem with > invalid superblock checksum. Run e2fsck? > [FAILED] Failed to mount /mnt/sdcard.
This isn't normal. Your effort should be on finding out why this problem is happening in the first place. This doesn't strike me as the (somewhat) ordinary case of unclean unmount, which results in journal replay at next mount attempt. But something considerably more serious. -- Chris Murphy _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
