Hide Forgot
Description of problem: I only have two partitions, / and swap: Device Boot Start End Blocks Id System /dev/sda1 * 2048 1026047 512000 83 Linux /dev/sda2 1026048 312580095 155777024 8e Linux LVM both are encrypted with the same password. When starting up, looks like the password is used to access / properly, but the same passwd isn't applied to swap. Entering the same password doesn't help in the plymouth screen. When I hit 'esc' and enter the passwd in the text mode, each key has to be pressed twice or even thrice for a corresponding '*' to appear. When the appropriate number of *s are provided, the boot process goes on. May 27 08:40:24 amit-x200 kernel: [ 35.400265] systemd-fsck[660]: /dev/sda1: clean, 88/128016 files, 64598/512000 blocks May 27 08:40:24 amit-x200 kernel: [ 35.601343] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) May 27 08:40:24 amit-x200 kernel: [ 63.473000] systemd-cryptsetup[614]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/6cb8a495-b861-40e3-b2e4-aaf6c1982290. May 27 08:40:24 amit-x200 kernel: [ 70.332708] systemd-cryptsetup[614]: Invalid passphrase. May 27 08:40:24 amit-x200 kernel: [ 83.577602] systemd-cryptsetup[614]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/6cb8a495-b861-40e3-b2e4-aaf6c1982290. May 27 08:40:24 amit-x200 kernel: [ 90.616367] Adding 4192280k swap on /dev/mapper/luks-6cb8a495-b861-40e3-b2e4-aaf6c1982290. Priority:0 extents:1 across:4192280k This didn't happen with the F15 kernel on F14 userspace on my laptop, but I suspect I saw this on my desktop (F15 kernel on F14 userspace) once, when I reverted to the F14 kernel. However, happens on both laptop and desktop after upgrading to F15. FWIW I run the F16 (2.6.39-1) kernel on my laptop but the F15 kernel on the desktop.
(In reply to comment #0) > same passwd isn't applied to swap. Entering the same password doesn't help in > the plymouth screen. When I hit 'esc' and enter the passwd in the text mode, > each key has to be pressed twice or even thrice for a corresponding '*' to > appear. When the appropriate number of *s are provided, the boot process goes > on. I saw the same thing after the upgrade to F15. It's sorted out now and I think an old F14 kernel was responsible. For some reason, I didn't get a fc15 kernel via anaconda but after a 'yum upgrade' later on the luks passphrase nightmare disappeared. I'd like to know what could be the reason for that. I'm worried I'll have the same problem with custom kernels..
(In reply to comment #1) > I saw the same thing after the upgrade to F15. It's sorted out now and I think > an old F14 kernel was responsible. For some reason, I didn't get a fc15 kernel > via anaconda but after a 'yum upgrade' later on the luks passphrase nightmare > disappeared. > > I'd like to know what could be the reason for that. I'm worried I'll have the > same problem with custom kernels.. I tried with the F15 as well as F15 (.39) kernels, both exhibit this bug. Anything else you did that could have worked around this issue?
Amit, I'm sorry but I don't recall what else I did that could have made it work :( I had several problems after the upgrade. Some were related to broken (or not upgraded) packages, and although I first blamed systemd for many problems, in retrospective I'm not so sure about it any more. At some point bootup and login worked. But I do remember well the curious behaviour that I had to enter characters several times "to get a star" to display. For a long passphrase, this was really cumbersome! It appeared to be hanging at random and not only in graphical/plymouth boot, I think. Have you checked failed systemd services? I think I disabled akmods and something else I don't remember now.
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