[rescue] Installing Solaris 8 on SS20
rescue at sunhelp.org
Tue Jul 24 16:13:15 CDT 2001
I always fumble around with this stuff myself, but here is what I think
1) Your boot partition is maybe too big - 2 Gig is about the limit (IIRC)
2) Your new drive needs a label - you need to boot off CD-ROM, open a
session (right click on desktop after install is up) and then run the
format. Select your drive, label it, and then write the label and exit.
3) Once labeled, the install should go fine...
4) The boot image needs to be in the first 2 Gig on the drive (IIRC).
That should get you going... If you are still stuck, don't hesitate to
write back to the list!
Ket us know how it ends up,
s at avoidant.org wrote:
> Hello all,
> I picked up an 18G SCA drive from http://www.softwareandstuff.com
> (thanks to whoever pointed it out) and while waiting for it to arrive, I
> reinstalled Solaris on the 9G I had in there before, figuring to use the
> 18G as /home (or /export/home as it may be).
> Well, the install went fine. i let the installer pick slice sizes,
> though I admit I changed /export/home (made it smaller since it wouldn't
> be used as such after the 18G was installed).
> So, old Sun (Toshiba) cd-roms being what they are, the install took
> forever and a half, and it was finished when I got home from work today
> (with 18G in hand). Reboot to finish, and it tells me
> bootblk: can't find the boot program
> Program terminated
> Type help for more information
> <#0> ok
> Is this because the bood slice (/) is too large? That's all I can think
> of. If so, why didn't the installer make it smaller? Or complain like
> Linux does if you make the bood partition too big? Is this some sort of
> sick joke on the part of the Sun engineersw, or am i missing something?
> Also, figuring I'd have to reinstall anyway, i stuck the 18G in and
> "boot cdrom", and it tells me "corrupt label - wrong magic number". I
> assume this is because it's a new disk, with no Sun disk label. Will
> install take care of that, or do I take it out and put it back when the
> (re-)install is done?
More information about the rescue