Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 150238

Summary:	Anaconda Ignores Device directives in kickstart file
Product:	Red Hat Enterprise Linux 3	Reporter:	Ron Reed <rreed>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED CANTFIX	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	clumens
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:	2005-09-21 21:16:07 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 Ron Reed 2005-03-03 21:38:20 UTC

+++ This bug was initially created as a clone of Bug #147687 +++

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107
Firefox/1.0

Description of problem:
I have some PowerEdge 2550 servers. These servers have both the internal
PERC 3Di raid and a PERC 3Dc card in them.

I am working on creating a Kickstart CD and I have a problem with the
order of how the raid devices are installed. The PERC 3Dc (megaraid) is
found first and gets set-up as /dev/sda, the PERC 3Di (aacraid) get
detected second and gets set-up as /dev/sdb. I need to get the 3Di to be
/dev/sda during the install.

Version-Release number of selected component (if applicable):
anaconda-9.1.4.1-1.RHEL

How reproducible:
Always

Steps to Reproduce:
1. Boot the bootdisk.img from a standard RHE3.0-WS CD
2. At the boot: prompt type vmlinuz initrd=initrd.img ks=cdrom:/ks.cfg

  

Actual Results:  The install will start, but the megaraid device is setup as
/dev/sda and the aacraid device is setup as /dev/sdb

Expected Results:  The device parameter in the ks.cfg file should have set the
aacraid device as scsihost0 and allowed the kernel to set it up as /dev/sda.

Additional info:

Comment 1 Chris Lumens 2005-03-11 16:24:57 UTC

Marking as NEEDINFO based on comments to anaconda-devel-list.  Will post a link
to the relevant archives later so we can keep this all in sync.

Comment 2 Jeremy Katz 2005-09-21 21:16:07 UTC

Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product.  If you have further details, feel free to
reopen the report with the additional details attached.