Bug 438367 - Reusing encrypted partitions in a new install is broken.
Reusing encrypted partitions in a new install is broken.
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: David Lehman
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-03-20 12:31 EDT by Bruno Wolff III
Modified: 2008-04-04 11:54 EDT (History)
0 users

See Also:
Fixed In Version: anaconda-
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-04 11:54:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bruno Wolff III 2008-03-20 12:31:45 EDT
Description of problem:
While doing a reinstall of rawhide I wanted to save a little time by reusing the
raid definitions I had used previously. They originally showed up as type
foreign. I went in to specify that they should be reformatted as ext3 and
specified encryption and specified a mount point. At this point things looked OK
in that menu. However when I close it the device still showed as being type
foreign (rather than ext3) and there was no lock. When I went back to check it
with the edit function the mount point information had been removed.
The raid away with encrypted swap seemed to work correctly.
I expect to be able to work around this easily, and I doubt it will affect many
(any?) people trying to use the beta, so there probably isn't a rush to do this.
I didn't have any encryption on normal devices, so I don't know if raid is
really needed to trigger this.

Version-Release number of selected component (if applicable):
anaconda- on an x86_64 system.

How reproducible:
I don't know as this is the first reinstall which I tried to do reusing existing
encrypted file systems.

Steps to Reproduce:
1.Install fedora using encrypted file systems (and possibly raid 1).
2.Redo the install using a custom layout and try to reuse an encrypted partition
in the new install.
Actual results:
Mount point information is lost before I can proceed to the next step of the

Expected results:
That I be able to move on to the next step of the install.

Additional info:
Comment 1 Jeremy Katz 2008-03-20 12:42:36 EDT
Dave is looking at this and depending on how the patch looks, we're going to
make the call of whether to put it in or to put off this support until F10
Comment 2 Bruno Wolff III 2008-03-20 12:54:42 EDT
OK. The work around was pretty simple, so it may not be worth risking something
that might break things at this point. I just deleted the raid arrays and
recreated them. Doing this one at a time made it so I didn't even have to do
much picking. The install is proceeding now, and I expect it to work. (I am up
to the starting install process. This may take several minutes... prompt.)
Comment 3 David Lehman 2008-04-04 11:54:39 EDT
As of anaconda- you can reuse preexisting LUKS partitions, RAID
devices, and logical volumes, provided you enter the correct passphrase when
prompted (prompting occurs immediately prior to the partitioning screens, after
root password screen).

Encrypted RAID member devices do not work at this time, but a fix is in the works.

Note You need to log in before you can comment on or make changes to this bug.