Bug 1080

Summary:	SILO installs on [possibly] wrong drive.
Product:	[Retired] Red Hat Linux	Reporter:	Peter Jones <pjones>
Component:	silo	Assignee:	Jeff Johnson <jbj>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.2	CC:	pbrown
Target Milestone:	---
Target Release:	---
Hardware:	sparc
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-04-09 22:55:29 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 Peter Jones 1999-02-08 18:43:36 UTC

Earlier sparcs remap SCSI IDs 0 and 3 in OpenBOOT.  Linux
ignores this.  SILO then proceeds to install on the lowest
SCSI ID.  If you have a drive on 0 and 3, SILO will install
on 0, the sparc will try to boot off of ID 3.

Comment 1 Preston Brown 1999-03-29 21:48:59 UTC

Jeff, is this an installer issue (i.e. parameters written to the SILO
config file) or a silo issue itself?

Comment 2 Jeff Johnson 1999-04-09 22:55:59 UTC

Fixing this problem in silo would require knowing all the
Sun OBP versions in order to take appropriate corrective
measures. It's easier just to fix this problem in the
documentation by saying that on older suns's, you should make
sure that that unit numbers are the same as the target ID's by
setting the appropriate OpenPROM variable before using silo.