[8164] in linux-scsi channel archive
Re: recovery behaviour with 1 bad + 1 good drive (aic7xxx)
daemon@ATHENA.MIT.EDU (Dan Jones)
Tue Feb 22 20:17:20 2000
Message-ID: <38B2F87D.5AAB6C3B@valinux.com>
Date: Tue, 22 Feb 2000 12:58:37 -0800
From: Dan Jones <djones@valinux.com>
MIME-Version: 1.0
To: Ricky Beam <jfbeam@bluetopia.net>
Cc: linux-scsi@vger.rutgers.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Ricky Beam wrote:
>
>
> This depends on the firmware of the controller.
>
> In my case, it would appear something as simple as a SCSI bus parity error
> can crash a Mylex RAID controller. I don't know why the hell they won't
> listen to me when I tell them it's crashing -- I even sent them the i960's
> console data from boot to crash. (I sent the board for repair. Two months
> later, I get it back with a new RTC battery on it !?!? That, of course,
> didn't fix a damned thing -- it crashed 17 min. after I put it back in the
> system. Needless to say, this REALLY pisses me off.)
>
No comment on how responsive Mylex is, but I wouldn't depend upon
RAID to protect me on a system that gets SCSI parity errors. It
isn't designed for that. SCSI parity errors are natures way of
indicating that something needs to be corrected in your storage
configuration. Of course, finding exactly what is wrong can be
a trial i.e cable, connector, termination, loading, etc. Until
SCSI3 is completely implemented, the basic assumption is that
transfers on the SCSI bus must be error free.
--
Dan Jones, Storage Engineer VA Linux Systems
V:(408)542-5737 F:(408)745-9130 1382 Bordeaux Drive
djones@valinux.com Sunnyvale, CA 94089
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
