Systemd boot issue

[Chris Murphy]

On Sep 9, 2014, at 7:46 AM, P J P <pj.pandit at yahoo.co.in> wrote:

> Is there a way to debug what Systemd is doing after printing above message??

http://fedoraproject.org/wiki/How_to_debug_Dracut_problems
http://freedesktop.org/wiki/Software/systemd/Debugging/

In such a case I always use rd.break to hopefully get a dracut prompt if the initramfs is failing. If that doesn't work and you still get a hang, then you'll need to read about rd.break= and setting it for a point prior to the failure to isolate.

rd.debug will include a huge pile of everything the initramfs is doing, you might avoid this until you know whether it's the initramfs or systemd unit or service giving a problem.

systemd.log_level=debug will produce quite a bit of systemd debug text.

When I'm impatient I used both debug options at the same time, but it makes boot much slower.

If you manage to get to a shell, journalctl -b -l is helpful since it's available in very early boot. Another possibility is if you can boot single user (emergency.target) successfully and enable the systemd early debug shell.



Chris Murphy