From owner-freebsd-hardware@FreeBSD.ORG Wed Oct 13 17:04:52 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60E0E106564A for ; Wed, 13 Oct 2010 17:04:52 +0000 (UTC) (envelope-from aurelien.bras@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1DA148FC08 for ; Wed, 13 Oct 2010 17:04:51 +0000 (UTC) Received: by gwb20 with SMTP id 20so172282gwb.13 for ; Wed, 13 Oct 2010 10:04:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=kzZF54IZJkrAz1K35A2K1PHx7W3SvdDgMomlWnZE4Wc=; b=EiN86aGBdAg/U12ZHetcJ94basXyWqK2nRfiQVOjx9rsG/+BWF6StNguR8JJ4zM/TV 2SxBcV7uR8jHy+1skoYyZWj+d+RPHrH/o6bk4yGUKhs28vIfxBV4zEWxjr1a1E5JINiH besOxHTG/qJkvdJrbUIJFlQzfQzpzye2C2j4k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Kak2c5ow7BlqYRayoYPcO5lzRpePFBa6IRcgDBLKDcVAut2hn0WCHiMEzts7BM9/DB zfw7b8y5IZudYn6cSpgwDuux6vZ7ux9Mdnef3sJvvxVSoc4UGA6cDboYNL+3Bdsdf1lz fGTuIyQ5MTr6lXVsH5d534WxMGrSUbj2JoEq8= MIME-Version: 1.0 Received: by 10.42.177.7 with SMTP id bg7mr2489515icb.450.1286987826834; Wed, 13 Oct 2010 09:37:06 -0700 (PDT) Received: by 10.231.142.141 with HTTP; Wed, 13 Oct 2010 09:37:06 -0700 (PDT) Date: Wed, 13 Oct 2010 18:37:06 +0200 Message-ID: From: =?ISO-8859-1?Q?Aur=E9lien_Bras?= To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: support of dell r710 hardware X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Oct 2010 17:04:52 -0000 Hi, I'm looking to buy a Dell r710 with this controller : SAS6iR/PERC H200 Any feedback about support with freebsd 8.1 ? Thanks, Aur=E9lien From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 15 19:45:58 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70410106564A for ; Fri, 15 Oct 2010 19:45:58 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (edge.tidalhosting.net [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id 28C3B8FC0A for ; Fri, 15 Oct 2010 19:45:57 +0000 (UTC) Received: from jack.bspruce.com ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Fri, 15 Oct 2010 15:05:55 -0400 X-WatchGuard-Mail-Exception: Allow Message-ID: <4CB8A614.6000707@greatbaysoftware.com> Date: Fri, 15 Oct 2010 15:05:56 -0400 From: Charles Owens MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Subject: mfiutil reports "PSTATE 0x0020" new drive state X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2010 19:45:58 -0000 Hello, We have a mfi-based RAID array with a failed drive. When replacing the failed drive with a brand new one 'mfiutil' reports it having status of "PSTATE 0x0020". Attempts to work with the drive to make it a hot spare are unsuccessful (eg. using "good" and/or "add" subcommands of mfiutil). We've tested procedures for replacing failed drives in the past and haven't run into this. Looking at the code for mfiutil it appears that this is happening because the mfi controller is reporting a drive status code that mfiutil doesn't know about. The system is remote and in production, so booting into the LSI in-BIOS RAID-management-tool is not an attractive option. Any help with understanding the situation and potential next steps would be greatly appreciated. More background information follows below. Thanks, Charles Storage configuration: 4-drive RAID 10 array plus one hot spare [root@svr ~]# mfiutil show config mfi0 Configuration: 2 arrays, 1 volumes, 0 spares array 0 of 2 drives: drive 0 ( 149G) ONLINE SATA enclosure 1, slot 0 drive 1 ( 149G) ONLINE SATA enclosure 1, slot 1 array 1 of 2 drives: drive 4 ( 149G) ONLINE SATA enclosure 1, slot 3 drive 3 ( 149G) ONLINE SATA enclosure 1, slot 2 volume mfid0 (296G) RAID-1 256K OPTIMAL spans: array 0 array 1 [root@svr ~]# mfiutil show drives mfi0 Physical Drives: ( 149G) ONLINE SATA enclosure 1, slot 0 ( 149G) ONLINE SATA enclosure 1, slot 1 ( 149G) ONLINE SATA enclosure 1, slot 2 ( 149G) ONLINE SATA enclosure 1, slot 3 ( 149G) PSTATE 0x0020 SATA enclosure 1, slot 4 Partial system boot log: Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-RELEASE-p2 #4: Thu Mar 4 04:21:04 UTC 2010 cowens@newcastle.greatbaysoftware.com:/usr/obj/usr/src/sys/BEACON Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz (2261.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Stepping = 5 Features=0xbfebfbff Features2=0x9ce3bd AMD Features=0x28100000 AMD Features2=0x1 TSC: P-state invariant real memory = 6442450944 (6144 MB) avail memory = 6202064896 (5914 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) x 2 SMT threads ... mfi0: port 0x1000-0x10ff mem 0xb1900000-0xb193ffff,0xb1940000-0xb197ffff irq 16 at device 0.0 on pci6 mfi0: Megaraid SAS driver Ver 3.00 mfi0: [ITHREAD] ... AcpiOsExecute: failed to enqueue task, consider increasing the debug.acpi.max_tasks tunable ACPI Error (psparse-0633): Method parse/execution failed [\\_SB_.PCI0.HEC2.HSCI] (Node 0xccbff740)mfid0: on mfi0 mfid0: 303268MB (621092864 sectors) RAID volume '' is optimal -- Charles Owens Great Bay Software, Inc. From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 15 20:51:38 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C7BB106564A for ; Fri, 15 Oct 2010 20:51:38 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (edge.tidalhosting.net [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id C31BA8FC12 for ; Fri, 15 Oct 2010 20:51:37 +0000 (UTC) Received: from jack.bspruce.com ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Fri, 15 Oct 2010 16:51:33 -0400 X-WatchGuard-Mail-Exception: Allow Message-ID: <4CB8BED6.8040204@greatbaysoftware.com> Date: Fri, 15 Oct 2010 16:51:34 -0400 From: Charles Owens MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <4CB8A614.6000707@greatbaysoftware.com> In-Reply-To: <4CB8A614.6000707@greatbaysoftware.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Subject: Re: mfiutil reports "PSTATE 0x0020" new drive state X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2010 20:51:38 -0000 Hmm... the problem appears to have resolved itself. After a few hours the new drive seems to have gone back into the array, and the original hot spare drive put back into hot-spare state. So I'm interpreting state 0x0020 to therefore mean something like "hang on while I use this new drive to automatically put everything back as it was before the failure". Is this correct? Thanks, Charles [root@Bsvr ~]# mfiutil show drives mfi0 Physical Drives: ( 149G) ONLINE SATA enclosure 1, slot 0 ( 149G) ONLINE SATA enclosure 1, slot 1 ( 149G) ONLINE SATA enclosure 1, slot 2 ( 149G) HOT SPARE SATA enclosure 1, slot 3 ( 149G) ONLINE SATA enclosure 1, slot 4 On 10/15/10 3:05 PM, Charles Owens wrote: > Hello, > > We have a mfi-based RAID array with a failed drive. When replacing > the failed drive with a brand new one 'mfiutil' reports it having > status of "PSTATE 0x0020". Attempts to work with the drive to make it > a hot spare are unsuccessful (eg. using "good" and/or "add" > subcommands of mfiutil). We've tested procedures for replacing > failed drives in the past and haven't run into this. > > Looking at the code for mfiutil it appears that this is happening > because the mfi controller is reporting a drive status code that > mfiutil doesn't know about. The system is remote and in production, > so booting into the LSI in-BIOS RAID-management-tool is not an > attractive option. > > Any help with understanding the situation and potential next steps > would be greatly appreciated. More background information follows below. > > Thanks, > > Charles > > > Storage configuration: 4-drive RAID 10 array plus one hot spare > > [root@svr ~]# mfiutil show config > mfi0 Configuration: 2 arrays, 1 volumes, 0 spares > array 0 of 2 drives: > drive 0 ( 149G) ONLINE > SATA enclosure 1, slot 0 > drive 1 ( 149G) ONLINE > SATA enclosure 1, slot 1 > array 1 of 2 drives: > drive 4 ( 149G) ONLINE > SATA enclosure 1, slot 3 > drive 3 ( 149G) ONLINE > SATA enclosure 1, slot 2 > volume mfid0 (296G) RAID-1 256K OPTIMAL spans: > array 0 > array 1 > > [root@svr ~]# mfiutil show drives > mfi0 Physical Drives: > ( 149G) ONLINE SATA enclosure 1, > slot 0 > ( 149G) ONLINE SATA enclosure 1, > slot 1 > ( 149G) ONLINE SATA enclosure 1, > slot 2 > ( 149G) ONLINE SATA enclosure 1, > slot 3 > ( 149G) PSTATE 0x0020 SATA > enclosure 1, slot 4 > > > Partial system boot log: > > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 8.0-RELEASE-p2 #4: Thu Mar 4 04:21:04 UTC 2010 > cowens@newcastle.greatbaysoftware.com:/usr/obj/usr/src/sys/BEACON > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(R) CPU E5520 @ 2.27GHz (2261.27-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x106a5 Stepping = 5 > > Features=0xbfebfbff MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Features2=0x9ce3bd ,SSE4.1,SSE4.2,POPCNT> > AMD Features=0x28100000 > AMD Features2=0x1 > TSC: P-state invariant > real memory = 6442450944 (6144 MB) > avail memory = 6202064896 (5914 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs > FreeBSD/SMP: 2 package(s) x 4 core(s) x 2 SMT threads > > ... > > mfi0: port 0x1000-0x10ff mem > 0xb1900000-0xb193ffff,0xb1940000-0xb197ffff irq 16 at device 0.0 on pci6 > mfi0: Megaraid SAS driver Ver 3.00 > mfi0: [ITHREAD] > > ... > > AcpiOsExecute: failed to enqueue task, consider increasing the > debug.acpi.max_tasks tunable > ACPI Error (psparse-0633): Method parse/execution failed > [\\_SB_.PCI0.HEC2.HSCI] (Node 0xccbff740)mfid0: on > mfi0 > mfid0: 303268MB (621092864 sectors) RAID volume '' is optimal > > > > From owner-freebsd-hardware@FreeBSD.ORG Fri Oct 15 22:49:30 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 894E1106564A; Fri, 15 Oct 2010 22:49:30 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2CAB08FC0A; Fri, 15 Oct 2010 22:49:29 +0000 (UTC) Received: by qwe4 with SMTP id 4so653961qwe.13 for ; Fri, 15 Oct 2010 15:49:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6Qs6AIzSbGc+FC1crWIG+XXrWFwZNZUtvRD6KONE2MA=; b=NMBqNsN9oefGSRYEQ4h6ZyXnJU6yEDZcxPX1MIQuKdtW0a2xOd4U5A0tREyW8KIRlA oW85ElAimXpUX3gYDdtDcqxOUAVyFg1iL8DdRNaIhm5yuP3/eFPAT0JZa8TqRIggY/V+ fQ6sFIYFfOXDOd2CtfXdANgaWsVzgOp6UX5P8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=nS8z+7O9WrsZ9vjLPK1EXB1SzX6ML/GS/h+3VrMfevQ3pxFLOH7UDUhPV6237EnwTT 1aOfCLBgl6sRYJJTE4By01rBh1aydaipNDVj6ZjBS13tP7pMiRPn4gMSdEmINMd8gYOE S7nxTveZEnDSyYdr4lwIvS0bHcqMxgun5EZTM= MIME-Version: 1.0 Received: by 10.224.212.199 with SMTP id gt7mr365267qab.130.1287181137068; Fri, 15 Oct 2010 15:18:57 -0700 (PDT) Received: by 10.229.61.29 with HTTP; Fri, 15 Oct 2010 15:18:57 -0700 (PDT) In-Reply-To: <4CB8BED6.8040204@greatbaysoftware.com> References: <4CB8A614.6000707@greatbaysoftware.com> <4CB8BED6.8040204@greatbaysoftware.com> Date: Sat, 16 Oct 2010 02:18:57 +0400 Message-ID: From: Sergey Kandaurov To: Charles Owens Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Scott Long , freebsd-hardware@freebsd.org Subject: Re: mfiutil reports "PSTATE 0x0020" new drive state X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2010 22:49:30 -0000 On 16 October 2010 00:51, Charles Owens wrote= : > =A0Hmm... the problem appears to have resolved itself. =A0After a few hou= rs the > new drive seems to have gone back into the array, and the original hot sp= are > drive put back into hot-spare state. > > So I'm interpreting state 0x0020 to therefore mean something like "hang o= n > while I use this new drive to automatically put everything back as it was > before the failure". =A0Is this correct? > > Thanks, > Charles > > [root@Bsvr ~]# mfiutil show drives > mfi0 Physical Drives: > ( =A0149G) ONLINE =A0SATA enclosure 1= , slot 0 > ( =A0149G) ONLINE =A0SATA enclosure 1= , slot 1 > ( =A0149G) ONLINE =A0SATA enclosure 1= , slot 2 > ( =A0149G) HOT SPARE =A0SATA enclosur= e 1, slot > 3 > ( =A0149G) ONLINE =A0SATA enclosure 1= , slot 4 > > > > On 10/15/10 3:05 PM, Charles Owens wrote: >> >> =A0Hello, >> >> We have a mfi-based RAID array with a failed drive. =A0When replacing th= e >> failed drive with a brand new one 'mfiutil' reports it having status of >> "PSTATE 0x0020". =A0Attempts to work with the drive to make it a hot spa= re are >> unsuccessful (eg. using "good" and/or "add" subcommands of mfiutil). =A0= We've >> tested procedures for replacing failed drives in the past and haven't ru= n >> into this. >> >> Looking at the code for mfiutil it appears that this is happening becaus= e >> the mfi controller is reporting a drive status code that mfiutil doesn't >> know about. =A0The system is remote and in production, so booting into t= he LSI >> in-BIOS RAID-management-tool is not an attractive option. >> >> Any help with understanding the situation and potential next steps would >> be greatly appreciated. =A0More background information follows below. >> >> Thanks, >> >> Charles >> >> >> Storage configuration: =A04-drive RAID 10 array plus one hot spare >> >> [root@svr ~]# mfiutil show config >> mfi0 Configuration: 2 arrays, 1 volumes, 0 spares >> =A0 =A0array 0 of 2 drives: >> =A0 =A0 =A0 =A0drive 0 ( =A0149G) ONLINE =A0SATA >> enclosure 1, slot 0 >> =A0 =A0 =A0 =A0drive 1 ( =A0149G) ONLINE =A0SATA >> enclosure 1, slot 1 >> =A0 =A0array 1 of 2 drives: >> =A0 =A0 =A0 =A0drive 4 ( =A0149G) ONLINE =A0SATA >> enclosure 1, slot 3 >> =A0 =A0 =A0 =A0drive 3 ( =A0149G) ONLINE =A0SATA >> enclosure 1, slot 2 >> =A0 =A0volume mfid0 (296G) RAID-1 256K OPTIMAL spans: >> =A0 =A0 =A0 =A0array 0 >> =A0 =A0 =A0 =A0array 1 >> >> [root@svr ~]# mfiutil show drives >> mfi0 Physical Drives: >> ( =A0149G) ONLINE =A0SATA enclosure = 1, slot >> 0 >> ( =A0149G) ONLINE =A0SATA enclosure = 1, slot >> 1 >> ( =A0149G) ONLINE =A0SATA enclosure = 1, slot >> 2 >> ( =A0149G) ONLINE =A0SATA enclosure = 1, slot >> 3 >> ( =A0149G) PSTATE 0x0020 =A0SATA enc= losure >> 1, slot 4 >> >> mfi0: =A0port 0x1000-0x10ff mem >> ... >> Hi, Charles Owens. 0x20 is much likely to be the copyback physical state, which is missing in enum mfi_pd_state. And what you've experienced is copyback feature in action :) Your array has been rebuilt with HSP as its ordinal PD, then you switched failed drive with good one, and HSP came into copyback mode to move all its data back to good disk. That prevents reordering of disk numbers in array and double rebuilding. --=20 wbr, pluknet