From owner-freebsd-stable Thu Mar 2 8:10:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id E7A8637BFFB for ; Thu, 2 Mar 2000 08:10:37 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 100F1E8B0; Thu, 2 Mar 2000 11:10:34 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id LAA09841; Thu, 2 Mar 2000 11:10:34 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14526.37497.981697.452892@onceler.kcilink.com> Date: Thu, 2 Mar 2000 11:10:33 -0500 (EST) To: Brad Knowles Cc: freebsd-stable@freebsd.org Subject: Re: Crash on boot when disks are present? In-Reply-To: References: X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. I think it has to do with having both internal and external drives on the same controller, but I'm not sure. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message