Bug 427351

Summary:	bootloader will not install onto raid device, if other volumes present in system
Product:	Red Hat Enterprise Linux 5	Reporter:	Adam Cetnerowski <adam.cetnerowski>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	low
Version:	5.3	CC:	agk, dwysocha, heinzm, krzysztof.wojcik, mbroz, prockai
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-05 15:23:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Cetnerowski 2008-01-03 12:32:46 UTC

During installation, if /dev/mapper/isw_* is selected as the device for
bootloader, the bootloader will be installed on the first non-raid volume instead. 

This problem does not occur, if the raid volume is the only device.

Comment 1 Milan Broz 2008-01-04 12:53:01 UTC

I think that bootloader cannot be installed on dmraid device (you need first
boot ramdisk to run dmraid and create device in /dev/mapper; installer probably
should not allow selecting this device).

Anyway, this is installation issue, reassigning to anaconda.

Comment 2 Krzysztof Wojcik 2009-01-05 09:04:26 UTC

This is very old bug. 
In current version there is no reproduce.
My suggestion is to close it.