From owner-freebsd-questions Wed Nov 15 21:25:28 2000 Delivered-To: freebsd-questions@freebsd.org Received: from copernicus.tranquility.net (copernicus.tranquility.net [206.152.117.186]) by hub.freebsd.org (Postfix) with ESMTP id 4916E37B479 for ; Wed, 15 Nov 2000 21:25:25 -0800 (PST) Received: (from sid67@localhost) by copernicus.tranquility.net (8.11.1/8.11.1) id eAG5SBh53906; Wed, 15 Nov 2000 23:28:11 -0600 (CST) (envelope-from sid67) Date: Wed, 15 Nov 2000 23:28:11 -0600 From: Ben Weaver To: Josh Paetzel Cc: questions@FreeBSD.ORG Subject: Re: What's up with these SCSI parity errors and aborted commands? Message-ID: <20001115232811.A53887@tranquility.net> References: <20001113072628.A4463@tranquility.net> <01d901c04ead$e705ce40$0200000a@vladsempire.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <01d901c04ead$e705ce40$0200000a@vladsempire.net>; from jpaetzel@hutchtel.net on Tue, Nov 14, 2000 at 08:43:55PM -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 14, 2000 at 08:43:55PM -0600, Josh Paetzel wrote: > > ----- 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 > Nope, I sure haven't added or moved any SCSI devices in a while. Thanks for your response. Are there any tools (i.e. software utilities) that would help me diagnose the cause? Thanks, -Ben > > > > 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