Description of problem: Sometimes on cold boot I don't get a password prompt for my luks root partition. Rebooting with Ctrl+Alt+Del is a workaround that will always work. Version-Release number of selected component (if applicable): systemd 208-9.fc20 plymouth 0.8.9-3.2013.08.14.fc20 dracut 034-64.git20131205.fc20.1 anaconda 20.25.15-1.fc20 How reproducible: often (chance >50%) on two different machines, both running F20 with all updates from updates-testing installed Additional info: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.12.7-300.fc20.x86_64 root=/dev/mapper/luks-6ba90457-13bf-4a36-acfb-355e0eed063d ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks.uuid=luks-6ba90457-13bf-4a36-acfb-355e0eed063d vconsole.font=latarcyrheb-sun16 rhgb LANG=de_DE.UTF-8
This bug is not related to plymouth: I've uninstalled plymouth (and regenerated initramfs) – bug is still present. This bug is still present on 3.13.3-200.fc20 kernel on x86_64.
I am also seeing this issue, or one very much like it. I was able to work around it by adding rd.auto to the kernel command line. This makes me think it is a dracut issue.
I see the same problem too. It looks like a race condition early in boot, because any attempt to add debugging stuff (rd.debug for example) causes the bug to vanish. Also adding some kernel modules in the initramfs (with add_drivers+=" vfat ") is also enough to hide this race. I could generate two rdsosreport.txt log files, from the same computer, one where the boot stalls, and another where the password prompt to unlock the luks volumes is normally displayed.
Created attachment 867380 [details] rdsosreport.txt when the luks volumes are not unlocked
Created attachment 867381 [details] rdsosreport.txt when the luks volumes are correctly unlocked
I'm occasionally seeing the same at work (and so is a work colleague). Removing the "quiet" from the kernel command line seems to always result in a successful boot. So far, I've never seen this at home.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.