From owner-freebsd-questions Tue Nov 14 18:41:58 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ns1.hutchtel.net (ns1.hutchtel.net [206.9.112.100]) by hub.freebsd.org (Postfix) with ESMTP id B075637B4E5 for ; Tue, 14 Nov 2000 18:41:54 -0800 (PST) Received: from mark8 (hutch-320.hutchtel.net [206.10.68.20]) by ns1.hutchtel.net (8.9.1/8.9.0) with SMTP id UAA09741; Tue, 14 Nov 2000 20:41:46 -0600 (CST) Message-ID: <01d901c04ead$e705ce40$0200000a@vladsempire.net> From: "Josh Paetzel" To: "Ben Weaver" , References: <20001113072628.A4463@tranquility.net> Subject: Re: What's up with these SCSI parity errors and aborted commands? Date: Tue, 14 Nov 2000 20:43:55 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Ben Weaver" To: Sent: Monday, November 13, 2000 7:26 AM Subject: What's up with these SCSI parity errors and aborted commands? > The last week or so I've been seeing alot of this in my kernel log messages. The box is running 4.0-RELEASE. Does anyone know what's causing this? I hope it's not my hard drive going south. The fullest slice on the da0 device is only at 86% (there's still 350MB free)... > > > (da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 0 c0 24 bf 0 0 80 0 > > (da0:ahc0:0:0:0): WRITE(06). CDB: a 5 a5 ef 80 0 > > (da0:ahc0:0:0:0): WRITE(06). CDB: a 5 a6 ef 80 0 > > (da0:ahc0:0:0:0): WRITE(06). CDB: a 5 a5 6f 80 0 > > (da0:ahc0:0:0:0): WRITE(06). CDB: a 5 9b 3f 80 0 > > (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 > > (da0:ahc0:0:0:0): SCSI parity error > > (da0:ahc0:0:0:0): WRITE(06). CDB: a 5 9c bf 80 0 > > (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 > > (da0:ahc0:0:0:0): SCSI parity error > > (da0:ahc0:0:0:0): WRITE(06). CDB: a 5 9b 3f 80 0 > > (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 > > (da0:ahc0:0:0:0): SCSI parity error > > (da0:ahc0:0:0:0): WRITE(06). CDB: a 5 9c bf 80 0 > > (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 > > (da0:ahc0:0:0:0): SCSI parity error > > (da0:ahc0:0:0:0): WRITE(06). CDB: a 5 9a bf 80 0 > > (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 > > (da0:ahc0:0:0:0): SCSI parity error > > (da0:ahc0:0:0:0): WRITE(06). CDB: a 5 9c bf 80 0 > > (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 > > (da0:ahc0:0:0:0): SCSI parity error > > (da0:ahc0:0:0:0): WRITE(06). CDB: a 5 9c bf 80 0 > > (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 > > (da0:ahc0:0:0:0): SCSI parity error > > (da0:ahc0:0:0:0): WRITE(06). CDB: a 5 9c bf 80 0 > > Any help is greatly appriciated. > > Thanks, > > -Ben > Looks like your scsi controller is having trouble talking to the drive. You didn't just add or move devices and forget to reset the terminators, did you? If you haven't changed or moved hardware recently I would say that you are either losing a drive, a controller, or a cable. Josh > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message