[arch-general] systemd fsck

[Mantas Mikulėnas]

On Sat, Aug 11, 2012 at 6:27 AM, David Benfell
<benfell at parts-unknown.org> wrote:
> 2) But I did notice an error that worried me--just because it looks
> worrying--as it came up:
>
> Aug 09 13:34:36 graton systemd-fsck[270]: /dev/sda3 is mounted.
> Aug 09 13:34:36 graton systemd-fsck[270]: e2fsck: Cannot continue,
> aborting.
> Aug 09 13:34:36 graton systemd-fsck[270]: fsck failed with error code 8.
> Aug 09 13:34:36 graton systemd-fsck[270]: Ignoring error.
> Aug 09 13:34:36 graton systemd-fsck[289]: /dev/sdb1: clean,
> 398077/33554432 files, 27916145/134217728 blocks
> Aug 09 13:34:36 graton systemd-fsck[287]: /dev/sdb3: clean,
> 647214/21102592 files, 26531961/84405504 blocks
> Aug 09 13:34:36 graton systemd-fsck[348]: /dev/sda4: clean,
> 1650719/59490304 files, 57620902/237931957 blocks
> Aug 09 13:34:37 graton systemd-fsck[320]: /dev/sda1: clean, 33/10040
> files, 22152/40160 blocks
> Aug 09 13:34:37 graton systemd-fsck[293]: /dev/sdb2: clean,
> 4926903/67125248 files, 195736925/268500992 blocks
>
> /dev/sda3 is the root partition.

Does your kernel have the "ro" option specified? I know little about
this, but I think ext34 partitions cannot be checked while mounted
read-write and the usual way of doing this for the root partition has
been to add "ro" to the kernel command line, and to remount the root
partition read-write after checking it. (Though running the check from
initramfs might be an even better method, Arch here has an option for
that.)

-- 
Mantas Mikulėnas