From owner-freebsd-questions Tue Aug 6 21:24:36 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA06333 for questions-outgoing; Tue, 6 Aug 1996 21:24:36 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts12-line16.uoregon.edu [128.223.150.148]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA06324 for ; Tue, 6 Aug 1996 21:24:33 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id VAA00246; Tue, 6 Aug 1996 21:24:22 -0700 (PDT) Date: Tue, 6 Aug 1996 21:24:22 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: "James E. Leinweber" cc: questions@freebsd.org Subject: Re: 2.1.5-RELEASE generic kernel panics looking for mythical sd1a root In-Reply-To: <199608061643.LAA21108@stovall.slh.wisc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 6 Aug 1996, James E. Leinweber wrote: > Bravo! The kernel duely informed me that the syntax to force it to use the BIOS > device 1 (i.e, the SCSI disk in a two disk IDE + SCSI computer) is: > > 1:sd(0,a)kernel > > And this works. Thanks very much for the quick and helpful response. Thankfully, that syntax works 99.99% of the time. There is some problem with the guessing the boot blocks do to figure out where your FreeBSD slice is. My guess is, since your configuration is rather, er, extended, that the boot blocks don't have enough logic to make it through the maze. The unfortunate part is that you're stuck forever typing that in to Boot: until you move your disks around. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major