Bug 61032

Summary:	Boot controller order not propely detected.
Product:	[Retired] Red Hat Linux	Reporter:	Issue Tracker <tao>
Component:	anaconda	Assignee:	Michael Fulbright <msf>
Status:	CLOSED DUPLICATE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	dcm
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-03-12 15:08:54 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 Issue Tracker 2002-03-12 15:08:12 UTC

Description of Problem:

At the Boot Loader Configuration screen the boot order shown is not correct. Shown: 

/dev/cciss/c0d0 
/dev/cciss/c0d1 
/dev/cciss/c1d0 
/dev/cciss/c1d1 
/dev/ida/c0d0 

Actual controller order in RBSU: 

/dev/ida/c0d0 
/dev/cciss/c0d0 
/dev/cciss/c1d0 

It is not possible to select individual drives to boot from. You can only select
the order of the controllers. 

System: DL760 
Mem: 5GB 

Also, the locations for installing the bootloader are: 

/dev/cciss/c0d0 master boot recoord 
or 
/dev/ida/c0d0 first sector of first partition

Comment 1 Jeremy Katz 2002-03-13 19:54:31 UTC

As I've told Compaq at least three times now for Advanced Server...

This is because the x86 does not export information on device ordering in a
consistent fashion that works on all hardware.  Will be fixed in the next major
revision of Red Hat Linux, but the changes are extremely intrusive, and thus not
being backported for Advanced Server

*** This bug has been marked as a duplicate of 59434 ***