From owner-freebsd-scsi Tue Jan 7 8:24:43 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 912BF37B401 for ; Tue, 7 Jan 2003 08:24:41 -0800 (PST) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAB2843E4A for ; Tue, 7 Jan 2003 08:24:40 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by aslan.scsiguy.com (8.12.6/8.12.5) with ESMTP id h07GORWq048465; Tue, 7 Jan 2003 09:24:27 -0700 (MST) (envelope-from gibbs@scsiguy.com) Date: Tue, 07 Jan 2003 09:24:27 -0700 From: "Justin T. Gibbs" To: R P , freebsd-scsi@FreeBSD.ORG Subject: Re: scsi parity errors Message-ID: <822850000.1041956667@aslan.scsiguy.com> In-Reply-To: <3.0.5.32.20030107063959.00916c40@pop.west.cox.net> References: <3.0.5.32.20030107063959.00916c40@pop.west.cox.net> X-Mailer: Mulberry/3.0.0b10 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > I have a problem since adding a second hard drive to the 68-pin LVD/SE > cable on an Adaptec 29160. > > The machine has two PPro 200 cpus, 384MB ram, Linksys lne100tx NIC, > generic PCI USB card, Elsa Synergy II-32 PCI video card, Adaptec 1510 ISA > SCSI controller (for a scanner) and SoundBlaster Vibra16 ISA card. There > are two drives on the LVD/SE cable and neither is terminated as the cable > is terminated. There is a SCSI CDRW on the 50-pin SE connector and a > 9.2GB drive on the 68-pin SE connector. Both are terminated. How is the controller terminated? Are you using auto termination for both the primary (LVD only) and secondary (LVD/SE) bus segments? If you boot the system with verbose set, the aic7xxx driver will indicate how it has setup your controller termination. You need termination enabled on the primary segment and only the high byte termination enabled on the secondary segment. > When I tried booting 4.4 from the HD after adding the second LVD drive, > parity errors ran up the screen and the machine automatically rebooted. > Trying the 4.0 CD produced the same parity errors and a stall. Removing > _all_ drives and cables but drive 0, the 18GB drive containing the earlier > FreeBSD didn't work. There are now no circumstances that allow FreeBSD to > install on that drive. Booting the 4.7 CD didn't work, but allowed > getting debug output. It sounds like you have manual termination settings that are no longer correct for your setup or were never correct but happened to work under a ligher load. > These drives and adapter work in all configurations tried with MSDOS, > Windows NT, and 2000 using supplied drivers from Adaptec and no drive > parity or other drive errors were detected. The non-FreeBSD drivers perform domain validation and will silently perform speed fallback to avoid parity errors. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message