Bug#808151: systemd: failed to start remount root and kernel file system
biebl at debian.org
Thu Dec 17 13:55:54 GMT 2015
Am 17.12.2015 um 13:46 schrieb Frank B. Brokken:
> 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).
What exactly do you mean with halt? The systems completely locks up so
you can't use the keyboard and switch to tty9?
That would sound like a kernel problem.
> 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?
Can you make a screenshot or a video from the boot process with "quiet"
removed from the kernel command line.
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers