Jump to content

Driver for LSI MegaRAID SAS family

RAID LSI

  • Please log in to reply
358 replies to this topic

#221
dukzcry

dukzcry

    Retired

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

bilbo,

 

Had you tried to do initial setup using card BIOS and not lsi program for windows (preferably using default volume settings for the test time)? Better to do fast init to avoid waste of time. What if you set PreferMSI=false in kext plist properties, does it improve anything? Just in case...

 

 

I've seen on one previous post one capture showing a more recent firmware.. Should I update the firmware?

You may try. You may also contact the person with a card of subject and ask about settings etc.

 

 

Log seem miss the BBU ????? I dont have battery.

Then you should just ignore the error.



#222
bilbo

bilbo

    InsanelyMac Protégé

  • Members
  • PipPip
  • 72 posts

After tests and tests ,I finally found a workaround to got Raid working. 

 

1- I re- configured the raid, using raid bios. I used sighly different settings changing write policies , but anything important. 6 disks in raid 5.

 

2- I reboot on win and mac. Both systems detect new volume. Both show me the dialog to initializate. I decide do it in Windows, with windows disk utlity. Just initializate. Not partitions.

 

3- I reboot and mac. All OK. Disk utility can see volume

 

4- Again in windows, I did the partitions. Two partitions in my case. With nfts FS.

 

5- Rebooting in Mac ... Bingo. Everything seems OK.

 

Now. On mac, with disk utility, I delete the volume , partitioning it again. So disk utility writes again partition table. I use gpt, of course. Result at next boot:  Boot procces stops again at LSI bios loading :surprised: . No way.

 

-I discovered I didn't need disconnect HD to acces bios. I need just press ctrl-H before of bios card load process, and keep it pressing. Again, I repeat whole process.

 

- Again on point 5, I try to avoid make partitions. Just format. But I can't do it. But I get "can't erase (mediakit reports not enough space on device for requested operation)" error.

 

- I decide do all process in windows. One important thing here. On my prevoius post I explained that mac could't see volume on my second try. I used one utility on windows to make "exotic" partitions and format (I need exfat and ext3). Now I think this utility was the guilty. So I decide be carefull with this kind of utilities. After think about that I decide trust in gparted. I reboot using a live ubuntu , I format one of my partitions in ext3. Always without touch volume structure. Just format. I haven't found a trustly way to format in exfat , so I decide use nfts for the other partition and use paragon nfts in mac.

 

-Everything is ok. I have my Raid mounted on mac. First test give me similar read/write results than in Win. I have to test it working.

 

In short: Bios LSI doesn't like how mac disk utility makes table partition and/or structure. I realize it is sighly different than in windows (different first primary partition size ).

 

My workaround: perform raid in bios card > Initialize and make the partitions just using windows disk utiliy> Use gparted to format partitions if use HFS or exotic FS, always without touch table partition, just to format.

 

.

.

.

.

.

 

... and I have to express my gratitude to dukzcry. To have my raid working is my fundamental to my hackintosh project. It doesn't make sense without a raid. Using LSI card is important for me because these are the supported card on my workstations, needed to keep compatibilitie with linux too ( I use linux on my workstation too!!) . Use LSI card on mac was my dream. Same raid with win/mac/linux. So thank you , duckzcry, for waste your time ....  ;)  :)



#223
jfive

jfive

    InsanelyMac Protégé

  • Members
  • Pip
  • 27 posts

Thank you soooo much DuckCrzy for creating and maintaining this project and your thread for so many years. Thanks to your work, I was able to successfully to get my rig running without any issues.

 

I'd like you or someone smarter myself, to comment on how to deal with TRIM to an SSD RAID-1 VD in relation topics within this thread. I did add the Chimera plugin for 10.10 but not seeing TRIM enabled in SCSI drive info in System Information. And yea, TRIM is activated with Samsung 840-Pro 128 & 256 SSDs connected to motherboard SATA ports.

 

http://www.anandtech.com/show/6161/intel-brings-trim-to-raid0-ssd-arrays-on-7series-motherboards-we-test-it

 

Relevant items in my rig:

OSX Yosemite 10.10

i7-4770k on GA-Z87-UD4H, F9

Dell PERC H700 FW 12.10.06

-> 2x Western Digital 1TB WD1003FZEX 1TB in RAID-1

