Date: Fri, 16 Dec 2011 16:01:24 +1100 From: Jan Mikkelsen <janm-freebsd-hackers@transactionware.com> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-hackers@freebsd.org, Hugo Silva <hugo@barafranca.com>, Borja Marcos <borjam@sarenet.es> Subject: Re: mfi (Dell H700) + hot swapping doesn't appear to work with RC1 Message-ID: <D5A38F88-C47C-42B5-9DB1-D8716C96F506@transactionware.com> In-Reply-To: <201112150956.45214.jhb@freebsd.org> References: <4EE8A005.5030607@barafranca.com> <9317551F-CBE0-4368-B798-498E58E240B2@sarenet.es> <2EA3FFF4-E6A2-4371-8891-26E99C551C67@transactionware.com> <201112150956.45214.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16/12/2011, at 1:56 AM, John Baldwin wrote: > On Thursday, December 15, 2011 4:19:58 am Jan Mikkelsen wrote: >> For the mfi controllers I have been testing recently (MegaRAID = 9261-8i), you=20 > need to install the sysutils/megacli port, and use that to clear the=20= > "foreignness" of the disk you just added. Something like: >>=20 >> MegaCli -CfgForeign -Clear -a0 >>=20 >> You should be able to then recreate it as a JBOD device, and progress=20= > through whatever higher level recovery you need to do. >=20 > Can you do this by marking it as 'good' via mfiutil and then using = mfiutil > to create a volume? I was going to reply and say that mfiutil will complain about the drive = being in the wrong state, but after reading the other replies I decided = to test. With a blank drive, yes, you can use mfiutil to recreate the jbod = device. You don't even need to do an "mfiutil good" first. If you use a drive that has previously been used by an mfi controller, = it shows up as "bad". Doing "mfiutil good" makes it go to the = "unconfigured good" state. Then creation of the jbod fails with this = error: mfiutil: Command failed: Wrong firmware or drive state mfiutil: Failed to add volume: Input/output error At this point you need to reach for "MegaCli -CfgForeign" and deal with = the now foreign drive. You can use -Import (as pointed out by Andrew Boyer) or -Clear. In my = previous testing (on which my original reply was based), I used drives = that were being moved between machines and so my procedure ended up = being -Clear because I did not want the drive to have the same = configuration as the last time it was used. That was followed a dd from = /dev/zero and then the higher level steps. I have just tested -Import = for the same slot and it worked fine for me. I have not tested -Import = when putting the drive into a different slot. Regards, Jan.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D5A38F88-C47C-42B5-9DB1-D8716C96F506>