Jump to content

Driver for LSI MegaRAID SAS family


dukzcry
 Share

402 posts in this topic

Recommended Posts

Installed the card in a different machine and let the machine reboot after installing your driver this time and the problem went away. Now I have a whole new problem though. I created a RAID 5 from the BIOS. OS X 10.8 and 10.9 can both see the VD:

$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *160.0 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS Boot                    159.7 GB   disk0s2
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                                                   *12.0 TB    disk1

mfiutil as well:

$ sudo mfiutil show config
mfi0 Configuration: 1 arrays, 1 volumes, 0 spares
    array 0 of 5 drives:
        drive  0 ( 2795G) ONLINE <ST33000650NS 0001 serial=Z290DDF7> SATA
        drive  1 ( 2795G) ONLINE <ST33000650NS 0001 serial=Z29063E6> SATA
        drive  2 ( 2795G) ONLINE <ST33000650NS 0001 serial=Z29062YC> SATA
        drive  3 ( 2795G) ONLINE <ST33000650NS 0001 serial=Z2904V1V> SATA
        drive  4 ( 2795G) ONLINE <ST33000650NS 0001 serial=Z2904TZL> SATA
    volume mfid0 (11T) RAID-5 64K OPTIMAL <dionysus> spans:
        array 0

However Disk Utility hangs at "Unmounting disk" in both OS when trying to partition. After that mfiutil stops showing the controller at all. Any ideas what might be going on or how I can fix it? I don't see anything in the logs. Should I try the debug version of your kext?

 

Thanks again!

 

I went ahead and grabbed the debug version. Results here:

Nov 30 16:05:43 hostname com.apple.SecurityServer[16]: Succeeded authorizing right 'com.apple.DiskManagement.Partition' by client '/usr/sbin/diskmanagementd' [519] for authorization created by '/Applications/Utilities/Disk Utility.app' [516] (10000B,0)
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] ProcessParallelTask: Opcode 0x1b, Target 0
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] LogicalDiskCmd
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] Started processing
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] Command queued
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] interruptHandler: pcq vaddr 0xffffff82aef26000
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] pi: 0x14 ci: 0x13
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] ccb: 0
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] mraid_cmd_done
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] ProcessParallelTask: Opcode 0x0, Target 0
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] LogicalDiskCmd
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] Started processing
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] Command queued
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] interruptHandler: pcq vaddr 0xffffff82aef26000
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] pi: 0x15 ci: 0x14
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] ccb: 0
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] mraid_cmd_done
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] ProcessParallelTask: Opcode 0x0, Target 0
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] LogicalDiskCmd
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] Started processing
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] Command queued
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] interruptHandler: pcq vaddr 0xffffff82aef26000
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] pi: 0x16 ci: 0x15
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] ccb: 0
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] mraid_cmd_done
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] ProcessParallelTask: Opcode 0x1b, Target 0
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] LogicalDiskCmd
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] Started processing
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] Command queued
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] interruptHandler: pcq vaddr 0xffffff82aef26000
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] pi: 0x17 ci: 0x16
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] ccb: 0
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] mraid_cmd_done
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] ProcessParallelTask: Opcode 0x2a, Target 0
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] IOCmd: trlen: 131072, lba: 0, blkcnt: 256
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] CreateSGL
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] Paddr[0]: 0x55ccd000
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] genIOVMSegments: nseg 32
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] frame_size: 432, extra_frames: 6
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] Started processing
Nov 30 16:05:44 hostname kernel[0]: [SASMegaRAID] Command queued
Nov 30 16:05:45 hostname com.apple.SecurityServer[16]: Session 100010 created
Nov 30 16:05:47 hostname kernel[0]: [SASMegaRAID] ProcessParallelTask: Opcode 0x0, Target 0
Nov 30 16:05:47 hostname kernel[0]: [SASMegaRAID] LogicalDiskCmd
Nov 30 16:05:47 hostname kernel[0]: [SASMegaRAID] Started processing
Nov 30 16:05:47 hostname kernel[0]: [SASMegaRAID] Command queued
Link to comment
Share on other sites

However Disk Utility hangs at "Unmounting disk" in both OS when trying to partition. After that mfiutil stops showing the controller at all. Any ideas what might be going on or how I can fix it?

This may be a rised problem with 64-bit LBA that was observed on PERC 6. Could you please detach the "dionysus" array, attach a single disk (marked as VD) of any size lower than 2 Tb and test with it? After that do the same using a 2.8 Tb drive from dionysus and report here. Thanks for coop.

Link to comment
Share on other sites

