Description of problem: Rawhide boot currently fails to complete (eventually running into some lvm systemd lvm storage subsystem errors). I noticed the error in the Summary while booting: """ [ OK ] Reached target Basic System dracut-pre-pivot[212]: //lib/dracut/hooks/pre-privot/90plymouth-newroot.sh: line 5: [: too many arguments Welcome to Fedora 18 (Rawhide)! [ OK ] Reached target Login Prompts : [ OK ] Stopped Journal Service. Starting Journal Service... [FAIL] Failed to start Journal Service. : """ I think the lvm storage errors are unrelated. Version-Release number of selected component (if applicable): dracut-022-63.git20120727.fc18 How reproducible: every time Steps to Reproduce: 1. install rawhide 2. boot rawhide install Actual results: above error from Expected results: no error Additional info: Booting without rhgb still got the same error.
*** Bug 844229 has been marked as a duplicate of this bug. ***
I'm not sure if this is the same problem or not: I got heaps of "Failed to start Journal Service" errors on a rawhide virtual machine after I added selinux=0 on the kernel command line at boot time, then tried to boot without that. I solved part of the problem by doing touch /.autorelabel as root and rebooting (see http://fedoraproject.org/wiki/SELinux/ManagingFileContext) then running fixfiles relabel as root from a non-graphical terminal. That got rid of a lot of the boot problems, but now I can't get a graphical login dialog, just a blank black X windows screen, even though systemctl status gdm shows that Gnome display manager claims to be running normally.
(In reply to comment #2) > I'm not sure if this is the same problem or not: I got heaps of "Failed to > start Journal Service" errors on a rawhide virtual machine after I added > selinux=0 on the kernel command line at boot time, then tried to boot > without that. I solved part of the problem by doing > > touch /.autorelabel > > as root and rebooting (see > http://fedoraproject.org/wiki/SELinux/ManagingFileContext) then running > > fixfiles relabel > > as root from a non-graphical terminal. That got rid of a lot of the boot > problems, but now I can't get a graphical login dialog, just a blank black X > windows screen, even though > > systemctl status gdm > > shows that Gnome display manager claims to be running normally. This would be a bug for initscripts, because it is supposed to touch .autorelabel and do the fixfiles with: /lib/systemd/system/fedora-autorelabel.service /lib/systemd/system/fedora-autorelabel-mark.service Do you have these service files? And are you sure, you didn't mask them?