From owner-freebsd-current Wed Mar 15 17:36:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA04410 for current-outgoing; Wed, 15 Mar 1995 17:36:46 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA04402 for ; Wed, 15 Mar 1995 17:36:42 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id UAA02099; Wed, 15 Mar 1995 20:33:30 -0500 From: Peter Dufault Message-Id: <199503160133.UAA02099@hda.com> Subject: Re: Problems with SCSI drive & ncr To: bvickers@bossanova.ICS.UCI.EDU (Brett J. Vickers) Date: Wed, 15 Mar 1995 20:33:30 -0500 (EST) Cc: current@FreeBSD.org In-Reply-To: <9503151121.aa24161@paris.ics.uci.edu> from "Brett J. Vickers" at Mar 15, 95 11:20:34 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 808 Sender: current-owner@FreeBSD.org Precedence: bulk Brett J. Vickers writes: > sd1(ncr0:1:0): ABORTED COMMAND asc:47,0 SCSI parity error fru:2, retries:4 ... >(ncr0:1:0): "SEAGATE ST3390N 9546" is a type 0 fixed SCSI 2 There are a lot of Seagate drives out there complaining about parity errors and specifying a Field Replaceable Unit of 2. I'm looking for ideas (other than Seagate firmware problems) as to why this is happening. There was a posting on comp.periphs.scsi about this and the Sun system was complaining about a "vendor specific" code asc:47 ascq:0, but I looked at the spec and don't see that this can be anything but parity error. If anyone has any ideas holler. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267