Bug#808151: systemd: failed to start remount root and kernel file system

Frank B. Brokken f.b.brokken at rug.nl
Thu Dec 17 12:46:43 GMT 2015

Dear Michael Biebl, you wrote:

> What happens afterwards? Are you dropped into the rescue shell?

Afterwards (i.e., after the initial failure message) the system tries to
continue booting, but shows lots of failure messages, eventually grinding to a
halt. No reboot (e.g. ctrl-alt-del) is possible and there's no rescue shell.

> If not, try to enable the debug shell by adding "systemd.debug-shell" to
> the kernel command line. This will give you a root shell on tty9.

Unfortunately, it doesn't, since the system halts (I first removed the
automatic reboot on failure).

However, during the process I observed that setting systemd.debug-shell and
removing the default 'quiet' specification from grub's /etc/default/grub (so,
now it specifies:


greatly reduces the chances of a failing boot. Not completely, but
greatly. Still, when rebooting fails there's just the plain halt, w/o a debug
shell. Since removing the quiet also produces a lot more output on the screen,
might my problem not simply be some timing problem?

    Frank B. Brokken
    Center for Information Technology, University of Groningen
    (+31) 50 363 9281 
    Public PGP key: http://pgp.surfnet.nl
    Key Fingerprint: DF32 13DE B156 7732 E65E  3B4D 7DB2 A8BE EAE4 D8AA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 465 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151217/2a7d19ef/attachment-0002.sig>

More information about the Pkg-systemd-maintainers mailing list