From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 2 09:14:38 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47A0916A4D2 for ; Fri, 2 Jul 2004 09:14:38 +0000 (GMT) Received: from hartley.mintel.co.uk (hartley.mintel.com [213.206.147.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D31D43D53 for ; Fri, 2 Jul 2004 09:14:37 +0000 (GMT) (envelope-from jason.thomson@mintel.com) Received: from [10.0.62.5] ([10.0.62.5])i629D9pb045224; Fri, 2 Jul 2004 10:13:09 +0100 (BST) (envelope-from jason.thomson@mintel.com) Message-ID: <40E52725.1060409@mintel.com> Date: Fri, 02 Jul 2004 10:13:09 +0100 From: Jason Thomson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Alasdair Lumsden References: <1088701228.2638.86.camel@host-83-146-2-180.bulldogdsl.com> <20040701215131.GA83112@elvis.mu.org> <1088722694.2554.48.camel@host-83-146-2-180.bulldogdsl.com> <20040701230015.GA87635@elvis.mu.org> <1088724938.2879.17.camel@host-83-146-2-180.bulldogdsl.com> <20040701233811.GA89536@elvis.mu.org> <1088725862.2879.22.camel@host-83-146-2-180.bulldogdsl.com> In-Reply-To: <1088725862.2879.22.camel@host-83-146-2-180.bulldogdsl.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) cc: freebsd-hardware@freebsd.org Subject: Re: 3Ware 8506 Series, 3DM, Upgrading to 9000 Series X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2004 09:14:38 -0000 This sounds like a similar problem we have experienced with FreeBSD 4.x and 7506 cards, but only with Maxtor disks (so far): The card stops responding - the console prints swap_pager error messages - and the whole system locks up (of course). We fixed the symptoms by using Maxtor's PowerMax (DOS) tools to scan the disks. One of the disks had a bad sector. We used the PowerMax tools to repair the disk (I guess it just wrote to the bad sector to remap it), and then rebuilt the array. Haven't had a problem with that machine since. However, we do have the same symptoms occurring on two other machines, but like you, it's intermittent, and these are production machines that can't be down for too long. I will ensure that I have DDB compiled in and crashdumps enabled should this occur again. I would love to help track this down - if this is the same problem. Alasdair Lumsden wrote: > On Fri, 2004-07-02 at 00:38, Paul Saab wrote: > >>This will tell you how to get into DDB and when you get the ddb prompt, >>type trace and tell us where it is hung at. > > > Ahh, excellent. Thanks, I'll give this a go. > > Unfortunately the hang doesn't occur very often, so it might be a few > weeks before it happens again. > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > >