Re: Systemd boot issue

2014-09-11 Thread Chris Murphy
On Sep 11, 2014, at 2:51 AM, P J P wrote: > Hello Chris, > >> On Wednesday, 10 September 2014 9:15 PM, Chris Murphy wrote: >> Well I have no idea what's on the screen at the time of the hang. Maybe a >> cell phone photo would be useful. Or maybe you should use the debug kernel >> which >>

Re: Systemd boot issue

2014-09-11 Thread Andrew Lutomirski
On Sep 11, 2014 1:51 AM, "P J P" wrote: > >Hello Chris, > > > On Wednesday, 10 September 2014 9:15 PM, Chris Murphy wrote: > > Well I have no idea what's on the screen at the time of the hang. Maybe a > > cell phone photo would be useful. Or maybe you should use the debug kernel which > > was

Re: Systemd boot issue

2014-09-11 Thread P J P
Hello Chris, > On Wednesday, 10 September 2014 9:15 PM, Chris Murphy wrote: > Well I have no idea what's on the screen at the time of the hang. Maybe a > cell phone photo would be useful. Or maybe you should use the debug kernel > which > was one of Paul Wouters suggestions. Or you could go

Re: Systemd boot issue

2014-09-10 Thread Chris Murphy
On Sep 10, 2014, at 2:28 AM, P J P wrote: > Hi, > >> On Wednesday, 10 September 2014 12:28 PM, poma wrote: >> dr. acut? > > Can't say for sure. I added "rdshell rd.debug" parameters to the boot command > line, again it throws a long list of debug messages from - > /lib/dracut-lib.sh@xxx. M

Re: Systemd boot issue

2014-09-10 Thread poma
On 10.09.2014 10:28, P J P wrote: >Hi, > >> On Wednesday, 10 September 2014 12:28 PM, poma wrote: >> dr. acut? > > Can't say for sure. I added "rdshell rd.debug" parameters to the boot command > line, again it throws a long list of debug messages from - > /lib/dracut-lib.sh@xxx. Messages ar

Re: Systemd boot issue

2014-09-10 Thread P J P
Hi, > On Wednesday, 10 September 2014 12:28 PM, poma wrote: > dr. acut? Can't say for sure. I added "rdshell rd.debug" parameters to the boot command line, again it throws a long list of debug messages from - /lib/dracut-lib.sh@xxx. Messages are about trying to setup /etc/sysconfig/network-

Re: Systemd boot issue

2014-09-09 Thread P J P
Hi, After removing 'rhgb quiet' and adding 'systemd.log_level=debug systemd.log_target=console' it generates a huge pile of debug messages at halts at - Switching root. I tried booting the _same_ 3.16.0 kernel on another F20 machine, it stops at the same spot. :( --- Regards -Prasad http

Re: Systemd boot issue

2014-09-09 Thread P J P
Hello Daniel, Chris, Thank you so much for sharing the links and the notes, much appreciate it. > On Wednesday, 10 September 2014 12:23 AM, Daniel J Walsh wrote: > > Did you try to boot with enforcing=0? > To see if it is an SELinux issue? Yes I tried with enforcing=0, it does not seem to

Re: Systemd boot issue

2014-09-09 Thread Daniel J Walsh
Did you try to boot with enforcing=0? To see if it is an SELinux issue? On 09/09/2014 09:46 AM, P J P wrote: > Hello, > > I've been trying to boot into kernel-3.16.0 on a F19 machine. But it just > stops after saying > > .. > [OK] Reached target Initrd Default target > > System is not hung, b

Re: Systemd boot issue

2014-09-09 Thread Chris Murphy
On Sep 9, 2014, at 7:46 AM, P J P 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 dra

Re: Systemd boot issue

2014-09-09 Thread Paul Wouters
On Tue, 9 Sep 2014, P J P wrote: I've been trying to boot into kernel-3.16.0 on a F19 machine. But it just stops after saying Is it a familiar issue to anyone? Is there a way to debug what Systemd is doing after printing above message?? I had similar issues, and I'm still on 3.14.7-100 on