Hello dukzcry,

 

I've seen people say Asus pike 2008 ( 0x00721000 ) not working.

 

You can just tell me if you don't have solutions at this date ?

 

Here is my pci :

04:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03)

Thank you very much.

Link to comment
Share on other sites

justroach,

 

If you'll find time, you may try increasing the numbers of disks in array, starting from two drives and see what size confuses os.

Thanks for the remote access offer, but i think it will not help much for the both of us, as a lot of reboots may be needed and an access to the raid bios, which is much like impossible without network kvm usage.

 

Hi, panpansh!

 

Please see: http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/?p=1910160 and http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/?p=1910165

 

Though a3drv-hba driver is no more accessible. You may ask that Astek company or kubasko person: http://www.insanelymac.com/forum/user/944415-kubasko/ for it.

Link to comment
Share on other sites

justroach,

 

If you'll find time, you may try increasing the numbers of disks in array, starting from two drives and see what size confuses os.

Thanks for the remote access offer, but i think it will not help much for the both of us, as a lot of reboots may be needed and an access to the raid bios, which is much like impossible without network kvm usage.

 

I have a network KVM, I'll get it set up. The size is not the problem. It is something to do with RAID-5 and the driver implementation. See the below. Making a giant RAID-0 works just fine. Thanks so much again for your help and your work.

dionysus:~ lroach$ sudo mfiutil show config
mfi0 Configuration: 1 arrays, 1 volumes, 0 spares
    array 0 of 5 drives:
        drive  0 ( 2795G) ONLINE <ST33000650NS 0001 serial=Z290DDF7> SATA
        drive  1 ( 2795G) ONLINE <ST33000650NS 0001 serial=Z29063E6> SATA
        drive  2 ( 2795G) ONLINE <ST33000650NS 0001 serial=Z29062YC> SATA
        drive  3 ( 2795G) ONLINE <ST33000650NS 0001 serial=Z2904V1V> SATA
        drive  4 ( 2795G) ONLINE <ST33000650NS 0001 serial=Z2904TZL> SATA
    volume mfid0 (14T) RAID-0 64K OPTIMAL <dionysus> spans:
        array 0
dionysus:~ lroach$ df -h
Filesystem      Size   Used  Avail Capacity   iused     ifree %iused  Mounted on
/dev/disk0s2   149Gi  126Gi   22Gi    85%  33118840   5869906   85%   /
devfs          197Ki  197Ki    0Bi   100%       682         0  100%   /dev
/dev/disk4     7.3Ti  3.9Ti  3.3Ti    55% 528028470 448642192   54%   /Volumes/Untitled RAID Set 1
map -hosts       0Bi    0Bi    0Bi   100%         0         0  100%   /net
map auto_home    0Bi    0Bi    0Bi   100%         0         0  100%   /home
/dev/disk5     3.5Gi  3.5Gi    0Bi   100%         0         0  100%   /Volumes/CentOS_6.3_Final
/dev/disk1s2    14Ti  1.5Gi   14Ti     1%     98517 915418406    0%   /Volumes/Untitled 1
Link to comment
Share on other sites

 

I have a network KVM, I'll get it set up. 

 

So this is far more problematic than I thought. The video is mega slow just across town making the interface too laggy to be of much use. I'm going to try out a couple of other ideas, but are there any more troubleshooting steps I can take to maybe get this to work beforehand?

Link to comment
Share on other sites

I was so excited when the phantom partitions that show up after I create a VD got unmounted, but that is about the only change using the new version you posted. Still stuck at "Unmounting disk" and mfiutil still shows nothing after I try to partition using Disk Utility.

 

Just for the heck of it I put Winblows™ 7 on a separate disk and loaded the drivers. I built out a NTFS volume with a GUID partition on the VD. The Tuxera and native OS X NTFS drivers lose their mind trying to access the volume. Not sure if that gives you any more ideas....

 

A giant RAID-0 of all the drives works (15TB) as does a RAID-10 of 4 drives (6TB). If I was a baller I guess I would just roll with RAID-10. Unfortunately I am not.

Link to comment
Share on other sites

Hey Big D,

 

I bought several other cards which appear to work without an issue. Most recently the IBM M5015, LSI 8704ELP and an IBM M1015 with feature key. I would still love to get these H310s working (I bought 10 thinking they would all work). I should have a full remote KVM system for you to play with shortly. Let me know if anything else comes to mind on your side. Thanks so much again!

  • Like 1
Link to comment
Share on other sites

Hey Big D,

 

