From owner-freebsd-stable Sun Nov 24 15:42:22 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9485837B401; Sun, 24 Nov 2002 15:42:20 -0800 (PST) Received: from mtiwmhc11.worldnet.att.net (mtiwmhc11.worldnet.att.net [204.127.131.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id C425543EAF; Sun, 24 Nov 2002 15:42:16 -0800 (PST) (envelope-from cswiger@mac.com) Received: from prime ([12.88.88.237]) by mtiwmhc11.worldnet.att.net (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with SMTP id <20021124234215.HKGU20682.mtiwmhc11.worldnet.att.net@prime>; Sun, 24 Nov 2002 23:42:15 +0000 Message-ID: <002b01c29413$21079630$0301a8c0@prime> From: "Charles Swiger" To: , References: <20021124193031.GA18148@nvg.ntnu.no> Subject: Re: SCSI parity error; software- or hardware-problem? Date: Sun, 24 Nov 2002 18:42:18 -0500 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 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG taliesin@nvg.ntnu.no wrote: [ ... ] > If it is *only* a hardware-problem it is easy though expensive to fix; > but what part of the system is the problem? Cable, disks or > controller- card? In that case, what controller-card/disks would you > recommend? This isn't likely to be a FreeBSD issue. SCSI parity errors are generally due to termination problems or your cables getting flaky. Given that you appear to be using both a 50-pin narrow SCSI-2 device (the CD-ROM), and 68-pin SCSI-3 devices at Ultra-160 speeds, well, let's just say that the aforementioned problems are more likely to occur. Some things to do would be to try removing the CD-ROM for a while and test out the system and see whether that helps. Or drop the speed down to SCSI-2 (40MB/s-- 20MHz @ 16 bits wide). You might also double-check for the existance of a BIOS upgrade for the card, and review the card's internal termination configuration. -Chuck PS: A willingness to purchase replacement hardware when you encounter problems is not a bad approach, at least if one values getting the job done regardless of cost. That being said, it's also likely that you can get your existing hardware to work without spending money quite yet...or to at least isolate a specific defective component which does need to be replaced. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message