From owner-freebsd-stable@FreeBSD.ORG Thu Oct 23 01:53:22 2003 Return-Path: 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 6166716A4B3 for ; Thu, 23 Oct 2003 01:53:22 -0700 (PDT) Received: from mta03-svc.ntlworld.com (mta03-svc.ntlworld.com [62.253.162.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1608843F3F for ; Thu, 23 Oct 2003 01:53:21 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.124]) by mta03-svc.ntlworld.comESMTP <20031023085319.FPRN21223.mta03-svc.ntlworld.com@llama.fishballoon.org>; Thu, 23 Oct 2003 09:53:19 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 1ACbCp-000F7p-IP; Thu, 23 Oct 2003 09:52:31 +0100 Date: Thu, 23 Oct 2003 09:52:31 +0100 From: Scott Mitchell To: Doug White Message-ID: <20031023085231.GA57527@llama.fishballoon.org> References: <20031022212556.GA48208@llama.fishballoon.org> <20031022153722.P71676@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031022153722.P71676@carver.gumbysoft.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE-p13 i386 Sender: Scott Mitchell cc: freebsd-stable@freebsd.org Subject: Re: aic7896 SCB timeout - is this a sign of impending doom? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Oct 2003 08:53:22 -0000 On Wed, Oct 22, 2003 at 03:39:40PM -0700, Doug White wrote: > As mentioned, SCSI timeouts can have multiple causes, most of them not > good. The thing to watch for is which target the command timed out on. > Command timeouts can come from: > > . Bad cabling or termination > . Bad cabling or termination > . Bad cabling or termination (it needs to be said three times) > . Flakey/failing device > > If it continues to happen then you should take a look around. Temperature > wouldn't be a bad thing to check anyway. Hi Doug, The drives are housed in a hot-swap cage in an Intel server case, so cabling or termination problems would be quite serious... there's only one cable and that's hardwired in. The drives are ~3 years old so it would not surprise me if one was on the way out. Might be time to investigate the SMART monitoring tools that were mentioned on here a week or so ago. Temperature shouldn't be a problem given the number of fans in the case, but I'll check that they're all still running OK. This particular box is at the bottom of a rack in a room with a ridiculous oversupply of underfloor aircon - overheating has never been a problem here :-) Anyway, I'll keep an eye on it and hope it doesn't happen again. > Good boards. I'm using them as my build farm right now. 600MHz procs > aren't that fast anymore but its a solid machine. Agreed, they're excellent machines. We use t pair of them as file / cvs / DNS / NIS / www / etc. servers, which they're more than adequate for. Thanks for your help. Cheers, Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott at fishballoon.org | 0xAA775B8B | -- Anon