I bought several other cards which appear to work without an issue. Most recently the IBM M5015, LSI 8704ELP and an IBM M1015 with feature key. I would still love to get these H310s working (I bought 10 thinking they would all work). I should have a full remote KVM system for you to play with shortly. Let me know if anything else comes to mind on your side. Thanks so much again!

Hi,

 

I've never asked you what FW version do you use? Had you tried recent revisions of both Dell or LSI (not officially supported) firmwares?

 

 

IBM M1015
It's uses the same chip as H310. And since M1015 works with RAID5, there's not much i can fix here. Proprietary Windows drivers, i presume, have  some kind of workaround, but all that stuff is closed and is under NDA.
Link to comment
Share on other sites

Hey ppl :)

Big kudos for the work, this is impressive and cool !

 

Just a quick silly question, with your driver there is no chance to make it work on an actual Mac, right ?

TIA :)

 

Hi Billy,

 

I have not played with this driver in particular, but it will likely work in an Intel Mac with one caveat. Because the firmware on the devices have a BIOS Apple's implementation of EFI will not recognize it as a boot device. If you're OK with that I'd bet on it working. I say this based on a number of cards (NIC, HBA, etc.) that I have used from the PC world in my old Intel Powermac.

Hi,

 

I've never asked you what FW version do you use? Had you tried recent revisions of both Dell or LSI (not officially supported) firmwares?

 

dukzcry,

 

The version that came on the cards is newer than anything I can find on Dell's site (they have 20.12.1-002,A02, but the cards have 20.12.2-001. I've tried flashing the firmware back with Dell's utilities for Winbloze™ under Win 7 for the two latest versions they have. They say they completed, but the card disagrees. All of that said Dell's support site is a mess.

 

I'm in the middle of a giant rsync right now, but when that is done I'll toss that Dell card back in there and try from a DOS bootable USB key and see if that works.

 

The only thing I have seen about flashing them with LSI firmware talks about "IT mode". This apparently turns them into a HBA, which is not what I want. Do you have any further experience you could share on this? Any firmware flashing utils under different OS that you think might work with the ROMs that Dell lets you download?

  • Like 1
Link to comment
Share on other sites

 

Hey ppl  :)

Big kudos for the work, this is impressive and cool !

 

Just a quick silly question, with your driver there is no chance to make it work on an actual Mac, right ?

TIA  :)

Thanks, Billy! It should work. Just take into account Justroach's notice regarding UEFI. This thread might help: http://www.insanelymac.com/forum/topic/94679-sas-controllers-w-efi-for-mac-os-x-osx86-solutions/ Creativerig2013 was intended to try, however he hand't come back with report: http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/page-5?do=findComment&comment=1950475 Plz let us know how it will go, if you try.

 

 

I'm in the middle of a giant rsync right now, but when that is done I'll toss that Dell card back in there and try from a DOS bootable USB key and see if that works.

 

The only thing I have seen about flashing them with LSI firmware talks about "IT mode". This apparently turns them into a HBA, which is not what I want. Do you have any further experience you could share on this? Any firmware flashing utils under different OS that you think might work with the ROMs that Dell lets you download?

That's right. More over, IT (and other non-RAID) mode requires other driver, and we don't have such one for OS X.

Sry pal, not much to suggest. When i've played flashing mine, just used an official Dell utility under the DOS. Please don't bother with. I though you might have used either not officially supported LSI firmware or an old Dell firmware, which may behave badly when used under this driver (that's why i've asked), but since you're on recent Dell fw, there is no need to reflash.

  • Like 1
Link to comment
Share on other sites

 

 

Thanks, Billy! Don't see why not. Just take into account Justroach's notice regarding UEFI. This thread might help: http://www.insanelymac.com/forum/topic/94679-sas-controllers-w-efi-for-mac-os-x-osx86-solutions/ Creativerig2013 was intended to try, however he hand't come back with report: http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/page-5?do=findComment&comment=1950475 Plz let us know how it will go, if you try.

 

 

 

OK I will Thx

Link to comment
Share on other sites

  • 3 weeks later...

Hi dukzcty.. many thanks for writing the driver! Its really swung me to the M1015/SAS2008 when building my new system from old second hands parts. I picked up first of all a M1015 card which I tried in my old machine. This worked no problem and got picked up straight away. This card I plan to use in under ESX in my new system. I also got a Supermicro X8DAL-6F board which has an onboard SAS2008. I have just flashed this to LSI9240.

 

I already had installed a Windows 8 and Mavericks to a single SSD using the onboard SATA 1  and am now trying to move the disk to the SAS controller. Before I can expect to boot to Mavericks from the SSD hooked to the SAS controller I am trying to get your kext loaded and working however I am not able to see the onboard SAS2008 controller.

 

