From owner-freebsd-stable@FreeBSD.ORG Tue Apr 17 17:56:12 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DC4B106564A for ; Tue, 17 Apr 2012 17:56:12 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id E5D8E8FC12 for ; Tue, 17 Apr 2012 17:56:11 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 5C86BB958; Tue, 17 Apr 2012 13:56:11 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Tue, 17 Apr 2012 13:51:53 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p13; KDE/4.5.5; amd64; ; ) References: <201204161632.q3GGWwJo045910@ambrisko.com> <8CECFFF5-9540-46BF-B855-082049CC5EFB@transactionware.com> In-Reply-To: <8CECFFF5-9540-46BF-B855-082049CC5EFB@transactionware.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Message-Id: <201204171351.53831.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 17 Apr 2012 13:56:11 -0400 (EDT) Cc: Jan Mikkelsen Subject: Re: LSI MegaRAID SAS 9240 with mfi driver? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2012 17:56:12 -0000 On Monday, April 16, 2012 10:15:10 pm Jan Mikkelsen wrote: >=20 > On 17/04/2012, at 2:32 AM, Doug Ambrisko wrote: >=20 > > Jan Mikkelsen writes: > > | On 31/03/2012, at 1:14 AM, Doug Ambrisko wrote: > ... > > | > Yes, this card is supported with the mfi(4) in projects/head_mfi. = =20 Looks > > | > like we fixed a couple of last minute found bugs when trying to cre= ate=20 a > > | > RAID wth mfiutil. This should be fixed now. I'm going to start the > > | > merge to -current today. The version in head_mfi can run on older > > | > versions of FreeBSD with the changes that Sean did. > > |=20 > > | I have just imported the mfi(4) and mfiutil(8) into a 9.0-RELEASE tre= e=20 to=20 > > | try this out. > > |=20 > > | When booting up with two fresh drives attached, they show up as usabl= e=20 > > | JBOD disks. However, I cannot use mfiutil to create anything with the= m.=20 > > | Every drive gives > > |=20 > > | "mfiutil: Drive n not available" > >=20 > > You might want to include the output of: > > mfiutil show drives > > and then the command you are trying to do to create a RAID with. > >=20 > > | Is this expected behaviour? How can I create a raid1 volume using=20 > > | mfiutil and clean disks? > >=20 > > I'm not sure if mfiutil can switch disks from JBOD mode to RAID. > > I don't see any reason why it shouldn't. It can't go from RAID to=20 > > real JBOD mode since it doesn't have code to support that. > >=20 > > | I tried using MegaCli from the LSI website (versions 8.02.16 and > > | 8.02.21), but they can't even detect the controller. I know you > > | said at some point that a very recent version of MegaCli was=20 > > | required. What version is necessary? > >=20 > > What was the syntax you used since usage is cryptic? I've never > > seen a MegaCli that couldn't access the card. What I meant by > > more recent MegaCli is earlier versions didn't have the JBOD > > commands in it. I have a 8.00.46 that knows about JBOD. >=20 > The MegaCli problem was an embarrassing operator error which I can't blam= e=20 on the bad UI. >=20 > "mfiutil create jbod =85" doesn't create a JBOD disk, it creates a raid0= =20 volume. I think that was expected. The biggest problem with this controller= =20 and just mfiutil is that you can't get a drive from the JBOD state to the=20 unconfigured-good state, and a blank disk starts in JBOD. So to do any setu= p=20 you need to resort to the BIOS utility or MegaCli. >=20 > For each disk to change from JBOD to "Unconfigured-good" so that it can b= e=20 used to create a volume, I needed to do: >=20 > MegaCli -PDMakeGood -Physdrv '[64:1]' -force -a0 >=20 > Obviously with the right drivespec. Once they're in this state I can use= =20 mfiutil to create volumes. >=20 > I can get drives from the unconfigured-good state to JBOD by doing "MegaC= li=20 =2DPDMakeJBOD =85".=20 >=20 > This is just in a little test machine with a few drives. Now that it is=20 working to this level I will get a server with a 9240 and give it a proper= =20 run. I'll also try the driver out in one of the 9261 based servers we've go= t=20 here. >=20 > Thanks! It should be very easy to add a 'good' command to mfiutil. Actually, there= =20 already is a 'good' command. Have you tried using that? # mfiutil good =2D-=20 John Baldwin