Jump to content

Driver for LSI MegaRAID SAS family

RAID LSI

  • Please log in to reply
363 replies to this topic

#121
dukzcry

dukzcry

    Retired

  • Members
  • PipPipPip
  • 138 posts
  • Gender:Not Telling

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.insanelym...mily/?p=1908246 There are debug kexts which will match against 0072 i've attached there.



#122
takeawaydave

takeawaydave

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 203 posts
  • Gender:Male
  • Location:Switzerland

Try the steps kubasko did here and onwards: http://www.insanelym...mily/?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 :) 



#123
MrSTiMPy

MrSTiMPy

    InsanelyMac Protégé

  • Members
  • Pip
  • 22 posts

Thanks man!! Will most likely purchase the 9260, test and post results!

 

Cheers!



#124
MrSTiMPy

MrSTiMPy

    InsanelyMac Protégé

  • Members
  • Pip
  • 22 posts

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!!



#125
dukzcry

dukzcry

    Retired

  • Members
  • PipPipPip
  • 138 posts
  • Gender:Not Telling

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.insanelym...7707-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.insanelym...mily/?p=1901976 so you may ask him


#126
MrSTiMPy

MrSTiMPy

    InsanelyMac Protégé

  • Members
  • Pip
  • 22 posts
i will be testing SSD Cachecade on this setup and migrating both windows and mac to new disks soon.
If there's anything worthy reporting, i'll let you know.

 

 

Hey CycleBurns, did you have any luck with the CacheCade? Thanks!!


 

CycleBurns was meant to try cachecade on his setup: http://www.insanelym...mily/?p=1901976 so you may ask him

 

Just sent him a private msg, but seems he was last online on June 2013... so I maybe out of luck...

Also, I am about to test my 9260, will let you know my findings!

 

Thanks for everything man!


Another question sir...

 

Sorry I am a bit of a bugger...

 

Do you suggest upgrading to the latest firmware?

 

Thanks!



#127
MrSTiMPy

MrSTiMPy

    InsanelyMac Protégé

  • Members
  • Pip
  • 22 posts

OK, I am back to report my results... BIG SUCCESS!! :drool:

 

Screen Shot 2014-01-13 at 11.12.51 PM.png

 

Tomorrow I will install the cache battery... Crossing my fingers to get a reply from any of the guys with CacheCade and Fastpath...

Attached Files



#128
dukzcry

dukzcry

    Retired

  • Members
  • PipPipPip
  • 138 posts
  • Gender:Not Telling

Do you suggest upgrading to the latest firmware?

 

I would say yes, unless the latest FW breaks things for you.

 

OK, I am back to report my results... BIG SUCCESS!! :drool:

Tomorrow I will install the cache battery... Crossing my fingers to get a reply from any of the guys with CacheCade and Fastpath...

 

Good!



#129
dogmaphobic

dogmaphobic

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts
  • Gender:Male

Success with an Intel RT3WB080 Raid Controller.

 

I had one not being used and it didn't even occur to me to try on Mac OS. A quick google search (well, not so quick as I had to first find out to look for "MegaRaid") brought me here. Downloaded the kext, booted and it all came right up.

 

I have it with 4 2TB drives in Raid 5. When I first booted the disk was automatically mounted with its original NTFS partition and all files accessible. I reformatted and I am now in the process of restoring data into it.

 

A huge thanks for the effort!

 

The only question I have: Is there a way to have S.M.A.R.T. support?

 

Thanks!

 

 

Attached Files



#130
dukzcry

dukzcry

    Retired

  • Members
  • PipPipPip
  • 138 posts
  • Gender:Not Telling
 

Success with an Intel RT3WB080 Raid Controller.

 

An interesting controller you have, can find almost nothing about it :)

 

The only question I have: Is there a way to have S.M.A.R.T. support?

 

You can't see it directly in the OS, but you can monitor physical drives status as well as many other parameters using a console 'mfiutil' tool. Both utility and manpage are installed along with a kext.

 

Have fun!



#131
dogmaphobic

dogmaphobic

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts
  • Gender:Male

I got it from newegg a few years ago. They still have it listed: http://www.newegg.co...N82E16816117214

 

I had read something about mfiutil in passing but had not paid close attention to it. Thanks for pointing it out. I can't however, get the events (what I think it would be what I'm looking for). The config comes up OK:

 

>sudo mfiutil show config
mfi0 Configuration: 1 arrays, 1 volumes, 0 spares
    array 0 of 4 drives:
        drive  4 ( 1863G) ONLINE <WDC WD2002FAEX-0 1D05 serial=WD-WCAY000xxxx> SATA
        drive  5 ( 1863G) ONLINE <WDC WD2002FAEX-0 1D05 serial=WD-WCAY000xxxx> SATA
        drive  6 ( 1863G) ONLINE <WDC WD2002FAEX-0 1D05 serial=WD-WCAY000xxxx> SATA
        drive  7 ( 1863G) ONLINE <WDC WD2002FAEX-0 1D05 serial=WD-WCAY000xxxx> SATA
    volume mfid0 (5585G) RAID-5 256K OPTIMAL spans:
        array 0
 
