Bug 505518

Very much related:
Also see https://bugzilla.redhat.com/show_bug.cgi?id=501198 where the F10 installer creates a crypttab entry for the whole disk (except /boot) that is incompatible with what F11 ramdisks expect.

F10 was the original Fedora installed.
I got a line like:
luks-4a65c764-b0b1-4b1f-94fb-c76d1bc3e287
UUID=4a65c764-b0b1-4b1f-94fb-c76d1bc3e287 none

but the luks-bla phrase is wrong for F11 and prevents decryption from working.

Created attachment 349237 [details]
after entering the passphrase for my /home part

I have the same problem. Thought some logs might help.

Workaround is to temporarily change swap back to unencrypted.
(swapoff /dev/mapper/bla; mkswap /dev/bla; vi /etc/crypptab; vi /etc/fstab; reboot)

Hmmm.
Fedora 12 did not complain about swap in the FEW situations that I could use the CD/DVD.

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 WONTFIX if it remains open with a Fedora 
'version' of '11'.

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 prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Nothign was done so we up the version.

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 WONTFIX if it remains open with a Fedora 
'version' of '12'.

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 prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Nothign was done so we up the version.
And why close a ticket that is against rawhide?
Bugzapper says F12...

*** Bug 788236 has been marked as a duplicate of this bug. ***

Copying over my workaround from Bug 788236.

creating a keyfile (for example in /etc/luks/), adding it to the
volume, and then changing "none" to this path+filename in /etc/crypttab appears to work. On
boot, my root volume is unlocked, then the keyfile stored in /etc is used to
unlock the swap volume, which is then mounted.

Setting this up on installation is something that could be automated by
Anaconda.

The suspend/resume on this hardware is a bit buggy, so I can't thoroughly test
it's function with this.

Indeed I cannot suspend to disk using this. After it writes for about 10-15 seconds the console spews with IO errors writing to a block, with the block number incrementing.

I cannot reproduce read/write errors on this hardware outside of this instance.

I have no idea if this is the encryption at fault, or some other problem.

*** Bug 1254064 has been marked as a duplicate of this bug. ***

Any updates? Progress? Patches?

This is not a high-priority item for us, but patches are certainly welcome. Keep in mind that if you want support for this at installation time it will require patches to blivet, pykickstart, and anaconda.