boot disk swapping
Roger Davis
for a day, so hopefully someone here can give me the right answer.
I have two Indigo2 R10000 systems running 6.5.9m -- one has Extreme
graphics, the other High Impact. The Extreme died over the weekend,
and I need to get it back up ASAP (or rather, the material on its
boot disk, which is still OK). I want to stick the boot disk from
the Extreme into the High Impact and boot up the latter with the
identity of the former. This works fine except that the display of
the system locks up very quickly during the boot sequence. The system
does finish booting, however, and I can remotely log in. All I need
to do is replace the graphics drivers (or whatever) in the kernel
to get my display working again.
SGI told me to run inst with the 6.5 Foundation CDs and the 6.5.9
overlay CDs, doing the following:
set neweroverride on
keep *
install eoe.sw.base
install eoe.sw.gfx
install x_eoe*
This is *not* working -- all of the stuff reloads, autoconfig runs,
and the system reboots exactly as before, i.e., with a display frozen
with the 'Restarting system ... / Welcome to Indigo2 ...' messages.
What's wrong with my picture?
One SGI engineer thought I needed to load some special Impact software,
but I did not have to do this when I originally installed the High Impact
system, and that works just fine. The impactvideo, impactdm and impactcomp
packages he said I need are *not* installed on my working High Impact
system. These packages do exist on one of the 6.5.9 overlay CDs in
the unbundled subdirectory, but when I tried to install them just for
grins the installation failed, saying that the base packages required
for these overlays was not present.
I did eventually get my swapped system fully up by copying /unix from
my working High Impact boot disk, but this is not a long-term solution
as I can no longer generate a working kernel.
Any ideas?
--
Roger Davis
University of Hawaii/SOEST
r...@NoSpamHere.soest.hawaii.edu
Ralf Beyer
>
> I have two Indigo2 R10000 systems running 6.5.9m -- one has Extreme
> graphics, the other High Impact. The Extreme died over the weekend,
> and I need to get it back up ASAP (or rather, the material on its
> boot disk, which is still OK). I want to stick the boot disk from
> the Extreme into the High Impact and boot up the latter with the
> identity of the former. This works fine except that the display of
> the system locks up very quickly during the boot sequence. The system
> does finish booting, however, and I can remotely log in. All I need
> to do is replace the graphics drivers (or whatever) in the kernel
> to get my display working again.
What about mounting the Extreme disk in the High Impact
rather than booting from it?
Wouldn't this be sufficient?
Regards
Ralf Beyer
--
beyer.bra...@freenet.de
Scott Henry
R> OK, I've stumped SGI tech support (and beat my own head against the wall)
R> for a day, so hopefully someone here can give me the right answer.
...
R> SGI told me to run inst with the 6.5 Foundation CDs and the 6.5.9
R> overlay CDs, doing the following:
R> set neweroverride on
R> keep *
R> install eoe.sw.base
R> install eoe.sw.gfx
R> install x_eoe*
Try
install stale
instead.
--
Scott Henry <sco...@sgi.com> / Help! My disclaimer is missing!
IRIX/Linux MTS, / http://reality.sgi.com/scotth/
Silicon Graphics, Inc / SGI-One step ahead
Roger Davis
What you
>SHOULD have done was KEEP the Impact system's boot drive just the way
it was
>and install the other systems drive as another drive, a secondary
drive, a
>data drive. After booting the Impact with its original drive, mount
the other
>systems drive as new partitions. There was and is no reason to make
this
>problem harder than need be. If all you wanted to do was get files off
the
>other systems drive, you do not need to run a system off that drive.
Give up
>on trying to boot from the other systems drive before you make more of
a mess
>of things.
My Impact system has been disconnected from our LAN for an extensive
period
of time. Adopting your solution would require a few hours of
reconfiguring it
for reattachment to our LAN and installing all of the latest security
patches, plus
getting it blessed by our local network security staff. Besides which,
I'd prefer
not to reconfigure the automounter on a half-dozen other systems to look
for my
data on a different host -- the data I need are not actually on the boot
disk itself,
but rather on a set of external drives. It seemed far easier to run
inst to load a missing graphics driver -- this should have been a
20-minute
procedure. If these were two otherwise-identical Sun systems with
different
graphics cards this would be a complete non-issue, but I digress.
Jerry suggested:
>It sounds like you are trying to do the installation in two steps (e.g.
6.5
>then 6.5.9). Don't do it that way. Instead, put the 6.5.9 disks in,
then open
>all (this really means ALL) the 6.5 base disks.
Sorry if I was a little vague on this, but that's exactly what I did.
During a single
inst session I opened the 6.5 base Foundation disks (plus a few others
recommended
by SGI tech support) and all of the 6.5.9 overlays. The install
extracted stuff only
from Foundation 1 and I believe one of the overlays, IIRC.
Anybody else have any ideas?
------------
Roger Davis
r...@NoSpamHere.soest.hawaii.edu