The events cause an I/O error (edited with proper output):
 
> sudo mfiutil show events 1
<... snip ...>
12884 (Sat Jan 19 08:18:19 EST 2013/DRIVE/WARN) - Command timeout on PD 00(e0xfc/s3) Path 4433221100000000, CDB: 2f 00 a2 66 90 00 00 10 00 00
12885 (Sat Jan 19 08:18:19 EST 2013/DRIVE/WARN) - PD 00(e0xfc/s3) Path 4433221100000000  reset (Type 03)
mfiutil: Failed to fetch events: Input/output error
For what's worth, here is the log sequence:

 

>sudo mfiutil show logstate
mfi0 Event Log Sequence Numbers:
  Newest Seq #: 18575
  Oldest Seq #: 1
   Clear Seq #: 2
Shutdown Seq #: 18562
    Boot Seq #: 18563
 

Thanks!



#132
dukzcry

dukzcry

    Retired

  • Members
  • PipPipPip
  • 138 posts
  • Gender:Not Telling

I can't however, get the events (what I think it would be what I'm looking for). 

The events cause an I/O error (edited with proper output):
> sudo mfiutil show events 1
<... snip ...>
12884 (Sat Jan 19 08:18:19 EST 2013/DRIVE/WARN) - Command timeout on PD 00(e0xfc/s3) Path 4433221100000000, CDB: 2f 00 a2 66 90 00 00 10 00 00
12885 (Sat Jan 19 08:18:19 EST 2013/DRIVE/WARN) - PD 00(e0xfc/s3) Path 4433221100000000  reset (Type 03)
mfiutil: Failed to fetch events: Input/output error

 

By default, you're seeing only warning messages from the event log. If you need to see more, point to an appropriate class, like 'mfiutil show events -c info 1'. Classes are described at man page.

Just ignore I/O errors you'll see at the end of output, there's nothing to worry about. The reason is that mfiutil is written specially for FreeBSD's mfi driver, while this one is totally different from it.

 

For what's worth, here is the log sequence:

 

>sudo mfiutil show logstate
mfi0 Event Log Sequence Numbers:
  Newest Seq #: 18575
  Oldest Seq #: 1
   Clear Seq #: 2
Shutdown Seq #: 18562
    Boot Seq #: 18563

 

Instead of figuring out log entry numbers with 'logstate' cmd you may use aliases (see man for them). 'mfiutil show events -c info boot' for example.



#133
drowsyhaze

drowsyhaze

    InsanelyMac Protégé

  • Members
  • Pip
  • 35 posts
  • Gender:Male

Hey dukzcry, I have an LSI 9750-4i - I've read here that this driver isn't compatible because the firmware isn't, even though this family of cards uses the same processor. Is this true? Is there any workaround? I spent a lot of money on this card and would hate to have to buy another for 10.9 compatability.

 

I tried using the 9750-4i4e driver which is supposedly compatible through 10.8, having read it was broken in 10.8.3, but no dice. All drivers recognize an unformatted array but will not allow me to partition. Maybe I could inject the PCI-ID of the 4i4e into the DSDT and get results?

 

I may try gparted today to partition, but I understand that 10.9 still won't be able to mount the disk due to PCI-EFI not being available on the card's firmware.

 

I am using chameleon 2.2.1 if that's relevant.

 

Anyway, thanks so much for all of your hard work on this project, hope to hear from you soon!



#134
Shane 2

Shane 2

    InsanelyMac Protégé

  • Members
  • Pip
  • 19 posts
  • Gender:Male

I've been using your driver for a few days, and an issue has showed up.

 

Whenever I start Disk I/O on one of the partition/drive, I got sound assertion. This is my test routine:

 

a ) Clean boot.

b ) I start my music app and watch the console - Nothing

c ) I copy a file from one of the RAID drive to another drive

d ) sound assertion.

 

The console message about the assertion is this:

 

2014/1/17 上午3:45:18.000 kernel[0]: Sound assertion - 8086:8c20 FIFO error (Stream 7)
 
Is everyone experiencing similar problem or is it just me?
 
Is there other possibility for this to happen, how can I test it?
 
Beside using the Debug version of the kext which I will do after this weekend, what else can I do to help?


#135
dukzcry

dukzcry

    Retired

  • Members
  • PipPipPip
  • 138 posts
  • Gender:Not Telling

Hey dukzcry, I have an LSI 9750-4i - I've read here that this driver isn't compatible because the firmware isn't, even though this family of cards uses the same processor. Is this true? Is there any workaround? I spent a lot of money on this card and would hate to have to buy another for 10.9 compatability.

