On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering <lennart@xxxxxxxxxxxxxx> wrote: > > On Mo, 11.11.19 13:33, Belisko Marek (marek.belisko@xxxxxxxxx) 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. and then system goes to emergency mode. I inspect logs but cannot see any systemd-fsck process running. > > Lennart > > -- > Lennart Poettering, Berlin BR, marek -- as simple and primitive as possible ------------------------------------------------- Marek Belisko - OPEN-NANDRA Freelance Developer Ruska Nova Ves 219 | Presov, 08005 Slovak Republic Tel: +421 915 052 184 skype: marekwhite twitter: #opennandra web: http://open-nandra.com _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel