On Sat, Jul 19, 2014 at 10:27:48PM +0200, Zbigniew Jędrzejewski-Szmek wrote: > On Fri, Jul 18, 2014 at 06:18:28PM +0200, Bas Wijnen wrote: > > When booting into single user mode, things worked as expected. I was > > unable to remount the fs read-only; the logs you requested are attached. > > (The mei_me messages have always been there, also with sysv init; I > > don't think they are related to the problem.) > Running fsck on a filesystem mounted in rw mode is a bad idea.
I don't think that's happening. The kernel commandline specifies "ro", and AFAIK fsck would refuse to run on a read-write filesystem. The problem seems to be that when it fails, several services are started, one of which is mounting the fs read-write. > So instead of trying to fix things to remount the fs ro, fsck should > finish and succeed or fail *before* the filesystem is remounted rw. Yes, that's a good point. I'm not sure how it worked before; I haven't had fsck fail a lot. It might be that it used to spawn a shell on the read-only fs; that would make sense, especially because the next recommended action is to run fsck again. Thanks, Bas
signature.asc
Description: Digital signature
