LSI MegaRAID SAS 9240 with mfi driver?
Doug Ambrisko
ambrisko at ambrisko.com
Mon Apr 16 16:34:07 UTC 2012
Jan Mikkelsen writes:
| On 31/03/2012, at 1:14 AM, Doug Ambrisko wrote:
| > John Baldwin writes:
| > | On Friday, March 30, 2012 12:06:40 am Jan Mikkelsen wrote:
| > | > Hi,
| > | >
| ...
| >
| > | > I have a loan LSI MegaRAID SAS 9240-4i controller for testing.
| > | > The pciconf -lv output is:
| > | >
| > | > none3 at pci0:1:0:0: class=0x010400 card=0x92411000 chip=0x00731000 rev=0x03 hdr=0x00
| > | > vendor = 'LSI Logic / Symbios Logic'
| > | > device = 'MegaRAID SAS 9240'
| > | > class = mass storage
| > | > subclass = RAID
| > | >
| > | > I added this line to src/sys/dev/mfi/mfi_pci.c
| > | >
| > | > {0x1000, 0x0073, 0xffff, 0xffff, MFI_FLAGS_GEN2, "LSI MegaRAID SAS 9240"},
| > | >
| > | > It gave this result (tried with hw.mfi.msi set to 0 and to 1):
| > | >
| > | > mfi0: <LSI MegaRAID SAS 9240> port 0xdc00-0xdcff mem 0xfe7bc000-0xfe7bffff,0xfe7c0000-0xfe7fffff irq 16 at device 0.0 on pci1
| > | > mfi0: Using MSI
| > | > mfi0: Megaraid SAS driver Ver 3.00
| > | > mfi0: Frame 0xffffff8000285000 timed out command 0x26C8040
| > | > mfi0: failed to send init command
| > | >
| > | > The firmware is package 20.10.1-0077, which is the latest on the LSI website.
| > | >
| > | > Is this path likely to work out? Any suggestions on where to go from here?
| > |
| > | You should try the updated mfi(4) driver that Doug (cc'd) is going to soon
| > | merge into HEAD. It syncs up with the mfi(4) driver on LSI's website which
| > | supports several cards that the current mfi(4) driver does not. (I'm not
| > | fully sure if the 9240 is in that group or not. Doug might know however.)
| >
| > Yes, this card is supported with the mfi(4) in projects/head_mfi. Looks
| > like we fixed a couple of last minute found bugs when trying to create 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.
|
| I have just imported the mfi(4) and mfiutil(8) into a 9.0-RELEASE tree to
| try this out.
|
| When booting up with two fresh drives attached, they show up as usable
| JBOD disks. However, I cannot use mfiutil to create anything with them.
| Every drive gives
|
| "mfiutil: Drive n not available"
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.
| Is this expected behaviour? How can I create a raid1 volume using
| mfiutil and clean disks?
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
real JBOD mode since it doesn't have code to support that.
| 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
| required. What version is necessary?
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.
| dmesg:
|
| mfi0: <Drake Skinny> port 0xdc00-0xdcff mem 0xfe7bc000-0xfe7bffff,0xfe7c0000-0xfe7fffff irq 16 at device 0.0 on pci1
| mfi0: Using MSI
| mfi0: Megaraid SAS driver Ver 4.23
| mfi0: 7021 (387925223s/0x0020/info) - Shutdown command received from host
| mfi0: 7022 (boot + 4s/0x0020/info) - Firmware initialization started (PCI ID 0073/1000/9241/1000)
| mfi0: 7023 (boot + 4s/0x0020/info) - Firmware version 2.120.244-1482
| mfi0: 7024 (boot + 5s/0x0020/info) - Package version 20.10.1-0077
| mfi0: 7025 (boot + 5s/0x0020/info) - Board Revision 03A
| mfi0: 7026 (boot + 33s/0x0002/info) - Inserted: PD 32(e0xff/s1)
| mfisyspd0: <MFI System PD> on mfi0
| mfisyspd0: 1907729MB (3907029168 sectors) SYSPD volume
| mfisyspd0: SYSPD volume attached
| mfisyspd1: <MFI System PD> on mfi0
| mfisyspd1: 1907729MB (3907029168 sectors) SYSPD volume
| mfisyspd1: SYSPD volume attached
You are definitely in real JBOD mode with each drive being /dev/mfisyspd0
and /dev/mfisyspd1. So you can access the drives as those to do some
experiments with if you want to.
Doug A.
More information about the freebsd-stable
mailing list