Bug 432009 - More than one encrypted partition during install crashes before finish
Summary: More than one encrypted partition during install crashes before finish
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-08 12:56 UTC by Mauricio Teixeira
Modified: 2008-02-20 16:15 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-20 16:15:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
grubyDiskName error in the console (27.79 KB, image/png)
2008-02-08 12:56 UTC, Mauricio Teixeira
no flags Details

Description Mauricio Teixeira 2008-02-08 12:56:52 UTC
I tried installing Fedora 9 Alpha from the publicly provided DVD. The
installation went fine with the default partitioning. Then I tried a new
partition scheme with various partitions and only /home encrypted, that worked
fine too.

When I tried a new partition scheme, having swap, root and home encrypted, I got
the error in the screen shot attached.

The error occurs at the end of installation, while "Installing bootloader".

Sorry if I could not copy the full bug report on the GTK window, but the test
install was run inside a VirtualBox machine, and I could not find a way to copy,
so I had to screen shot the tty.

Comment 1 Mauricio Teixeira 2008-02-08 12:56:52 UTC
Created attachment 294349 [details]
grubyDiskName error in the console

Comment 2 Mauricio Teixeira 2008-02-08 12:58:53 UTC
An addition, here is the full partition scheme:

/dev/sda1 = /boot 100MB
/dev/sda2 = / 5G
/dev/sda3 = swap 1G
/dev/sda5 = /home 2G

Comment 3 David Lehman 2008-02-20 16:15:37 UTC
The problem is triggered by the use of an encrypted regular partition for the
root filesystem.

This should be fixed in rawhide once booty is rebuilt.


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