Red Hat Bugzilla – Bug 459430
anaconda does not write ks disk encryption options to anaconda-ks.cfg
Last modified: 2008-08-19 13:05:31 EDT
Description of problem:
--install was done as a virt-guest--
Install Fedora 9 using disk encryption.
Default lvm disk partition used.
System gets encrypted successfully.
Looking at anaconda-ks.cfg after install
authconfig --enableshadow --passalgo=sha512
timezone --utc America/New_York
bootloader --location=mbr --driveorder=xvda --append="console=hvc0 rhgb quiet"
# The following is the partition information you requested
# Note that any partitions you deleted are not expressed
# here so unless you clear all partitions first, this is
# not guaranteed to work
#clearpart --linux --drives=xvda
#part /boot --fstype ext3 --size=200 --ondisk=xvda
#part pv.2 --size=0 --grow --ondisk=xvda
#volgroup VolGroup00 --pesize=32768 pv.2
#logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=512 --grow --maxsize=1024
#logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow
according to the docs, you should see a line like
autopart --encrypted --passphrase=<password>
This should be fixed in recent rawhide as well as the F10 Alpha. Can you verify that it is fixed in these newer releases?
I tried f10 Alpha, it failed to boot after putting in the encryption passwd.
I ran the test as a virt guest of rhel 5.2. I'll get some more details tomorrow.
ok.. testing f10 alpha on a physical box.. w/ disk encryption.
partition layout, cleared all lvm's
/ remaining drive , encrypted
fails to boot
Mount failed for selinux on /selinux: No such file or directory
switchroot: mount failed: No such file or directory
Yes, there are some problems with plymouth that prevent the system from booting. Apparently I forgot about them when recommending that you try the Alpha.
I have verified that this is indeed broken in the Alpha and am in the process of verifying a fix that will be included in the F10 Beta.
Fix will be in anaconda-22.214.171.124-1.