Date: Tue, 07 Jan 2003 11:59:02 From: R P <rpsbsd@cox.net> To: "Justin T. Gibbs" <gibbs@scsiguy.com> Cc: freebsd-scsi@freebsd.org Subject: Re: scsi parity errors Message-ID: <3.0.5.32.20030107115902.009423f0@pop.west.cox.net> In-Reply-To: <822850000.1041956667@aslan.scsiguy.com> References: <3.0.5.32.20030107063959.00916c40@pop.west.cox.net> <3.0.5.32.20030107063959.00916c40@pop.west.cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Justin, Thanks for your quick response. At 09:24 AM 1/7/03 -0700, you wrote: >> 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? Yes. The current config is two drives on the LVD and only the CDRW on the 50 pin SE. Nothing is on the 68 pin SE. >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. Verbose? How's that set? Setting Low off and high on resulted in no CDRW detected by the controller. Even with both the SE cables disconnected, there is no access to the 18G drive (drive 0). That leaves just the LVD cable and the two drives. But even with the 36G disconnected and only the 18G drive, I can't get it to boot without parity errors. >> 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. Are you saying that in this case, the drives on the ends of the 50 pin and 68 pin SE cables should not terminate the cables? > >> 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. One cable with terminator, one unterminated drive attached, controller termination set to automatic, many parity errors. What's left? Bad cable or Card? Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20030107115902.009423f0>