Hi A workaround is to boot in maintenance mode. The disks are then correctly checked and next normal boot is ok
Regards Ludovic On Mon, 2015-06-08 at 10:26 +0200, Michael Biebl wrote: > Am 08.06.2015 um 08:01 schrieb Ludovic Lebègue: > > > For a few days now each time the computer boots it forces a file system > > check on two of my disks. > > > > Here is the relevant journalctl entry : > > > > Jun 08 07:48:19 leonardo kernel: input: PS/2 Generic Mouse > > as /devices/platform/i8042/serio1/input/input8 > > Jun 08 07:50:50 leonardo systemd-fsck[459]: fsck: Warning... fsck.ext4 > > for device /dev/sdb1 exited with signal 13. > > Jun 08 07:50:50 leonardo systemd-fsck[459]: fsck failed with error code > > 8. > > Jun 08 07:50:50 leonardo systemd-fsck[459]: Ignoring error. > > Jun 08 07:50:50 leonardo systemd[1]: Started File System Check > > on /dev/disk/by-uuid/553ea986-223e-4391-89be-c9da0c2fa197. > > Jun 08 07:50:50 leonardo systemd[1]: Mounting /home... > > Jun 08 07:50:50 leonardo kernel: EXT4-fs (sdb1): warning: maximal mount > > count reached, running e2fsck is recommended > > Jun 08 07:50:50 leonardo systemd[1]: Mounted /home. > > Jun 08 07:50:50 leonardo kernel: EXT4-fs (sdb1): mounted filesystem with > > ordered data mode. Opts: (null) > > Jun 08 07:51:32 leonardo systemd-fsck[460]: fsck: Warning... fsck.ext4 > > for device /dev/sdc1 exited with signal 13. > > Afaics, the underlying problem is, that fsck fails to fix the problems. > So it's rerun on each boot. > > What odd though, return code 13 is the sum of > > 1 Filesystem errors corrected > 4 Filesystem errors left uncorrected > 8 Operational error > > So, fsck at the same time says the errors were corrected, on the other > side it says they weren't. > Am I interpreting the return codes correctly? > > CCed the e2fsprogs maintainers for input. >
signature.asc
Description: This is a digitally signed message part
