From owner-freebsd-scsi Sat Dec 28 07:53:01 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA15725 for freebsd-scsi-outgoing; Sat, 28 Dec 1996 07:53:01 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id HAA15717 for ; Sat, 28 Dec 1996 07:52:53 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id QAA23542; Sat, 28 Dec 1996 16:52:26 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id QAA03720; Sat, 28 Dec 1996 16:52:01 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id QAA12624; Sat, 28 Dec 1996 16:39:25 +0100 (MET) From: J Wunsch Message-Id: <199612281539.QAA12624@uriah.heep.sax.de> Subject: Re: Q: scsi parity error? To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Date: Sat, 28 Dec 1996 16:39:25 +0100 (MET) Cc: ping@stepnet.com (Ping Mai) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612280405.UAA01359@red.stepnet.com> from Ping Mai at "Dec 27, 96 08:05:39 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Ping Mai wrote: > exact error message: > > sd0(ahc0:0:0): ABORTED COMMAND info:c53a0 asc:47,0 SCSI parity error, retires:1 > > i like to know if this is a problem with the drive hw, or am i doing > something wrong. if it's a drive problem i need to return it to quantum asap. It's usually a problem with the drives. I used to have a similar problem with an older Seagate drive, but only after replacing my old mainboard with its BusLogic Bt742A EISA controller with an NCR 53c810. I finally gave up fighting against it, and simply didn't log the first error. (The first retry did always succeed, so other than a slightly reduced throughput, there was no ill side-effect from this.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)