Cross-flashing M5015: The latest working LSI-firmware?

Discussion in 'RAID Controllers and Host Bus Adapters' started by Rhinox, May 28, 2013.

  1. Rhinox

    Rhinox Member

    Joined:
    May 27, 2013
    Messages:
    144
    Likes Received:
    24
    First, greetings to all forum-members from passer-by!

    I just obtained IBM M5015 controller and was scared by terribly long boot-time, so I started looking for some info and found this forum by chance. I have a few questions, but please be patient with me, because I'm complete noob concerning cross-flashing, never done this, and never heard about it untill now...

    I would like to flash the latest LSI-firmware (4.10 p2, 12.13.0-0154), but I have read somewhere on this forum some versions can not be flashed on M5015, they simply do not work (oem-controller is detected, or something like that). So my question is:
    Q1: which is the last LSI-firmware version working with M5015?

    Q2: what the hell is "SBR" (or is it SRB)? I have read it must be wiped out and new loaded. Where can I find the new/latest one?

    Q3: That "megarec" tool used for cross-flashing, is it a part of standard LSI-tools (MegaCLI or StorCLI)? If not, where can I find/download it?

    Q4 (which should be probably Q1), please be honest with me and tell me: is there some serious danger I could do something wrong and render the raid-controller completely irreversibely unusable? Did this ever happen to someone?
     
    #1
  2. mobilenvidia

    mobilenvidia Moderator

    Joined:
    Sep 25, 2011
    Messages:
    1,745
    Likes Received:
    37
    You can flash any LSI9260 FW to the M5015, who ever says otherwise is wrong.
    But this will not solve the slow boot.
    You need to flash the SBR from the LSI9260 to the M5015 fooling it into thinking it's no longer a M5015 with slow boot.
    SBR are the OEM settings for the card, it has the card name and some other specific OEM settings
    The SBR cross flashing was locked quite a few versions ago.
    But you can get around this by clearing the flash first then writing the SBR as per below

    I keep the SBR and other files over here

    You'll need to grab what ever FW you want, I've simply had no time to update the files.
     
    #2
  3. Opensupport.it

    Opensupport.it New Member

    Joined:
    Oct 21, 2015
    Messages:
    26
    Likes Received:
    1
    i try to flash my two ibm M5014 controller with last LSI firmware (because they are different release)
    i read this post and using this bootable image (SAS2108 (LSI 9260) based firmware files) and the last LSI firmware from lsi site (12.15.0-0239).

    i change sbr with LSI and all step is ok, no display error on all controller card, but i have a question:

    when i enter in webbios config i see model of controlle is M5014 but i aspect that is 9260...but firmware pkg/version is ok upgraded with LSi version number, is correct or my flashing procedure is wrong?? apparently controller work...

    but before using it in production I would be safe..

    help please!
     
    #3
  4. canta

    canta Active Member

    Joined:
    Nov 26, 2014
    Messages:
    948
    Likes Received:
    168
    the card always says M501X after cross-flashing. this is hardcoded(HW identification) in the card.
    Cross-flashing or not is not a matter on M501X. the card still slows during booting.

    just take two steps: pick IBM(now is lenovo) M501X firmware update or cross-flashing with LSI.
     
    #4
    Last edited: Nov 16, 2015
  5. Opensupport.it

    Opensupport.it New Member

    Joined:
    Oct 21, 2015
    Messages:
    26
    Likes Received:
    1
    Ok i use SAS2008.zip and add last LSI firmware and flash with this after write with Lsi9260 sbr in the zip image..

    i don't use IBM because i don't have again SysOp installed (win o linux) and dos boot disk save me with this operation, and second point LSI is more update


    This operation with LSI firmware in this exemple is cross-flashing for me... (or I did not understand what you mean - Sorry i'm italian :D )

    Make a bootable DOS USB disk
    Place the above files on the USB
    Boot to USB
    Megarec -cleanflash 0
    Reboot to USB
    Megarec -m0flash 0 0xxx_yyy.rom
    Megarec -writesbr 0 sbrzzzzz.bin
    Reboot
    no errors.

    Is all done...Controller work an boot the disk, i think is ok....
    but i don't notice a big difference high speed startup... (better is better...)
     
    #5
  6. canta

    canta Active Member

    Joined:
    Nov 26, 2014
    Messages:
    948
    Likes Received:
    168
    Lsi or IBM firmware onyour card is not matter. The card always slow during booting with lsi or IBM firmware...
    Your card always say 5014 with lsi firmware since this is coded in hardware inside the card.
     
    #6
  7. GabrieleV

    GabrieleV New Member

    Joined:
    May 31, 2015
    Messages:
    6
    Likes Received:
    3
    Please not that latest LSI firmware doesn't allow to crossflash sir, it shows successful but sbr still remains IBM one.

    Check what card model is shown at initialization, initialization times are really different between IBM and LSI.

    You need an older version of firmware, if I remember correctly should be .192
     
    #7
  8. canta

    canta Active Member

    Joined:
    Nov 26, 2014
    Messages:
    948
    Likes Received:
    168
    follow mobilenvidia suggestion.
    basically. sbr cross-flash is no permitted, you need to play hide and seek to do that

    booting msg is different between ibm (oops Lenovo) and lsi..

    the card always recognize as M501X with or without cross-flashing
     
    #8
  9. Opensupport.it

    Opensupport.it New Member

    Joined:
    Oct 21, 2015
    Messages:
    26
    Likes Received:
    1
    #9
    Last edited: Nov 17, 2015
  10. ZicZac

    ZicZac New Member

    Joined:
    Jan 25, 2016
    Messages:
    1
    Likes Received:
    1
    In my case the M5014 is controller 0 (the only one) in the system.
    You can speed up the initialisation in 3 simple steps:

    MegaOEM -AdpSettings Write -f MyM5014.ini -a0

    ...reads MFC_DEFAULT structure and creates an INI file. Inside the INI search for "delayPOST" and change the value. Possible coded values: 0 to 7, which gives a value of 0, 15, 30, 45, 60, 75, 90, 105 seconds.

    MegaOEM -AdpSettings Read -f MyM5014.ini -a0

    ...reads INI file, forms MFC_DEFAULT structure and sends it to the FW.
     
    #10
    lowfat likes this.
  11. bearhntr

    bearhntr New Member

    Joined:
    Feb 29, 2016
    Messages:
    4
    Likes Received:
    0
    I have followed these steps from this URL: SAS2108 (LSI 9260) based firmware files - Projects, Tools, Utilities & Customized INFs

    LSI 9260 based controller Firmware page.

    Here all the latest LSI SAS2108 based FW can be found.
    It includes FW from LSI, IBM, Dell, Oracle, SuperMicro, Fujitsu and Intel.

    sas2108

    How to flash the SAS2108 based cards:

    Make a bootable DOS USB disk (Google it)
    Place the above files on the USB

    Boot to USB
    Megarec -cleanflash 0 (0 = if only one LSI card in computer, you'll need to work out which number to flash if more than one)
    Reboot to USB
    Megarec -m0flash 0 0xxx_yyy.rom (xxx= version number, yyy= OEM version)
    Megarec -writesbr 0 sbrzzzzz.bin (zzzzz= Card type you are trying to flash to, only really needed with M5014/5015)
    Reboot
    Done

    Latest BIOS from Firmware Package 12.12.0-0124
    BIOS 3.25.00_4.12.05.00_0x05180000.00 7/25/20

    Use Megarec or Megacli or MSM to flash to controller, nothing else will be updated only BIOS

    ==========================================[end]

    I have an IBM M5015 controller which was not seeing any HDDs installed in my X3500 (7977) server. I installed a longer cable from the backplane to the controller, and disabled the ONBOARD SAS - as nothing was attached to it. None of the HDDs were seen in the Web Setup tool, although they all lit up on boot up. The server has an IBM ServeRAID 8k-l controller - which is like a DIMM (server does not boot without it installed).

    I was told this was because the HDDs were not IBM and the controller was looking for specific drives. It was suggested that I flash the controller to the 9260-8i. I found the steps above, and performed them exactly.

    Now when I boot the server I am no longer getting the BIOS information for the controller card. I get nothing at all.

    Did I kill my controller? Can it be fixed?

    Please help.

    *BH*
     
    #11
  12. bearhntr

    bearhntr New Member

    Joined:
    Feb 29, 2016
    Messages:
    4
    Likes Received:
    0
    OK ... UPDATE.

    I was able to get my controller to start showing on the boot up....but I am still not seeing my (4) 4TB and (1) 160GB HDDs (when I press CTRL+H) on that prompt; which are on the hotswap backplanes connected to the controller with MINI-SAS to MINI-SAS cables. I had to buy longer ones as the ones which went to the system board were not long enough.

    Any ideas?
     
    #12
  13. lowfat

    lowfat Member

    Joined:
    Nov 25, 2016
    Messages:
    59
    Likes Received:
    54
    :eek:

    Worked like a charm. Went from one minute for the card to initialize to about 5s.
     
    #13
Similar Threads: Cross-flashing M5015
Forum Title Date
RAID Controllers and Host Bus Adapters Cross-flashing an IBM M5014 to LSI 9260 Sep 9, 2012
RAID Controllers and Host Bus Adapters MegaRAID M5015 - How to use non IBM drives? Feb 9, 2018
RAID Controllers and Host Bus Adapters It's time to upgrade my M5015s Aug 31, 2017
RAID Controllers and Host Bus Adapters M5015 cross flash Jun 12, 2017
RAID Controllers and Host Bus Adapters Ibm M5015 and dell Jan 27, 2017

Share This Page