Windows tells me that its using vendor id 1000 and device id 0072. I tried editing the info.plist of the kext replacing 0073 with 0072 however I still don't see the onboard SAS.

 

What should I be doing ? and what have I probably done wrong ....

 

Thanks again for the cool cool work  !!!!

Link to comment
Share on other sites

Hi dukzcry,

 

First of all, THANK YOU for this and for your support!

 

Now, I am about to purchase a RAID controller, and don't have many alternatives as my country's customs regulations are c**ppy.

 

But I do have available for purchase at the same price (both with a LSISAS2108 RAID-on-Chip):

  • Lsi 3ware 9750-8i 6gb/s Sata/sas 512mb (which should have oficial support on OSX, but I think it got broken on 10.8.3)

  • Lsi 9260-8i 6gb/s Sata/sas Pci-e 512mb (which according to your README is supported properly being a 92XX)

Let's complicate things a bit more by saying that I am planning to use a couple of 4tb SATA HDDs with the winner in a stripping array on Mavericks (10.9).

 

Do you have any recommendations or comments?

 

Thanks once again and best regards!

Link to comment
Share on other sites

takeawaydave, MrSTiMPy

 

No problemo!

 

Lsi 9260-8i 6gb/s Sata/sas Pci-e 512mb (which according to your README is supported properly being a 92XX)

 

LSI 9260 works. Tested by few persons, one with an original 9260, other with an IBM M5014 and Dell H700 flashed into 9260.

 

 

Let's complicate things a bit more by saying that I am planning to use a couple of 4tb SATA HDDs with the winner in a stripping array on Mavericks (10.9).

 

Dunno about other people's disk layouts, but a man with H700 uses 3TB *4, can't say of what array type though. But, in general, the stripe (RAID 0) array support is good. H310, for example, was tested with a RAID 0 of 15 Gb (3 Tb * 5) which went ok.

Mavericks is supported just as previous releases.

 

Lsi 3ware 9750-8i 6gb/s Sata/sas 512mb (which should have oficial support on OSX, but I think it got broken on 10.8.3)

 

Though the chip is ok, it's not compatible at firmware side with this driver IIRC.

 

I also got a Supermicro X8DAL-6F board which has an onboard SAS2008. I have just flashed this to LSI9240.

Windows tells me that its using vendor id 1000 and device id 0072. I tried editing the info.plist of the kext replacing 0073 with 0072 however I still don't see the onboard SAS.

 

Try the steps kubasko did here and onwards: http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/?p=1908246 There are debug kexts which will match against 0072 i've attached there.

  • Like 1
Link to comment
Share on other sites

Try the steps kubasko did here and onwards: http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/?p=1908246 There are debug kexts which will match against 0072 i've attached there.

 

Thanks - just given this ago with the zip from here. The following kernel messages are printed:

[SASMegaRAID] super->InitializeController
[SASMegaRAID] [Helper] Region starting at 0xfae40000
[SASMegaRAID] Memory mapped at virtual address 0xa502d000, length 8192
[SASMegaRAID] Attach
[SASMegaRAID] Transition_Firmware
[SASMegaRAID] Firmware state: 0
[SASMegaRAID] Waiting for firmware to become ready
[SASMegaRAID] Firmware stuck in state: 0
[SASMegaRAID] Can't attach device
[SASMegaRAID] IOService->free

Seems like the device id's aren't the problem now so thats good :) 

Link to comment
Share on other sites

Seems like the device id's aren't the problem now so thats good :)

 

I'm sorry to disappoint you, but the following means (better to test few times though) that your firmware isn't compatible with a driver. Are you sure you flashed it to a MegaRAID/IR one?

 

Hey one last question: what about FastPath and CacheCade features? I think they are firmware enabled features, but not sure, if enabled on the firmware would the driver suport them?

 

Thanks once again and best regards!!

 

Can't help there. I've never got my hands on a controller with any of these features. Here's mentions of cachecade:

  1. "as i have intel rs2bl which is similar to lsi 9260 i have decided to invest in ssd cache unlock.. but seems it don't work" from http://www.insanelymac.com/forum/user/127707-hotbullet/ Don't know wether he meant that unlock didn't worked, or the "ssd cache" feature failed with this/any driver
  2. CycleBurns was meant to try cachecade on his setup: http://www.insanelymac.com/forum/topic/285197-driver-for-lsi-megaraid-sas-family/?p=1901976 so you may ask him
  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...