Path: utzoo!attcan!uunet!bu.edu!rpi!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!rice!rice!sun-spots-request
From: poffen@sj.ate.slb.com (Russ Poffenberger)
Newsgroups: comp.sys.sun
Subject: Re: SCSI disk and installboot problems...
Keywords: Hardware
Message-ID: <1990Oct7.220129.23501@rice.edu>
Date: 7 Oct 90 21:30:00 GMT
Sender: sun-spots-request@rice.edu
Organization: Sun-Spots
Lines: 24
Approved: Sun-Spots@rice.edu
Originator: spots@walhalla.rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 325, message 4
X-Refs:  Original: v9n278

In article <10169@brazos.Rice.edu> richard@cs.ua.oz.au writes:
>
>In article <10110@brazos.Rice.edu>, jto@ousrvr.oulu.fi (Jarkko
>Oikarinen) writes:
>|>
>|>But making the new disk bootable using
>|>installboot seemed to be impossible; it always flamed back with a message
>|>'not a superblock'. Why is this ?
>|>
>|>The command I used was something like:
>|>'installboot /mnt/boot bootsd /dev/sd4a'
>|>(the root partition of the new disk was mounted to /mnt).

I have had this occur sometimes when the root partition is not mounted as
root.  (eg /mnt). I don't really know why, but one way around it is to
boot off another device initially (tape or NFS) using the -a option (b
-sa), then when it asks the question for root and swap, give the local
disk (sd0a/sd0b). Once booted, then installboot works fine (installboot
-lv /boot bootsd /dev/rsd0a).

Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies       UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110             (408)437-5254