-> 2x Intel 530 128GB SSD in RAID-1 (this is my boot drive for OS X Yosemite; built w/ Chimera)



#224
dukzcry

dukzcry

    Retired

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

Thank you soooo much DuckCrzy for creating and maintaining this project and your thread for so many years. Thanks to your work, I was able to successfully to get my rig running without any issues.

 

I'd like you or someone smarter myself, to comment on how to deal with TRIM to an SSD RAID-1 VD in relation topics within this thread. I did add the Chimera plugin for 10.10 but not seeing TRIM enabled in SCSI drive info in System Information. And yea, TRIM is activated with Samsung 840-Pro 128 & 256 SSDs connected to motherboard SATA ports.

 

http://www.anandtech.com/show/6161/intel-brings-trim-to-raid0-ssd-arrays-on-7series-motherboards-we-test-it

 

Relevant items in my rig:

OSX Yosemite 10.10

i7-4770k on GA-Z87-UD4H, F9

Dell PERC H700 FW 12.10.06

-> 2x Western Digital 1TB WD1003FZEX 1TB in RAID-1

-> 2x Intel 530 128GB SSD in RAID-1 (this is my boot drive for OS X Yosemite; built w/ Chimera)

Unfortunately, i don't have experience with SSD, TRIM and RAID controllers which support TRIM. But to say simple, my driver doesn't tamper into the communication between OS and virtual drives, except for some wrapping. So, OS X should see what your controller gives it.

In my understanding, if your SSD drives provide TRIM, H700 supports TRIM and it doesn't require an additional support from the driver, then it should function, otherwise - no go.



#225
jfive

jfive

    InsanelyMac Protégé

  • Members
  • Pip
  • 27 posts

H700 supports TRIM [ ...] - no go.

 

That statment is correct. Just two minutes ago, I read the H310 is the one that plays nice with TRIM. However the H310 doesn't have CacheCade but the H700 (int-dual SFF-8087) does have CacheCade. I assume this has something to do with the fact TRIM is a function/facility of the OS and won't be able to work itself into the adapter's "virtual disks." Non-RAID SSDs may be has OS TRIM support but I'm no expert.

 

I would very much like to pay you a small bit for what you've done here. Not a rich man but will happily pay for something that was critical to a personal project. If not you, I'll gladly make a donation in your "name" to a charity of your choice that accepts PayPal.

 

Here's a easy list but only US-based groups: https://www.paypal.c...pp/search-cause



#226
jfive

jfive

    InsanelyMac Protégé

  • Members
  • Pip
  • 27 posts

Sent you some change man. Thanks again for everything.

 

PayPal Payment Sent (Unique Transaction ID # 97****72XE69****4P)



#227
dukzcry

dukzcry

    Retired

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

Sent you some change man. Thanks again for everything.

 

PayPal Payment Sent (Unique Transaction ID # 97****72XE69****4P)

Got it! Thank you much for your help pal :)

P.S.: In Russia with it's current situation, it's the money!



#228
agatek

agatek

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts

Dukzcry, thank you for your efforts to develop the driver. I tried to load it, got a message about firmware fault, upgraded the firmware and fell into more serious troubles. I am not giving any details here because I have a more basic question. I've been trying to make OSX to boot from PowerEdge 1950 gen II directly from a PERC5/i SAS hdd. Is it possible at all? As far as I know the said Dell has no (u)efi. In similar situation to boot it from Linux I would need to have the driver inside the kernel. Is it the same for OSX (seems it should be)?



#229
dukzcry

dukzcry

    Retired

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

Dukzcry, thank you for your efforts to develop the driver. I tried to load it, got a message about firmware fault, upgraded the firmware and fell into more serious troubles. I am not giving any details here because I have a more basic question. I've been trying to make OSX to boot from PowerEdge 1950 gen II directly from a PERC5/i SAS hdd. Is it possible at all? As far as I know the said Dell has no (u)efi. In similar situation to boot it from Linux I would need to have the driver inside the kernel. Is it the same for OSX (seems it should be)?

 

Hmm, that's strange. Both E and I versions of PERC 5 cards with either LSI or Dell firmware worked for people, and I still use PERC 5/E w LSI 7.0.1-0083.

Yes, it's possible if not that "firmware fault" issue. Whether BIOS or EFI is not matter, even if your server had EFI with a driver for your RAID card, this would only mean a support for your card in EFI environment, while OS X still need it's own.

For OS X it's almost the same, os will autoload the SASMegaRAID.kext (kernel extension, or kernel module in terms of linux) RAID driver before the stage of looking for a root device. For this the kext should be in kernel cache (you may run this utility once after the driver installment, just for sure it's in). Plus with Yosemite (preferably with Mavericks too) you need to use 'kext-dev-mode=1' boot option.



