Alternate boot disk

Jeremy Higdon jeremy at perf2.asd.sgi.com
Tue Nov 27 08:17:01 AEST 1990


In article <FDADCBB0233F000A20 at NRCNET.NRC.CA>, SERRER at NRCM3.NRC.CA (Martin Serrer) writes:
>  I just received a new disk (380 MByte) for my 4D50/GT and would like to install
> the newest version of unix on this disk leaving the old disk (170 MByte) intact.
>  The 170 was configured as SCSI id=1.
>  I would like to configure things now so that the 380 is id=1 and the 170 as
> id=2 and have the ability to boot from either disk.
>  So off I went moving SCSI id jumpers and changing the PROM 'bootfile' and
> 'root' env variables. but when I try to boot the 170 at its new address I get a
> message...
>   mount: giving up on:
>      /usr
>   followed by all the nasties one would expect if /usr wasn't available.

Perhaps /dev/usr is still linked to /dev/dsk/dks0d1s6.  The easiest thing
would probably be to boot disk 2 single user, cd /dev, ./MAKEDEV disklinks



More information about the Comp.sys.sgi mailing list