Bug 1080 - SILO installs on [possibly] wrong drive.
SILO installs on [possibly] wrong drive.
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: silo (Show other bugs)
5.2
sparc Linux
high Severity medium
: ---
: ---
Assigned To: Jeff Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-02-08 13:43 EST by Peter Jones
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-04-09 18:55:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Peter Jones 1999-02-08 13:43:36 EST
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 16:48:59 EST
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 18:55:59 EDT
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.

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