Hide Forgot
Created attachment 504427 [details] dmesg Description of problem: Fedora 15 fails to load in Graphical or Multi-user text mode with encrypted partitions in software RAID 1 configuration. Version-Release number of selected component (if applicable): Kernel 2.6.38.6-27.fc15.i686.PAE with all software up to date. How reproducible: Say once in 15 attempts the graphical desktop loads correctly. Steps to Reproduce: 1. Start computer 2. Enter passphrase at plymouth prompt 3. The Fedora logo fills and flares and the monitor goes black in standby mode Actual results: Operating system fails to load Expected results: Graphical desktop login screen Additional info: When the monitor goes into standby mode, if I press the UP arrow on the keyboard I see the text "Started forwarding password requests to plymouth." It hangs there with no opportunity to enter the passphrase again. The attached dmesg shows cryptsetup aborted due to dependency timeout and ends in a failed state. I've read similar bugs and comments about passing passwords to Plymouth but I thought I had better report this simply.
Might be a systemd bug. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I can add more information to this after trying repeatedly. The graphical desktop seems to be loading more frequently. When the screen goes black in standby mode (as noted above) if I press the UP arrow on the keyboard quickly enough (once or twice) I do get an opportunity to enter the luks password for /home, after which the process continues correctly to the graphical logon screen. One time the field was already populated by two asterisks which I could not delete and one time the asterisks could be deleted. But when the field is empty I enter the luks password and everything works ok.
The next few times I tried this method I was asked for the passphrase for swap. After entering it everything worked OK except once when I had to press 'reset' on the computer. It's a global passphrase, by the way.
I have this problem with Fedora 15 but it is intermittent. After many reboots and staring the plots generated by systemd-analyze plot, I noticed that the black screen (with rhgb on the command line) and the prompt for a password for the disk volumes or partitions that are not / or swap, correlates with systemd deciding to run the plymouth-start.service Systemd decides to run the plymouth-start.service when there is no pid file at /run/plymouth/pid. So either plymouthd isn't running (i.e. it died), or it didn't create a pid file in that location (but dracut tells it to). With rhgb removed from the kernel commandline, I modified my plymouth-start.service file to look like this at the end: [Service] Type=oneshot StandardOutput=kmsg+console ExecStart=/bin/echo Wanted to restart plymouthd ExecStart=/bin/ps axf ExecStart=/bin/ls -al /run/plymouth #ExecStart=/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid #ExecStartPost=-/bin/plymouth --show-splash #Type=forking And I confirmed that when systemd tries to run plymouth-start.service, plymouthd isn't running, nor is there a /run/plymouthd/pid file. I added plymouth.debug=file:/run/plymouthd/debug.log to my kernel command line in hopes of catching exactly why plymouthd is dying. So far I have been unable to get the problem to happen again with plymouth.debug set.
Created attachment 505405 [details] plymouthd debug log when symptoms are exhibited I added plymouth.debug=stream:/dev/null to my kernel command line and was able to reproduce the problem. The plymouth debug log is attached. I'm not quite sure what I'm looking at, but it does appear to me to stop unexpectedly at the end.
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