#230
agatek

agatek

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts

Thanks dukzcry for your response. I simply and apparently wrongly assumed efi could provide sort of translation layer but if not, I agree. For the earlier problem it was like this:
I was trying to install 10.10 booting from the Niresh'es 10.10 distribution usb img. I booted with the argument you suggested (kext-dev-mode=1 – as far as I can see it is enabled in this distribution by default) copying the kext to /System/Library/Extensions. I tried two kexts mentioned in this thread, one of MRSTIMPy and the other of yours (full debug, output below). Both failed with the message indicating a firmware problem:

Nov 15 02:45:38 localhost kernel[0]: [SASMegaRAID] InitializeController
Nov 15 02:45:38 localhost kernel[0]: [SASMegaRAID] [Helper] Region starting at 0xfc320000
Nov 15 02:45:38 localhost kernel[0]: [SASMegaRAID] Memory mapped at virtual address 0x93205000, length 8192
Nov 15 02:45:38 localhost kernel[0]: [SASMegaRAID] Attach
Nov 15 02:45:38 localhost kernel[0]: [SASMegaRAID] Transition_Firmware
Nov 15 02:45:38 localhost kernel[0]: [SASMegaRAID] Firmware state: 0xf0000000
Nov 15 02:45:38 localhost kernel[0]: [SASMegaRAID] Waiting for firmware to become ready
Nov 15 02:45:38 localhost kernel[0]: [SASMegaRAID] Firmware fault
Nov 15 02:45:38 localhost kernel[0]: [SASMegaRAID] Can't attach device
Nov 15 02:45:38 localhost kernel[0]: [SASMegaRAID] IOService->free

The controller has two SAS hdds attached. It booted (still does it after fw upgrades) with no issue both Linux and Win7.
Package 5.1.1.-0040
FW ver. 1.03.10-216
Bios ver. MT28
CtrlR ver. 1.04-107A
Boot blk ver. R.2.3.12
 
This firmware was upgraded to
Package 5.2.2.-0072
FW ver. 1.03.50-0461
Bios ver. MT28-9
CtrlR ver. 1.04-019A
Boot blk ver. R.2.3.12

The PE1950 main bios was upgraded to 1.10 2.20 from 1.4.x (IIRC because I was stupid enough not to write it down).

