[SunRescue] (no subject)

[Ken Hansen]

IIRC, the reason has to do withthe first batch of drives sun sealed inside the workstation on the assembly line - they had *no* jumpers installed,and when the first systems were tested with the final software release, the *problem* was found.

It is retained for historical purposes, but the short version is, as above, IIRC.

I may be off, but I don't think I am too far off.

boot disk maps to the default boot drive, disk3, which is *typically* mapped to the drive with SCSI ID #0.

Boot disk0 maps to the physical drive with the SCSI ID #3.

boot disk1 maps to the drive with SCSI ID #1.

boot disk2 maps to the drive with SCSI ID #2, etc.

Now, Linux, on the other hand, refers to drives by number, so if you have a drive with SCSI ID #0, then add a drive with a SCSI ID of #1, your system will not boot - because Linux numbers them from lowest to highest. What used to be sda (SCSI ID #0, viewed as #3 by Linux), becomes sdb, when a lower SCSI ID drive is added (SCSI ID #1 is *lower* than SCSI ID #0 ;^)...

See, Solaris is better! ;^)

Ken

-----Original Message-----
To: "'rescue at sunhelp.org'" <rescue at sunhelp.org>
Subject: RE: [SunRescue] boot prom value for booting from drive id=0 on SS5
Date: Mon, 21 May 2001 10:42:23 -0400
Reply-To: rescue at sunhelp.org

Bob--
It depends on what aliases are set in the
EEPROM.  To check those, you can use the
devalias command at the OpenBoot PROM prompt.

Usually, to boot disk 0, one or more of
the following should work:
  boot disk
  boot disk0
  boot disk3

The last one is because ID=3 is "disk 0" on
many Suns due to...well some reason lost in
the dawn of time.