From owner-freebsd-current Tue Jan 5 08:08:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00870 for freebsd-current-outgoing; Tue, 5 Jan 1999 08:08:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00863 for ; Tue, 5 Jan 1999 08:08:35 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id LAA49720; Tue, 5 Jan 1999 11:12:16 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 5 Jan 1999 11:12:16 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Blaz Zupan cc: freebsd-current@FreeBSD.ORG Subject: Re: Kernel cannot mount root with new bootblocks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 Jan 1999, Blaz Zupan wrote: > Here is my setup. I have two SCSI disks connected to an Adaptec 2940, the > first is a Quantum 540MB (SCSI ID 0), containing Windows 95, the second > is a NEC 1.5GB (SCSI ID 1) containing FreeBSD: [snip] > This is -current as of yesterday, with the latest boot code (installed > with "disklabel -B da1" and empty /boot/boot.conf). FreeBSD disk was > originally installed dangerously dedicated. > > Suggestions on how to fix this will be much appreciated. If someone else doesn't have a better solution you can try wiring the scsi devices down, look in LINT for this, a really bad hack is defining the: "kernel on XXX" line. good luck, -Alfred > Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz > Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message