Bug#763652: systemd: boot failed, can't execute /bin/plymouth

[Michael Biebl]

Am 01.10.2014 um 18:49 schrieb Nikolaus Rath:
> On 10/01/2014 09:22 AM, Michael Biebl wrote:
>> Am 01.10.2014 um 17:46 schrieb Nikolaus Rath:
>>> Package: systemd
>>> Version: 208-8
>>> Severity: normal
>>>
>>> Hello,
>>>
>>> My last attempt to boot this system but me into systemd's emergency
>>> mode. Runnig journalctl -xb showed that it failed to start plymouth,
>>> trying to execute /bin/plymouth failed with (IIRC) exit code 2.
>> That is most likely a red herring. The plymouth error is not fatal and
>> therefore most likely not the reason why you ended up in emergency mode.
>>
>> Do you have the journal log from that boot which failed?
> I tried to retrieve them with journalctl -b -1 after restart, but that
> failed (see other bug report). Is there another way to retrieve them
> (now that I have rebooted)?

Since you did not have persistent logs enabled, those messages are most
likely gone. When emergency mode is triggered, rsyslog has not started yet.

I think with the given information, it's best to close this bug report
and reopen it, in case you encounter the issue again.

In that case, when in emergency mode, please save the output of the
following commands
journalctl -alb
systemd-analyze dump
systemctl list-units --failed

Do you agree?

-- 
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...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141001/5a0cbb38/attachment-0002.sig>