LSI SAS 9201-16i – Compatibility issues

Now that I did solve the “conflict” between the Promise FasTrack and the nVidia RAID, I experience another conflict… with the new LSI SAS 9201-16i that I just plugged in the motherboard (an Asus Striker II Formula).

Click to Read More

With the default settings of the SLI, I get the following message (with exactly this spelling 😉 ) after the LSI initialization (which passes successfully),:

Warning: Have Option ROM can not be invoke (Vendor ID:105Ah, Deivce ID:3701h).

Here is the long story, full of twists and turns, and an Happy End 🙂

Looking after 105A in the PCI database of vendors, I found that this vendor is “Promise “. So, for sure, the LSI adapter had issues to coexist on my motherboard where the Promise FastTrak TX4660 🙁

Fortunately, this was only a warning and the disks connected on the FastTrak were available within Windows. The actual issue was that the configuration menu of the FastTrak was not accessible anymore at boot time (And therefore, it was impossible to modify the disk array, …) 🙁

A workaround would have been to disable the “Boot Support” in the LSI configuration (the problem only occurs with option “Boot Support” = “Bios Only” or “OS and Bios” in the LSI configuration utility). And this would have been a valid solution for me as I don’t intend to boot ever on any disk connected to this controller. Another option would have been to temporary unplug the LSI to get access to the configuration menu of the Promise adapter at boot time.

