From owner-freebsd-stable Sun Nov 28 9:59:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id AF45714D4C for ; Sun, 28 Nov 1999 09:59:56 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA21374; Sun, 28 Nov 1999 10:58:37 -0700 (MST) (envelope-from ken) Message-Id: <199911281758.KAA21374@panzer.kdm.org> Subject: Re: ahc problems (with vinum?) In-Reply-To: <14401.26545.58505.622791@trooper.velocet.net> from David Gilbert at "Nov 28, 1999 12:34:41 pm" To: dgilbert@velocet.ca (David Gilbert) Date: Sun, 28 Nov 1999 10:58:37 -0700 (MST) Cc: jgreco@ns.sol.net (Joe Greco), stable@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Gilbert wrote... > >>>>> "Joe" == Joe Greco writes: > > Joe> Just having spent a week debugging a (very) intermittent SCSI bus > Joe> problem, I agree that I've seen some odd behaviour of this sort. > Joe> What's even more exasperating is that, at least in some cases, it > Joe> does appear to recover the one device that erred, but the rest > Joe> stop functioning. > > It would appear that I have replicated the problem again... but I have > relagated my serial consoles to other more desparate uses. I will go > down and check, but from memory, that is typical of the sequence I > see. If you're seeing the same sorts of problems that Joe is, you probably have a cabling or termination problem. > My drives (just to respond to an earlier question) are correctly > terminated with manufacturer's parts --- so the LVD chain is > terminated with LVD parts supplied by the LVD enclosure maker. The > Ultra chain is terminated by an older drive that supports termination > ... and there are only two drives on that chain. > > I think my short-term solution will be to put a second 2940 in the > machine so that the root drive will still be functional when this > happens. ...And you can get console logs off the machine that way. That will hopefully reveal what sort of trouble is going on. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message