From owner-freebsd-scsi Sun Oct 27 15:32:31 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA25155 for freebsd-scsi-outgoing; Sun, 27 Oct 1996 15:32:31 -0800 (PST) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA25146 for ; Sun, 27 Oct 1996 15:32:26 -0800 (PST) Received: from crunch.io.org (crunch.io.org [198.133.36.156]) by post.io.org (8.7.5/8.7.3) with SMTP id SAA04501; Sun, 27 Oct 1996 18:32:05 -0500 (EST) Date: Sun, 27 Oct 1996 18:32:05 -0500 (EST) From: Brian Tao To: Stefan Esser cc: FREEBSD-SCSI-L Subject: Re: Wonky controller or drive? In-Reply-To: <199610141619.SAA04657@x14.mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 14 Oct 1996, Stefan Esser wrote: > > Hmm, I count 3 internal and two external cables ... > I guess each internal cable is some 100cm, actually, > at least I've yet to see a shorter cable being > delivered with a system. (Well, if you made it from > components yourself this is different :) We have our ribbon cables custom made for the position and orientation of our drives. There is enough slack for the cable to remain flexible, but not a lot of it loose inside the case. Anyhow, it turns out it *was* the new 4GB drive I had installed the previous week. It was causing the OS to report transient errors on all the other devices on the bus as well. I suppose this is possible if the SCSI connector on the bad drive degrades the signal on the wires. The 1GB boot drive (on the same physical cable as the 4GB) started showing more and more media errors. A low-level format fixed it up. I swapped in a new 4GB drive and all is well now. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"