From owner-freebsd-scsi Mon Jun 22 16:23:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19830 for freebsd-scsi-outgoing; Mon, 22 Jun 1998 16:23:50 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org ([209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA19795 for ; Mon, 22 Jun 1998 16:23:36 -0700 (PDT) (envelope-from shimon@nomis.Simon-Shapiro.ORG) Received: (qmail 3757 invoked by uid 1000); 22 Jun 1998 23:24:18 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 22 Jun 1998 19:24:18 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: RE: DPT support binaries - How to Setup Cc: freebsd-SCSI@FreeBSD.ORG, Chris Parry , alex@nac.net Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 22-Jun-98 Tom wrote: > > On Sun, 21 Jun 1998 alex@nac.net wrote: > >> Search the archives; there are about 10 instances of this in the past 2 >> months. > > I've been on freebsd-scsi list a long time. The only instance was your > system as I recall. > >> It is when the array is in degraded mode, and you try to boot. > > No. Done that here several times. > > However, you can't boot if the array is dead (RAID5 with two failed > drives) but that goes without saying. I've seen an interesting scenario > where a rebuild caused a marginal drive to fail, so you always want to > try > at least two simulated failures before bringing a new server online. About 2 out of 5 builds failed with firmware 7M0. The same hardware later revealed a bad disk shelf (one of the busses alarms continually). We moved the disks to another bay (SE rather than Differential) and controller, and the failure re-occured. This time changing a damaged cable cured it. I think you are right about the build process exposing weaknesses in the drives. I also think there is some sensitivity in the firmware. I have traced and verified the driver and am of the opinion that it is not FreeBSD (or driver) related. To change my mind, provide me with a core dump, and/or a trace that shows the nature of the crash. Otherwise, I'll quote my bootcamp seargant; ``talk is cheap''. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message