From owner-freebsd-hardware@FreeBSD.ORG Fri Jul 16 19:56:44 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 EBF7D16A4CE; Fri, 16 Jul 2004 19:56:44 +0000 (GMT) Received: from smtp.internal.alivewww.com (gp1.alivewww.com [217.158.94.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 723D543D31; Fri, 16 Jul 2004 19:56:44 +0000 (GMT) (envelope-from enquiries@alivewww.com) Received: from host-83-146-2-180.bulldogdsl.com ([83.146.2.180]) by smtp.internal.alivewww.com with asmtp (Exim 4.34) id 1BlYoy-0007qx-0C; Fri, 16 Jul 2004 20:56:40 +0100 From: Alasdair Lumsden To: Jason Thomson In-Reply-To: <40F82F29.9040006@mintel.com> 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> <40E52725.1060409@mintel.com> <40F82F29.9040006@mintel.com> Content-Type: text/plain Message-Id: <1090007796.3111.50.camel@host-83-146-2-180.bulldogdsl.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6-1mdk Date: Fri, 16 Jul 2004 20:56:37 +0100 Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org cc: vkayshap@amcc.com cc: Charles Sprickman cc: freebsd-hardware@freebsd.org cc: Doug White cc: Ken Smith Subject: Re: Reproducible FreeBSD 4.10-STABLE (Jul 7) , 3ware 7506-4 lockup. 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, 16 Jul 2004 19:56:45 -0000 On Fri, 2004-07-16 at 20:40, Jason Thomson wrote: > Another data point: > > In one previouse instance of this problem, we resolved the symptoms by > checking the disks with Maxtor's PowerMax tools. One disk was found to > have errors and been and repairing / replacing that disk resolved the > errors. (However, if the disk has errors, I would expect the RAID > card to deal with it!). Absolutely. If a disk is misbehaving, then it should be dropped from the array and the hot-spare used (if any). That way the disk can be pulled and replaced. The machine shouldn't lock up. We've ordered some 9000 series cards to replace the 8000 series cards we are having problems with. I'll report back any progress.