However, to solve this annoying issue, I did try to update the bios of the LSI from its current version ( to the latest version (The firmware being already the last one: To dos so, I did download the package “9201_16i_Package_P15_IT_Firmware_BIOS_for_MSDOS_Windows” from SLI’s Find Support webpage.

I did next start a command prompt with the option “Run As Administrator” (If you don’t Run it as Administrator, the bios updater won’t find the adapter!) and did execute: sas2flash.exe -o -f 9201-16i_it.bin -b mptsas2.rom

The command (.exe) comes from the subfolder \sas2flash_win_x64_rel, the firmware (.bin) comes from the subfolder \Firmware\HBA_9201_16i_IT and the bios (.rom) comes from the subfolder \sas2flash_dos_rel. I did copy everything in a single folder.

The option -o is to run in advanced mode, which is actually not mandatory to update firmware and bios of native LSI adpaters.

But the situation went then really worst. The LSI bios was executing fine, i.e. without warning anymore. But next, nothing else was happening. I could see on my LCD Poster that the PC was trying to load the Boot menu (or enter the setup if I did press DEL), but it was never completing that step ?! I did try to disable the sata controllers on the motherboard and remove the FastTrak controller. Nothing helped (I had to remove the LSI adapter to be able to reach the setup menu).

Fortunately, I found that I could still boot correctly with the LSI adapter on my other PC, build on top of an Asus P9X79Pro (with UEFI support!). So, I did start to look how to downgrade the bios on that PC…

Unfortunately², impossible to find the old version of the bios on SLI’s website. I only found a version of the bios on Lime-Tech, a great forum about among others “unRaid systems” (The bios can be found in the package “LSI SAS2116 chipset”). I did the downgrade but that didn’t solve the problem. It was a bit different however as the LCD poster told me that the boot sequence was stick on “Bios Init” instead of “Boot Menu”… (which was worst IMO).

Notice that I was only able to downgrade the Bios. The firmware might not be downgraded. Trying to do so resulted in a message : ERROR: Cannot downgrade NVDATA version 0xf000003 to 0xa030001.

I though that the problem with the boot could be due to the update operation being not 100% correctly executed from within Windows, although it seemed to go well. So I did try to flash from a bootable usb key. But is Dos mode, on the Asus P9X79Pro, I get the error ‘Failed to initialize PAL ….’. According to LSI, this meant that the update procedure won’t work using that motherboard 🙁

So, I did next try to flash the SLI’s bios using the UEFI Shell supported by my Asus P9X79Pro…

  1. First, I did download the package “UEFI_BSD_P15” from SLI web site
  2. Next, I did copy on my USB key the files x64sas2.efi and x64sas2.rom located in the package’s subfolder \UEFI_BSD_P15\uefi_bsd_rel
  3. Then, I did found the UEFI Shell (2 versions) from here:
    1. x86_64 UEFI Shell 2.0
    2. x86_64 UEFI Shell 1.0
  4. I did rename the Shell 2.0 (to be tried first) into shellx64.efi and copied it into the root folder of my USB key.
  5. I did also print the EFI shell user guide.
  6. I did plug the SLI adapter and the USB key into my Asus P9X79Pro.
  7. During the boot, I entered the Bios Setup of the ASUS, in Advanced mode.
  8. In the “Exit” menu (In the top-right corner), I did select “Launch UEFI Shell from filesytem device.
  9. From the start screen of the shell, I took note of the name of the USB device which was displayed automatically (otherwise I would have had to type the command ‘map’). The name was “FS0”.
  10. I did move to that device (without the need to mount it! It appeared to already be mounted! Otherwise I would have had to type ‘mount FS0:’) and I tried execute the flash:
    1. FSO:
    2. x64sas2.efi -o -b x64sas2.rom

And…. I didn’t succeed to execute the flash command 🙁 I still need to dig how to use UEFI… E.g.: Instructions found in LSI’s ReadMe to flash from UEFI shell tell however to execute:

    1. drivers
    2. Take not of the drive number <dh>
    3. unload <dh>
    4. sas2flash -c <n> -b x64sas2.rom   where <n> is the #of the controller (0 if only one). Notice that the command I found on SLI web site was named x64sas2.efi instead of sas2flash.efi

As the list of drivers is far too long, I had to capture it and enter the EFI editor to read it:

      1. drivers > list.txt
      2. edit list.txt
      3. To exit the EFI editor press the “F3” key (or type “Esc 3” depending on your system.

Unfortunatelly++, after several tries to flash from the UEFI shell, I decided to give up and try something else as I was clearly not able to execute the updater from the shell (But for sure, I will come back into that UEFI shell to learn how to use it correctly).

I read that many people did recommend to clean the firmware and the bios before upgrading. This can be done with the command: sas2flash -o -e 6. Unfortunately, this operation is not supported in Windows mode and must be executed in Dos mode, which is not possible for me on the Asus P9X79Pro as mentioned above (error ‘Failed to initialize PAL). What a nightmare!

In the mean time, I had sent an email to LSI to get a copy of the bios I had to wait more that 24h but then started a really good exchange with one of their technicians. The guy told me that this version was so old that it was not available anymore. The oldest version available was, but he suggested to investigate internally to see if someone would still have a copy. On my request, he did send me the version for a try…

A miracle! That version solves both the boot issue when the LSI is plugged on my Asus Striker II Formula and the warning message when the Promise is plugged too.

And icing on the cake, 3TB disks are well supported and I can boot from disks connected on the LSI adapter (although that’s not at all my purpose – reason why I will disable Boot Support on this adapter).

[EDIT]: In a next post, I report on re-using this experience to make another LSI, a SAS 9211-8i, compatible with my ASUS Striker II Formula too.






10 responses to “LSI SAS 9201-16i – Compatibility issues”

  1. Jacek Avatar

    Hello. I have a similar issue as you described with LSI card (boot problem). If you could send me a bios version I would be very grateful.


    1. Valery Letroye Avatar

      I did sent you the “package” by email earlier today and I already got your answer:

      After many attempts with different versions of firmware for my controller IBM1015 I lost hope that it will work properly with my motherboard Gigabyte EX38-DS4. Fortunately, with your help, I was able to finally solve this problem (I used only mptsas2.rom file).

      Happy that it helped! Don’t forget, if by any chance you visit Brussels, to bring a bottle of Żubrówka :p

  2. Rudi Avatar

    Hello. I have a similar issue as you described with LSI card (boot problem). If you could send me a bios version I would be very grateful.
    Kind Regards,

    1. Valery Letroye Avatar

      Hi Rudi.

      I just sent you the package… Hope it will solve your issue too.

      EDIT: I got your answer. Happy that it fixed the problem!

      Hi Valery,
      thanks a lot!
      It solved my problem.

      Kind regards,

  3. Konstantin Avatar

    Hi Valery. I have the same problem with LSI SAS 9201-16i and Supermicro X9DR3-F motherboard. Could you send me bios version I couldn’t google that. (

    1. Valery Letroye Avatar

      I should place the package on some file sharing website 😀
      Otherwise, being off for a few days, I did suggest you to send your request to LSI’s support team and you answered:

      Hi, I did it, I wrote to LSI and they sent me firmware v.8.00.000. Thanks for you replay.

      I have to say that LSI’s support is really nice. I hope this version is solving your issue too 😉
      Just to clarify about the package sent by LSI (for other readers), it contains both the Bios and Firmware

  4. Valery Letroye Avatar

    Ok, so, here is a link to download the package

    Simply click CTRL + S to save it locally.

  5. Windozesuk Avatar

    Hello Valery,

    I hope you may be able to help me as you seem to be very knowledgable on these LSI cards. I have a sas9201-16E, I installed it, running windows server 2016, and windows sees the card and installed the appropriate drivers. However, I have it connected to a JBOD (xstore AIC XJ SA13 212R), and it will not see any disk drives. I have a mix of 4TB, 5TB, and 8TB drives in it (WD and Seagate consumer grade SATA). Other SAS cards were able to see the drives on this same system. There is no BIOS prompt during boot up for this card, as it is only an HBA and not a RAID, correct? Is there anything I can try to get these drives to show up? I tried removing drives and adding one at a time, but none of them show. Do you have any suggestions? Thank you

    1. Valery Letroye Avatar

      Windozesuk (Love your nick :D)

      I spent many hours years ago to install my cards. But since, my server is running fine and I never had to reconfigure anything. So, I have to admin I forgot a lot about the particularities of using this card.

      If like me you configured the card to use HBA (JBOD/passthru), then you don’t have to configure anything else in the LSI’s Bios when adding a disk. And the only messages displayed at boot by the card is :
      – the SiI SATALINK BIOS version
      – “Adapter(s) disabled by User”
      – “Press CTRL-C to start LSI Corp Configuration Utility”

      I am adding disks from time to time in my server and never have any trouble to see them in windows (via the Windows “Disk Management” console).

      NB.: in my case, I assign a letter to each disk and add them into a pool managed with StableBit software.

      I may only suggest to use the card on another motherboard if there was no yellow warning sign in Windows “Device Manager” console. The LSI card should appear under “Storage Controllers”. If there is a yellow warning on it, it has possibly a conflict. But I presume you already double checked that…


  6. Windozesuk Avatar

    Thank you for that quick response. I was able to get it working, it had P13 firmware on it, I flashed it to P18, I didn’t go all the way to P20 as I figured I would start a bit lower first and it worked great, so I think I’ll leave it at P18 if I don’t encounter any further issues. Thanks again for the reply

Leave a Reply

Your email address will not be published. Required fields are marked *