Now, after upgrading the booting (usb thumbdrive) ends up for both .9 and .10 with the same kernel panic: "can't perform kext scan" but here goes some observations:
- it is not instant, it clearly reads the /System/Library/Extension (at least for .10) so it looks like after a kext gets injected something gets *beep*
- .9 boots well to the installation screen if:
    i) it boots from optical usb drive
    ii) (sometimes, I can't figure out the pattern) it boots well from the thumbdrive but an optical drive with .9 has to be present (in this case the OD blinks maybe 2 times only during the whole installation process)
As I am very novice to OS X not sure if the following is valid, but it seems to me something interferes with the USB thumbdrive/(er) during the boot time so in some point the file system on the drive is not present/mounted any longer. Could this be the case of “Can't perform kext scan”?

I guess now I will try to do it all more proper way not using the ready distributions but through the guidelines found on this website.



#231
dukzcry

dukzcry

    Retired

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

agatek,

 

Could you detach all your sas drives from the controller, will you still have a firmware fault after that?



#232
agatek

agatek

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts

agatek,

 

Could you detach all your sas drives from the controller, will you still have a firmware fault after that?

 

I will do it but I need some time to learn how as the earlier option (10.10) does not work any longer after the FW upgrade.



#233
dukzcry

dukzcry

    Retired

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

I will do it but I need some time to learn how as the earlier option (10.10) does not work any longer after the FW upgrade.

 

You could try to go with optical 10.9, to save your time at this point. After installer is loaded, you can open Terminal and load my kext directly right on this stage by issuing kextutil -v /path/to/SASMegaRAID.kext. It can be lied for example on usb stick. If it's a non-hfs+ formatted usb drive, then you'll need to do cp -r /Volumes/usbstickname/SASMegaRAID.kext /some/writable/path/probably//tmp; chown -R root:wheel /some/writable/path/probably//tmp/SASMegaRAID.kext; kextutil -v /some/writable/path/probably//tmp/SASMegaRAID.kext

 

P.S.: If you'll need to upgrade your os to the 10.10, then it could be easily done after installing clover or bareboot bootloader. After that you'll just need to download appstore os image, next you run install from there and all should go fine, without any need for usb sticks or other media.



#234
agatek

agatek

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts

Sorry for my much delayed response. Hectic period and nothing goes as planned.

I don't have kextutil on any of the bootable distribution I manage to boot. Only kextload that fails with the message that I should use kextutil. I can hardly comprehend this booting chaos. Now I can boot Hackintosh Yosemite from BD (that I burnt from iso supposingly for a VM) but only if I boot it from a Niresh 10.8.5 thumbdrive distro.

It tried to follow: http://www.insanelym...dated-10162014/ but it does not boot at all from such prepared thumbdrive,

 

PE1950 has one SATA port. I am going to hook up a sata hdd to it and see if I can install some bootable OSX on it. This should give me more freedom to play around with your SAS kext.



#235
agatek

agatek

    InsanelyMac Protégé

  • Members
  • Pip
  • 7 posts

Reporting success (as of the SAS driver).

  1. I activated the SATA port and hooked up a sata 2.5" hdd.
  2. Installed 10.8.5 from Niresh distro (this is the only one I managed to install so far. Niresh 10.9 panics, Hackintosh 10.10 installs but after rebooting it just hangs forever - still working on it). To boot it I needed the 10.8.5. installation thumbdrive (with Clover) and after it is loaded I have to execute efi boot to the SATA drive that brings you back (failing?) to the Clover boot screen again and only after this it boots as it should from the non-efi oprion.
  3. When I had it up and running I just installed (installer application) the duckzcry's release package and it did the job perfectly - all SAS drives become visible.
  4. Under Linux (sorry, feel more comfortable) I partitioned the SAS drive for the SATA 10.8.5 partition to fit (same size etc), and transferred it by simple dd if/of.
  5. I run grub installer under Linux to update the bootloader on the SAS bootable drive.
  6. Booted as per normal via grub menu with the exception that it stopped recognizing the video card (? - I have it at fixed 640x480 now with no options to chose and no specific card info under the system-information respective screen). Another thing I don't get, when I booted it from the SATA drive OS X recognized 3.02GB RAM only (4GB physical, ATI ES1000 16MB allocated). Booting it from SAS it recognized 4GB.

Besides the graphics, the ethernet cards are not yet working.

 

(Dell PowerEdge 1950II, 2x Quad Core E5345@ 2.33GHz, 4GB, 2x SAS 2.5" on iPERC5. More details in my earlier posts in this thread.)



#236
glow9

glow9

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts
  • Gender:Not Telling
  • Location:Berlin
  • Interests:Mac Graphics Animation Design

After I tried different things with my LSI 8708EM2 and your driver I am stuck so I decided to poste here.

I recently switched to 10.9.5 and Clover on a new Harddrive. Windows 7 is on seperate MBR-HD and older Chameleon OSX installs are on a third HD.

 

I set up Raid 5 in Web Bios and initialize a virtual drive there. Partition HFS+ in Mavericks. After reboot Raid is still there. After booting to an older OSX installation and then rebooting to Mavericks and/or Windows the Raid does not show up in Finder or in System Information / Parallel SCSI anymore but is still there in terminal mfiutil:

 

mfi0 Adapter:
    Product Name: MegaRAID SAS 8708EM2
   Serial Number: P0xxxxxxxx
        Firmware: 11.0.1-0048
     RAID Levels: JBOD, RAID0, RAID1, RAID5, RAID6, RAID10, RAID50
  Battery Backup: not present
           NVRAM: 32K
  Onboard Memory: 128M
  Minimum Stripe: 8K
  Maximum Stripe: 1M

mfi0 Volumes:
  Id     Size    Level   Stripe  State   Cache   Name
 mfid0 ( 2791G) RAID-5      64K OPTIMAL Disabled <hallo1>

mfi0 Configuration: 1 arrays, 1 volumes, 0 spares
    array 0 of 4 drives:
        drive 34 (  932G) ONLINE <Hitachi HDS72101 A3MA serial=JP2921Hxxxxxxx> SATA
        drive 35 (  932G) ONLINE <Hitachi HDS72101 A3MA serial=JP2940Hxxxxxxx> SATA
        drive 36 (  932G) ONLINE <Hitachi HDS72101 A3MA serial=JP6960Hxxxxxxx> SATA
        drive 37 (  932G) ONLINE <Hitachi HDS72101 A3EA serial=JP6921Hxxxxxxx> SATA
    volume mfid0 (2791G) RAID-5 64K OPTIMAL <hallo1> spans:
        array 0

mfiutil show events -c info boot
43345 (boot + 3s/CTRL/info) - Firmware initialization started (PCI ID 0060/1000/1013/1000)
43346 (boot + 3s/CTRL/info) - Firmware version 1.40.342-1650
43347 (boot + 3s/CTRL/info) - Board Revision
43348 (boot + 17s/DRIVE/info) - Inserted: PD 22(e0xff/s34)
43349 (boot + 17s/DRIVE/info) - Inserted: PD 22(e0xff/s34) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=707e895893bfffb3,0000000000000000
43350 (boot + 17s/DRIVE/info) - Inserted: PD 23(e0xff/s35)
43351 (boot + 17s/DRIVE/info) - Inserted: PD 23(e0xff/s35) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=7087875b99bddfad,0000000000000000
43352 (boot + 17s/DRIVE/info) - Inserted: PD 24(e0xff/s36)
43353 (boot + 17s/DRIVE/info) - Inserted: PD 24(e0xff/s36) Info: enclPd=ffff, scsiType=0, portMap=02, sasAddr=708786328ae3fcbc,0000000000000000
43354 (boot + 17s/DRIVE/info) - Inserted: PD 25(e0xff/s37)
43355 (boot + 17s/DRIVE/info) - Inserted: PD 25(e0xff/s37) Info: enclPd=ffff, scsiType=0, portMap=03, sasAddr=70718739a0d6eab8,0000000000000000
mfiutil: Failed to fetch events: Input/output error

 

All this info is displayed in terminal while the raid is not vissible to the finder/diskutility/system information.

Any idea what I can try to make the raid show up again in finder?
 



#237
glow9

glow9

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts
  • Gender:Not Telling
  • Location:Berlin
  • Interests:Mac Graphics Animation Design

I reconfigured the Virtual Disk as Raid 0 but still no luck. Disk Utility detects the device on first boot. After a reboot the drive is gone and the controller is not recogniced under System Information/Parallel SCSI. But is still there in the bootsequence and mfiutil.No matter whether I use clover or Chameleon. I am about to give up.



#238
jasonhill1981

jasonhill1981

    InsanelyMac Protégé

  • Members
  • Pip
  • 2 posts
  • Gender:Male

Hello, I have been reading throught this post great work !

 

My question is does this driver work with this card LSI/3ware 9650SE-12ML and Mac OSX 10.9 and 10.10 ?
Link to Card



#239
dukzcry

dukzcry

    Retired

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

glow9, it's a strange issue, never heard of anything similar. Maybe it's something wrong with your setup. The only option of this kext that can affect controller visibility is in the FAQ:

Q: The driver loads but my device doesn't show up in profiler. What should i do?
A: ...
If it's not a case, try inverting "PreferMSI" key value. It's under "Settings" dictionary in kext's plist.

upd: Good, so it's that not very common case, when message signaled interrupts doesn't work well for some setup.

 

jasonhill1981,

Hi! No it's not supported. However, an ancient 3ware controllers (8000 series) are supported by this project: https://github.com/r...older/osx-3ware Though i can't recommend to use any of them.



#240
glow9

glow9

    InsanelyMac Protégé

  • Members
  • Pip
  • 3 posts
  • Gender:Not Telling
  • Location:Berlin
  • Interests:Mac Graphics Animation Design

duczkry, Success: after setting „PreferMSI“ to NO the raid shows up all the time in profiler. Thank you so much for your time and effort.








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