From owner-freebsd-current Thu Jan 21 12:08:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21213 for freebsd-current-outgoing; Thu, 21 Jan 1999 12:08:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21207 for ; Thu, 21 Jan 1999 12:08:08 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA84520; Thu, 21 Jan 1999 13:07:53 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901212007.NAA84520@panzer.plutotech.com> Subject: Re: SCSI errors from IBM Netfinity 3500 In-Reply-To: <36A7724F.E283588A@MexComUSA.net> from Edwin Culp at "Jan 21, 99 10:30:39 am" To: eculp@MexComUSA.net (Edwin Culp) Date: Thu, 21 Jan 1999 13:07:53 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote... > I'm getting a lot of these SCSI disk errors from Current as of Sunday > with the onboard Adaptec Controler with an IBM netfinity 3500. Can > someone tell me if I should worry and/or what they mean? > > Thanks, > > ed > > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0x88 > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x4f > SCSIRATE == 0x88 > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10f > SCSIRATE == 0x88 > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0x88 You have a cabling or termination problem. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message