Red Hat Bugzilla – Bug 496363
anaconda refuses to mount encrypted file systems
Last modified: 2009-05-19 16:20:49 EDT
Description of problem:
During clean install of rawhide 20090417 using custom partitioning, specified that some encryted LVs be mounted on /mnt/...., but during first boot passwords were not prompted, LVs not mounted and directories in /mnt did not exist
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot.iso, askmethod
2. select custom partitioning
3. edit encrypted LVs requesting mount on /mnt/...
Looked good, but on first boot and subsequent, they were mot mounted, nor did directories exist in /mnt
mounted encrypted partitions (LVs)
In 126.96.36.199, you must first custom mount another LV in a VG, then custom mount the encrypted LV, otherwise anaconda ignores the mount point you specify. This may have been the case in .45, I didn't think to revisit a VG with that version.
I think I'm experiencing the same bug, (rawhide 20090420) though through a slightly different method. I had a working installation on a test machine where the VG on /dev/sda2 was encrypted, and I had created another encrypted ext4 partition directly at /dev/sda3 which was mounted as /home. Then I reinstalled...
I was able to remount everything except the encrypted ext4 partition on /dev/sda3. This was the only partition/volume that I chose not to format, since I wouldn't be formatting that partition if it were a system I used every day.
I later tried recreating this scenario without any encrypted partitions. Without encryption, /dev/sda3 mounted to /home with no problem.
pre-existing encrypted partitions still not mountable in anaconda 188.8.131.52 unless you first edit another LV in the VG.
You still must edit an encrypted file system two times in a row to get anaconda to record the mount point. .48 version.
Still a problem in version .50. Also, 499828 may have some relationship.
(In reply to comment #3)
> pre-existing encrypted partitions still not mountable in anaconda 184.108.40.206
> unless you first edit another LV in the VG.
Have you seen this with partitions also or only with LVs?
Not with non-encypted partitions, I only have encrypted LVs. Give me a couple hours and I'll build a test case.
Don't spend the time unless you want to -- encrypted partitions have been addressed already and should work just fine. It was your use of the word "partitions" in comment #3 that made me wonder if you were seeing it with partitions or just using terms loosely.
Didn't see #9 in time, so went ahead and built the test caser and encrypted partitions edit the first time.
I will be more careful about describing "partitions" and "LVs." Thanks for pointing this out.
Fix will be in anaconda-220.127.116.11-1. Thanks for the report.
with anaconda .52, the mount point stays in the dialogue after hitting ok, but then after hitting the next ok to go back to the custom partitioning screen, traceback: "luks object has no attribute." Auto bz said 499828 had already been submitted, traceback is there.
Working in .53. Closing.