It's tech, that matters!

48 thoughts on “SAS HBA crossflashing or flashing to IT mode, Dell Perc H200 and H310

  1. On my motherboard (Asus Rampage III Extreme, X58), inserting a reflashed (IT) Dell Perc H310 disables memory slot B1. So at least one DIMM is “lost” and the system memory count goes down.
    Taping over pins B5/B6 solves the problem.
    Hopefully this will prevent some people from pulling their hair out 😉

  2. I have two cards flashed with this method and they only detect one drive (out of 5 plugged in), what can be causing this?

    I also stopped at the 6GBSASHBA step as trying to flash 2118it.bin resulted in “cannot flash from IR to IT” (or something similar).

    1. Are you sure you have the right cable? I’ve seen that happen when people use a reverse breakout cable instead of a forward breakout cable. Also, what OS?

      I assume you’re using a UEFI motherboard? The sas2flash utility hasn’t been completely ironed out for the UEFI flash from 6GbpsSASHBA firmware to 2118it firmware. I’m still searching for a better version of sas2flash.

    2. sas2flash.efi distributed with LSI P19 was giving me the same “cannot flash it firmware over ir firmware” error when trying to flash 2118it.bin to an H310 in a Supermicro X10SAE. What worked was to use the sas2flash.efi in the base directory of mattr’s excellent zip collection:

      I also did sas2flash.efi -o -e 7 at one point to try to get past a “Failed to Validate Mfg Page 2” error. If you try this, make sure to first get your SAS address, and afterwards DO NOT REBOOT until you successfully flash *some* firmware to your card. After I ran the -e 7, I was unable to flash a firmware until I did sas2flash.efi -list. Then I could flash 6BGSAS.FW, and finally (using mattr’s sas2flash.efi) 2118it.bin. I don’t know if the -e 7 thing is needed. The critical thing is to use mattr’s ss2flash.efi and not the P19 one.

      Good luck! Many thanks to mattr!!!

      1. Older versions of sas2flash gave us the ability to override with a simple hit Y to accept. After P7 that was no longer an option. Using the older sas2flash version will allow us to do 2 things: first is bypass the “cannot flash it firmware over ir firmware” and the second is to flash the manufacture are with a different vendor. Looks like you ran into both of these issues. As you found out, the reason for the “Failed to Validate Mfg Page 2” error was generated because you needed to flash the Dell 6Gbps SAS HBA firmware prior to flashing the LSI firmware. I actually made a separate post about this error because I receive so many messages about it:

        The erase command is essentially doing the same thing as the cleanflash. Though cleanflash is more equivalent to doing a level 6 erase. A level 7 erase wipes everything including the mfg area. This doesn’t help in our flashing process though as the mfg is still on the card. It’s just not in the flash area. Our workaround is flashing the Dell 6Gbps SAS HBA firmware to trick sas2flash into thinking it’s a rebranded OEM LSI.

      2. mattr, thanks for clarification, and again for your excellent firmware zip and this site. Getting LSI IT on the H310 was a big pain even with your help. I’m not sure I’d have managed without.

  3. I was having problem flashing to LSI’s firmware. I kept getting :
    Writing Current Mfg Page 2 Settings to NVRAM.
    Failed to Validate Mfg Page 2!

    Firmware Returned Exception. IOCStatus=0x25, IOCLogInfo=0x0
    Due to error remaining commands will not be executed.
    Unable to Process Commands.
    Exiting SAS2Flash.

      1. I did. I even tried to use the megarec command outside of the bat commands. It’s odd because i see a lot of people are having success.

  4. Any good ideas how to convert an IT firmware flashed H310 back to its original state as a H310 PERC raid controller?

    1. I’m actually about to write up a tutorial on this exact topic. The simplest answer though is to just follow the same steps but with the H310 firmware. I haven’t done this in a while though and I can’t remember if there were any hangups. Hopefully I’ll have some time tonight to go through the process again and write something up.

  5. I’ve been fighting with this for a couple weeks now, and I figured I’d give everyone a rundown on how this experience panned out. I’m going to leave out all the crap that didn’t work.

    To start, I have an H200 rev.B2 card. I think the revision is an important part of what works and what doesn’t for people.

    To start, I downloaded the tools zip file from here and pulled some specific files from it.
    The files I needed were:

    Megarec.exe + sbrempty.bin
    2118p7.bin (p7)
    2118it.bin (p17)
    dos4gw.exe (megarec wont run without)
    dos32a.exe (megarec wont run without)

    I also used the p12 version of Sas2flsh.exe. I collected as many releases of this as I could find, and only p12 worked for me to put on the LSI firmware, though P15 did work for changing from RAID to HBA.

    For the boot process, I used Rufus to format my flash drive as an MSDOS boot disk. (that program is a serious godsend)

    And last but not least. I had to get the Dell A09 version of 6GBPSAS.fw to fix the card after everything was done.

    The motherboard you try this in has a BIG effect on whether it works or not. I could NOT get this process to work under ANY EFI-based motherboard with LegacyOptRom support. I got PAL errors up the wazoo. I had to use a pc that was bios based; and NOT an Intel reference board. Even with the B5/6 tape trick, I couldn’t get the Intel motherboards to boot.

    The command process I used was this:

    1. Megarec -writesbr 0 sbrempty.bin
    2. Megarec -cleanflash 0
    3. sas2flsh -f 2118p7.bin (no -o option used. it would fail if i tried it)
    4. sas2flsh -f 2118it.bin

    At that point, the card read as an actual LSI 9211-8i with p17 firmware on it, but there was a problem. The A port stopped functioning, which reduced my card to 4 drives available!

    I ended up reversing the process to go back to the Dell HBA firmware, and I got the A socket back, but then found out Drive A-0 wasn’t being detected as well. Turns out my card is faulty, which is why it was being sold.

    With the headache that I’ve had trying to make this thing work, I’m not sure I want to try with my new H310 card coming. I think I’ll just stick with the preloaded fw and just delete the boot rom.

  6. I forgot the line about adding back in the SAS Address:
    After the cleanflash 0

    sas2flsh -o -sasadd 5006xxx0xxxxxxxx
    then flash the P7 bin

  7. Matt,

    Thanks for the write up, it is very instructional. I am getting an error in the UFEI prompt about not being able to flash an it over an ir firmware. I see some other people have had this problem, and you mention that the old version of sas2flash.efi should prompt for this. I am using the tools from the zip file on page one, and I am not getting a prompt. I get the same error from sas2flash-p17.efi, which I guess is the updated one and which you mention you expect would not be able to flash the it over the ir. Is using an elevated prompt in windows the only solution? I am doing this on a linux build and don’t have a windows install on this machine.


    1. Sorry for the late reply. I’ve been away for a while. Typically this error is caused by some step being missed. Usually flashing the Dell SAS HBA firmware. I’m guessing you’ve found a resolution by now but you can try following the steps in this video post: with the updated zip file. It has some better tools and you can follow step by step with the video. The video quality is poor so I appologize for that but it should help.

  8. Beware of the LSI P20 firmware! There’s something totally strange going on when you use it. I have 3 Seagate 1TB SATA drives connected to my H200 and running P20 renders the disks unusable. You get tons of CRC errors. Formatting NTFS under Server 2012 R2 will always fail. And initialising a software raid in linux throws mpt2sas0: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000) every second…

    Wen’t back to P19 and everything is fine.

  9. One huge caveat with these procedures; if your Dell server happens to have an H700 card in addition to the H200, then the “megarec -cleanflash 0” command will brick the H700 card.

    I recommend removing any LSI-based RAID cards (like the H700 and H800) before trying this.

  10. Thanks for your guide!!
    i’ve found sas2flash.efi version P5 here:
    in the “” there is the P12 version only, which do not permit IT over IR “cannot flash it firmware over ir firmware” !!!
    With P5 version i can convert a Dell Perc H200 in standard LSI IT Mode only with UEFI boot no DOS

    sas2flash.efi -c 0 -list (and save the sas address)
    sas2flash.efi -o -e 6 (erase flash)
    sas2flash.efi -o -f 6GBPSAS.FW (flash original firmware)
    sas2flash.efi -o -f 2118it.bin (flash LSI IT firmware, type “y” when prompt vendor mismatch)
    sas2flash.efi -o -sasadd 500xxxxxxxxxxxxx

    Best regards!!

    1. The newer post with the video has an updated ZIP file with a ton of useful tools as well as all legacy versions of sas2flash. I need to updated the steps here soon and I’ll probably publish a new how post instead of editing the old one.

    2. Thank you gab.lau for P5 efi version which did the trick with my h200! Thank you mattr & others for making the guides and bundle of the tools needed!

  11. After following your steps I managed to get my H310 flashed to LSI 2118it.bin but when checking the adapter details using the list command it does not show the firmware product id with (IT) at the end like in your video. Is this something that can be overlooked or do I need to do something different?
    I ran into no problems during the process and slipped nothing. Last firmware file flashed was 2118it.bin

  12. After following your steps I managed to get my H310 flashed to LSI 2118it.bin but when checking the adapter details using the list command it does not show the firmware product id with (IT) at the end like in your video. Is this something that can be overlooked or do I need to do something different?
    I ran into no problems during the process and skipped nothing. Last firmware file flashed was 2118it.bin

      1. I had the same “problem”. Older version of sas2flsh.exe didn’t show product id with (IT). Newer version does show (IT) version.

  13. For guys like me who stuck with “cannot flash IT over IR” in UEFI: just flash from Windows command line using sas2flash-x64-p7.exe. I’ve got Windows 10 installed, but you can try doing it from Windows installation media (WinPE). Bet it’d work.

  14. Hi, I am trying to use same method to crossflash my PERC H330 but seem fail to do that. I can get my SAS address but can’t perform “megarec -writesbr 0 sbrempty.bin” or “megarec -cleanflash 0”
    I booting my desktop into DOS mode to do the step. all related FW getting from LSI avagotech. I also tried to cover P5-6 pin and can boot on non-Dell machine, that is amazing!! But fail to flash LSI fw for my desktop to use. Do you have any suggestion or idea whats going on? Major issue when execute “megarec …..” it claims No adaptor card was found…” Thanks for your kindly help!

  15. Any idea is there a way to cover PINs on RAID described below to bring it back from the death

    PERC – H310 – Mini – Mono –

    As you can see i assume Mini Mono is the same chip and after I flash it and deep dive then i realize what happen.

    What I did is:

    ### 1. erase the card

    megarec -writesbr 0 sbrempty.bin
    megarec -cleanflash 0

    ### After successful wipe i reboot and got error below:
    “Invalid PCIe card found in the Internal Storage slot!”
    “System halted!”

    ### Also tried without success to:
    1. remove controller and put it back again (yeaaa sometimes this things work)
    2. Set BIOS from Legacy to EUFI Boot
    3. Pray to work (didn’t help)
    4. Tried controller on other server with EUFI boot

    1. There is most likely a way to recover the card but since I don’t have one I can’t really do any testing with it. I’ve added a warning for people with those cards to not use these steps as several people around the webs have had issues.

  16. On a Windows 10 I cannot get the driver to say StorPort.
    My Dell H310 insists that it’s a Dell 6Gbps SAS HBA
    I can choose a “LSI Adapter, SAS2 2008 Falcon” driver, with the versionnumber, the same driverversion as the “Dell 6Gbps…”

    Will this do ok? Or what should I do to get the driver to say StorPort?

  17. Thank you so much for this! I thought I had bricked my H200 using another method I found elsewhere, but I was able to recover and update to the latest firmware with these excellent instructions. If you’re ever in Rhode Island I’ll buy you a beer.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s