Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Mar 2000 18:50:19 +0100
From:      Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
To:        Brad Knowles <blk@skynet.be>
Cc:        Vivek Khera <khera@kciLink.com>, freebsd-stable@FreeBSD.ORG
Subject:   Re: Crash on boot when disks are present?
Message-ID:  <20000302185019.B20215@internal>
In-Reply-To: <v04220810b4e44582339c@[195.238.1.121]>; from blk@skynet.be on Thu, Mar 02, 2000 at 05:22:51PM %2B0100
References:  <v0422080bb4e401fc570d@[195.238.1.121]> <14526.37497.981697.452892@onceler.kcilink.com> <v04220810b4e44582339c@[195.238.1.121]>

next in thread | previous in thread | raw e-mail | index | archive | help
[Don't remeber if my other reply went to Brad also or only to
the list... ]

On Thu, 02-Mar-2000 at 17:22:51 +0100, Brad Knowles wrote:
> 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?

Yes. See PR #16803.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000302185019.B20215>