Hide Forgot
Description of problem: On booting, after entering my LUKS password the system continues to boot for a few seconds and then puts the monitor into standby mode. To continue to boot I must: * press ESC so that I see a text screen asking for my password (again) * enter my password and press enter I have LUKS and LVM configured on this system: # dmsetup ls --tree luks-cd4fe06b-cad2-4a42-8925-9d309ca30c62 (253:2) └─ (8:17) vg_worm01-LogVol00 (253:1) └─luks-4ea0a3b7-5868-426d-8f12-ac58e2911efb (253:0) └─ (8:3) vg_worm00-LogVol00 (253:4) └─luks-2a3bee45-582c-4045-9042-2e48d5febf50 (253:3) └─ (8:6) I also have some bind mounts. Here is my /etc/fstab: /dev/mapper/vg_worm01-LogVol00 / ext4 defaults 1 1 UUID=cc6e7172-7f4e-4edf-8f08-a067ce88202e /boot ext3 defaults 1 2 /dev/mapper/vg_worm00-LogVol00 /home ext4 defaults 1 2 /dev/mapper/luks-cd4fe06b-cad2-4a42-8925-9d309ca30c62 /mnt/backup ext3 defaults 1 2 UUID=66412111-7bc5-404f-a072-0f764d8007fa swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /mnt/backup/mock /var/lib/mock none bind 0 0 /mnt/backup/mock-cache /var/cache/mock none bind 0 0 (as well as some NFS mounts which are not relevant) Version-Release number of selected component (if applicable): systemd-26-8.fc15.x86_64 dracut-009-12.fc15.noarch plymouth-0.8.4-0.20110510.2.fc15.x86_64 How reproducible: Every time I boot. Additional info: If I comment out both the bind mounts at the end, the system boots fine (but of course those paths are not bound).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Is this still an issue or can this bug be closed?
I still see this symptom occasionally but not every boot (e.g. happened this morning but not yesterday) with Fedora 16. systemd-37-3.fc16.x86_64
hmm wondering if this is some kind of race issue and or plymouth
Can you add --debug to the daemon startup in the plymouth-start.service and see if anything juicy pops on in the logs?
This seems to be a sympton of a larger problem an reporter mentioned an reliable workaround in bug 749027 comment three add "plymouth.debug=file:/run/plymouth/debug.log" to the kernel command line. Can you confirm/deny this workaround?
I've added it now. We'll see...
Adding the plymouth maintainer who might shed some lights on what's happening here...
Reassigning against plymouth afters speaking with it's maintainer. This is a fall out from requests being asynchronous now. What happens is that system needs a password so it first asks plymouthd if there are any already known passwords then plymouth will either respond with the password or will instead say "i don't know any" then it will ask plymouth to ask for a password. Now you can end up in a situation where you end up with two processes asking for any known passwords at the same time plymouthd telling both of them at the same time "i don't know any"then both processes at the same time saying "okay ask the user" At that point plymouthd will know about that password and the next request that comes by plymouthd won't say "i don't know any" instead it will reply with what it knows... The fix should be pretty straightforward and will be dealt with as soon as he has the time to do it. Thanks for your patience.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping