From owner-freebsd-hackers@FreeBSD.ORG Sat May 31 01:49:27 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 897661065675 for ; Sat, 31 May 2008 01:49:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2416C8FC15 for ; Sat, 31 May 2008 01:49:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m4V1nIoO030810; Fri, 30 May 2008 21:49:18 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Fri, 30 May 2008 21:43:11 -0400 User-Agent: KMail/1.9.7 References: <20080530210347.5E1A6F1808E@mx.npubs.com> In-Reply-To: <20080530210347.5E1A6F1808E@mx.npubs.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805302143.11920.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Fri, 30 May 2008 21:49:20 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/7300/Fri May 30 19:42:28 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Stef Walter Subject: Re: RAID status issues with Intel MatrixRAID ataraid X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 May 2008 01:49:27 -0000 On Friday 30 May 2008 05:03:48 pm Stef Walter wrote: > This isn't a bug report, just a heads up to anyone using the same setup. > This occurred in production, and I don't currently have a non-production > hardware on which to investigate this bug and/or create a patch. > > In certain conditions, even though the Firmware RAID BIOS, says that a > RAID is degraded, the FreeBSD driver thinks it's business as usual. In > my case this resulted in file system corruption. Relevant output below. > > FreeBSD version: 6.3-RELEASE-p2 > > Cheers, > Stef Walter > > > > BIOS OUTPUT: > > Copyright(C) 2003-06 Intel Corporation. All Rights Reserved. > > RAID Volumes: > ID Name Level Strip Size Status Bootable > 0 RAID Set 1 RAID1(Mirror) N/A 465.8GB Degraded Yes > 1 RAID1(Mirror) N/A 465.8GB Normal Yes > > Physical Disks: > Port Drive Model Serial # Size Type/Status(Vol ID) > 0 WDC WD5000ABYS-0 WD-WCAPW5637184 465.8GB Member Disk(0) > 1 ST3500320NS 5QM09E6F 465.8GB Error Occurred(0) > 2 WDC WD5000ABYS-0 WD-WCAPW5548822 465.8GB Member Disk(1) > 3 ST3500320NS 5QM0991D 465.8GB Member Disk(1) > Press to enter Configuration Utility........... > > > > RELEVANT SNIPPET FROM DMESG: > > ar0: 476937MB status: READY > ar0: disk0 READY (master) using ad4 at ata2-master > ar0: disk1 READY (mirror) using ad6 at ata3-master Err, you have two RAID volumes, one degraded, and one ok. ar0 is apparently the one that is ok (drives 2 and 3). What is more odd is that it isn't seeing a RAID config at all for ad0 and ad2 (drives 0 and 1). -- John Baldwin