Maybe I could inject the PCI-ID of the 4i4e into the DSDT and get results?

 

drowsyhaze, it seems to be true :( But isn't it possible to flash it with LSI 9261-4i firmware (or whatever card has the same hardware)?

As for DSDT i dunno. You may try.

 

 

I've been using your driver for a few days, and an issue has showed up.

 

Whenever I start Disk I/O on one of the partition/drive, I got sound assertion. This is my test routine:

 

a ) Clean boot.

b ) I start my music app and watch the console - Nothing

c ) I copy a file from one of the RAID drive to another drive

d ) sound assertion.

 

The console message about the assertion is this:

 

2014/1/17 上午3:45:18.000 kernel[0]: Sound assertion - 8086:8c20 FIFO error (Stream 7)
 
Is everyone experiencing similar problem or is it just me?
 
Is there other possibility for this to happen, how can I test it?
 
Beside using the Debug version of the kext which I will do after this weekend, what else can I do to help?

 

Not me at least. You may try to disable all third-party kexts you're not urgently need, and retest.

You may also try changing driver parameters in plist. For example disable MSI.

 

P.S.: Do you use an AppleHDA? You may try VodooHDA instead if it supports your sound.



#136
Shane 2

Shane 2

    InsanelyMac Protégé

  • Members
  • Pip
  • 19 posts
  • Gender:Male

I am using AppleHDA for now. I will try to disable unnecessary kexts and try. Thanks!



#137
bichobola

bichobola

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts

Hi. First thanks for the MegaRaid SAS kext. Now I can use my fujitsu d2616 (SAS2108) in OSX Mavericks 10.9.1!!

I have only a little problem. Now OSX can't sleep, the monitor goes off, but the computer remains enabled.

¿Anyone know a workaround?

 

Thanks.



#138
dukzcry

dukzcry

    Retired

  • Members
  • PipPipPip
  • 138 posts
  • Gender:Not Telling

Hi. First thanks for the MegaRaid SAS kext. Now I can use my fujitsu d2616 (SAS2108) in OSX Mavericks 10.9.1!!

I have only a little problem. Now OSX can't sleep, the monitor goes off, but the computer remains enabled.

¿Anyone know a workaround?

 

Thanks.

 

I'm sorry, but i was forced to add a hack to this driver which prevents the system from going to sleep. The reason is that i'm getting data corruption of boot volume and/or kernel panic on either wakeup or next boot after sleep->wakeup was made, when i'm booting OS from the drive attached to a controller (if i'm booting from a drive not handled by this driver, everything is ok). I've tried to fix this, but nothing helped so far.

I'll send you kexts with this hack disabled via PM, if you mind to check, maybe you got another experience... But, as a disclaimer, you'll need to disconnect all volumes with valuable data, and move your OS X boot drive to an internal controller.

 

P.S.: Note that round a minute should pass after the wakeup before you'll can access your drives.



#139
bichobola

bichobola

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts

Thanks a lot dukzcry. My boot hd is in another controller, and the minute for controller's wakeup is a normal behavior (under windows).

I'm going to try it.

Thanks, thanks and thanks again.



#140
CycleBurns

CycleBurns

    InsanelyMac Protégé

  • Members
  • Pip
  • 25 posts

Hey dukzcry,

 

i just can't thank you enough!

i am actually happy to see more and more people enjoying your work :) 

 

I've been using your kext for a while, and i sort of found a small issue.

 

 

It has to do with the visibility of the virtual disks, which is ' sort of' associated with the internal enumeration of the virtual disks.

Let me explain; In windows you always see all virtual disks. In OSX this depends. It depends on the availability of the disks PREVIOUS to the actual disk number on which your install is located.

I encountered this a while ago, when i just started, but disregarded it (after finding out what it was) to the firmware.

In the latest firmware update an issue was solved that implied the same behaviour. But now i encounter it again.

The situation is always the same; when i migrate to new disks. I found out because AFTER migrating an install, it would work.... untill i removed old disks (and associated virtual disks weren't available.

 

when i suspected to understand this behavior, i made new virtual disks (in WebBios), and since a new VD0 was available, the boot worked.

It appears that the enumeration of disks must be continous, or else it will not show the rest of the disks... IMPORTANT; Remember that if you remove disks (not deleting the virtual disks on the physical disks) the controller will remember them, causing 'gaps' in your VD enumeration.

 

 

See the image attached; for some reason ID 7 doesnt have the 'MFID' string prefixed, and the partition on this VD are not visible.

I suspect because there are no disks ID's 5 and 6 available. Similar situation can/will happen when you migrate your install from existing disks (hosted by the controller) to other disks on the controller.

I haven fully tested all possible scenario's, and once aware you can ' circumvent' this more or less, but i thought you (and others) might like to know.. 

 

Off course i might be mistaken, but i think this is worth checking out....

 

 

 

Attached Files








0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2016 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy