(on a clean rawhide system, installed and upgrade from F17 a week ago, when dracut killed the previous one)

Created attachment 598234 [details]
dmesg

Created attachment 598235 [details]
lspci

Created attachment 598236 [details]
system logs

Created attachment 598237 [details]
avcs according to ausearch

Created attachment 598238 [details]
avcs according to dmesg

[   16.636642] systemd[1]: Switching root.

Apparently your system has successfully switched to the real root. What is the bug in dracut now again?

I'm experiencing same problems but in my opinion this is not bug in dracut but in kernel: bug #840235

(In reply to comment #7)
> [   16.636642] systemd[1]: Switching root.
> 
> Apparently your system has successfully switched to the real root. What is
> the bug in dracut now again?

As stated in the original message, the system continues to boot only after manual emergency login and starting the gpm service (don't ask me why this is sufficient for systemd to conclude the root switch is successful when it wasn't before)

(In reply to comment #9)
> (In reply to comment #7)
> > [   16.636642] systemd[1]: Switching root.
> > 
> > Apparently your system has successfully switched to the real root. What is
> > the bug in dracut now again?
> 
> As stated in the original message, the system continues to boot only after
> manual emergency login and starting the gpm service (don't ask me why this
> is sufficient for systemd to conclude the root switch is successful when it
> wasn't before)

gpm.service is _not_ in the initramfs, this is already your real root.

Sure but at that point the initramfs handover was not successful according to systemd.

(In reply to comment #11)
> Sure but at that point the initramfs handover was not successful according
> to systemd.

[   12.332055] systemd[1]: Unknown kernel switch rd.systemd.log_level=debug. Ignoring.

change that in "systemd.log_level=debug"


I think this is the journal bug of systemd, which will be fixed with
http://cgit.freedesktop.org/systemd/systemd/commit/?id=bd3fa1d2434aa28564251ac4da34d01537de8c4b

(In reply to comment #12)
> (In reply to comment #11)
> > Sure but at that point the initramfs handover was not successful according
> > to systemd.
> 
> [   12.332055] systemd[1]: Unknown kernel switch rd.systemd.log_level=debug.
> Ignoring.

Already there:

[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-0.rc6.git4.1.fc18.x86_64 root=/dev/mapper/VolGroup00-fedora ro rd.md.uuid=60ab7ad8:5e71ed16:57627bc9:17e70637 rd.md.uuid=746f1cca:4ea1a3c9:22961411:6ca914c8 LANG=fr_FR.UTF-8 SYSFONT=True rd.lvm.lv=VolGroup00/fedora KEYTABLE=fr-latin9 rd.luks=0 rd.dm=0 rd.systemd.log_level=debug systemd.log_level=debug rd.info log_buf_len=1M

Before manually starting gpm convinces systemd it can actually boot:

fedora-s...it-late.service loaded failed failed      Initialize storage subsystems (RAID, LVM, etc.)
fedora-s...ge-init.service loaded failed failed      Initialize storage subsystems (RAID, LVM, etc.)
lvm2-monitor.service       loaded failed failed      Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling
systemd-journald.socket    loaded failed failed      Journal Socket
dev-disk...89a473c02f.swap loaded failed failed      /dev/disk/by-uuid/03924499-649c-41b8-9f63-d389a473c02f
dev-disk...3a0310ffb2.swap loaded failed failed      /dev/disk/by-uuid/ec420dbe-b6a9-48d4-ae67-1d3a0310ffb2

dracut-020-96.git20120717.fc18.x86_64
+
kernel-3.5.0-0.rc7.git1.2.fc18.x86_64

boots again properly. Thank you very much

BTW, the dracut problems made lwn headlines this week, so some explanations may calm the press

(In reply to comment #15)
> dracut-020-96.git20120717.fc18.x86_64
> +
> kernel-3.5.0-0.rc7.git1.2.fc18.x86_64
> 
> boots again properly. Thank you very much
> 
> BTW, the dracut problems made lwn headlines this week, so some explanations
> may calm the press

yeah, http://lists.fedoraproject.org/pipermail/devel/2012-July/169602.html

Seems this has been fixed a while back already. Closing.