Bug 755249 - Installation to LVM-on-RAID with uninitialized disk fails bootloader install
Summary: Installation to LVM-on-RAID with uninitialized disk fails bootloader install
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-20 01:55 UTC by Jon Masters
Modified: 2013-02-13 08:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 08:40:32 UTC
Type: ---


Attachments (Terms of Use)

Description Jon Masters 2011-11-20 01:55:06 UTC
Description of problem:

Unless one first loads a partitioner manually and initializes a new disk, any attempt to use a "custom" disk layout (LVM-on-RAID typical RHEL-like workstation configuration) fails with an error about not having chosen a target device for the bootloader installation. Going back during disk partitioning after specifying LVM and RAID options causes the installer to backtrace. After several attempts, and manual partitioning, I was able to get the installation to succeed.

Comment 2 Chris Lumens 2011-11-23 03:44:04 UTC
Log files?

Comment 3 Fedora End Of Life 2013-01-16 10:12:05 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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


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