From owner-freebsd-stable Thu Mar 2 8:41: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from morpheus.skynet.be (morpheus.skynet.be [195.238.2.39]) by hub.freebsd.org (Postfix) with ESMTP id 2F1DE37BD0E for ; Thu, 2 Mar 2000 08:40:58 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by morpheus.skynet.be (Postfix) with ESMTP id 03979CF17; Thu, 2 Mar 2000 17:40:43 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <14526.37497.981697.452892@onceler.kcilink.com> References: <14526.37497.981697.452892@onceler.kcilink.com> Date: Thu, 2 Mar 2000 17:22:51 +0100 To: Vivek Khera From: Brad Knowles Subject: Re: Crash on boot when disks are present? Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:10 AM -0500 2000/3/2, Vivek Khera wrote: > There are anecdotal reports of other external SCSI drives causing such > errors at boot on BSD/OS as well. The solution is to power up with > the drive off, and turn it on once the boot is started, or something > silly like that. But why is it a problem now, when it wasn't a problem earlier this week? Could a simple firmware upgrade of the controller on the drive array really cause problems that severe? > I think it has to do with having both internal and > external drives on the same controller, but I'm not sure. This is not what I have. I have two Adaptec 2940U2W controllers that are dedicated to this drive array, and the internal drive is on a separate controller (the built-in AIC-7890). -- These are my opinions and should not be taken as official Skynet policy ========================================================================= Brad Knowles, Sys. Arch., Mail/News/FTP/Proxy Admin Note: No Microsoft programs were used in the creation or distribution of this message. If you are using a Microsoft program to view this message, be forewarned that I am not responsible for any harm you may encounter as a result. See for details. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message