LSI SAS 9201-16e: ERROR: Firmware Host Boot Failed! [SOLVED]

Helmut101

New Member
Sep 28, 2021
11
3
3
I am about to return this card, but I want to give it a last try by asking here.

Context:
  • New LSI SAS 9201-16e "Bulk" Card ordered from an official IT distributor (not ebay)
  • Tried to flash to IT Mode with P20 firmware (for use as HBA in JBOD enclosure)
  • Tested all steps in two different computers
  • Tested different versions (older sas2flash; firmware P10)
On regular boot, I get:

Code:
Unable to load LSI Corporation MPT BIOSMPT BIOS Fault 05h encountered at adapter PCI(07h,00h,00h)
Sas2flash (UEFI) says:
Code:
>sas2flash -listall
Adapter Selected is a LSI SAS: SAS20116_1(B1)

Contoller is not operational. A firmware download is required.
Enter firmware file name or quit to exit:
>9201_16e-P20.bin

Chip is in Fault state. Attempting Host Boot...
ERROR: Firmware Host Boot Failed!

Firmware fault occured. Fault code: 0A
Megarec (DOS) cannot even find the card
Code:
Warning! IO Base address high. Currently not supported.
No MR controller(s) found.

If controller(s) physically present but not found,
Please shutdown the system and set the jumper in default position and power up.
The Line Warning! IO Base address high. Currently not supported. only appeared on one of the two computers.

I tried the "hammer" method:
Code:
# erase current firmware
>sas2flash -o -e 6
...
Chip is in Fault state. Attempting Host Boot...
ERROR: Firmware Host Boot Failed!

Firmware fault occured. Fault code: 0A
Attached the same as screenshots. As far as I can tell from posts, if megarec cannot see it, I looks like there is no other way to recover the card?
I checked for any jumpers ("jumper in default position"), but I don't see any.

PXL_20211202_122529104_TN.jpg

PXL_20211202_123554634_tn.jpg
 
Last edited:

Helmut101

New Member
Sep 28, 2021
11
3
3
I am one step farther: The card is not dead!

Looking up this thread, I downloaded 2116IT19.ROM from Supermicro's FTP server. At this point, I do not know whether this is a supermicro card, but this Firmware was the only one that did not error out immediately.

First, ignore that the file ends with .ROM (and not .bin).

There is a .bat file included in Supermicro with these steps:
Code:
@echo off
sas2flsh -o -e 7
cls
sas2flsh -f 2116IT19.ROM
sas2flsh -b mptsas2.rom
sas2flsh -b x64sas2.rom
cls
sas2flsh -o -sasaddhi 5003048
Since I cannot use sas2flsh (DOS), due to PAL errors, I substituted sas2flash (P20) (UEFI).

Code:
sas2flash -o -e 7
Look at the output:
Code:
Controller is not operational. A firmware Hostboot is required.
Enter firmware file name or quit to exit: > 2116IT19.ROM

Firmware Version 19.00.00.00
Firmware Image compatible with Controller.

Valid NVDATA Image found.
NVDATA Version 11.00.00.00
Checking for a compatible NVData image...

NVDATA Device ID and Chip Revision match verified.
Valid Initialization Image verified.
Valid BootLoader Image verified.

Performing Host Boot...
Firmware Host Boot Successful !

Executing Operation: Erase Flash

Erasing Entire Flash Region (including MPB) ...

Erase Flash Operation Successful!

Resetting Adapter...
Reset Successful!

Finished Processing Commands Successfully.
Exiting SAS2Flash.
Next step:
Code:
sas2flash -listall
Returns: No LSI SAS adapters found!

Running the command a second time is back to:
Code:
Adapter Selected is a LSI SAS: SAS2116_1(B1)

Controller is not operational. A firmware download is required.
Enter firmware file name or quit to exit:
At this point, I realize that the above means: To actually make the card accept _any_ commands, a firmware needs to be "downloaded", that is loaded ("Firmware Host Boot") to execute the provided command.

I tried this:
Code:
sas2flash -o -f 2116IT19.ROM
# Controller is not operational. ... Enter firmware file name or quit to exit: 2116IT19.ROM
This worked in the linked thread above, but not for me:
Code:
Controller is not operational. A firmware Hostboot is required.
Enter firmware file name or quit to exit: > 2116IT19.ROM

Firmware Version 19.00.00.00
Firmware Image compatible with Controller.

Valid NVDATA Image found.
NVDATA Version 11.00.00.00
Checking for a compatible NVData image...

Chip is in FAULT state. Attempting Host Boot...
Firmware Host Boot Successful !

Mfg Page 2 Mismatch Detected.
Writing Current Mfg Page 2 Settings to NVRAM.
updating Mfg Page 2.

Resetting Adapter...
Adapter Successfully Reset.

Chip is in RESET state. Performing Host Boot...
Firmware Host Boot Successful.

Beginning Firmware Download...
Takes about 5 Minutes, before returning:
Code:
Firmware Download Failed!

Due to error remaining commands will not be executed.
Maybe I still have the wrong firmware and this is a very rare variant of 9201-16e.
I tried the above command with any firmware version I could find:
  • 9201-16e-P10.bin
  • 9201-16e-P20.bin
  • DELL-A10-6GBPSAS-8e-IT.FW
Any other ideas?
 
Last edited:

Helmut101

New Member
Sep 28, 2021
11
3
3
Holy sh**

This was the solution:
Code:
sas2flash -o -e 7
sas2flash -o -c 0 -f 2116T207.ROM -b mptsas2.rom
Here, the first critical piece was to not issue any command between the two (e.g. do not try to list cards with sas2flash -listall, this will revert your card from RESET state back to FAULT state).

Second, as seen above, I needed to provide a firmware _and_ bios.

Sidenote, I used the P20 Supermicro firmware here (2116T207.ROM), provided in the linked thread.
Code:
Controller is not operational. A firmware Hostboot is required.
Enter firmware file name or quit to exit: > 2116T207.ROM

Firmware Version 20.00.00.00
Firmware Image compatible with Controller.

Valid NVDATA Image found.
NVDATA Version 14.00.00.00
Checking for a compatible NVData image...

Chip is in FAULT state. Attempting Host Boot...
Firmware Host Boot Successful !

Mfg Page 2 Mismatch Detected.
Writing Current Mfg Page 2 Settings to NVRAM.
updating Mfg Page 2.

Resetting Adapter...
Adapter Successfully Reset.

Chip is in RESET state. Performing Host Boot...
Firmware Host Boot Successful.

Beginning Firmware Download...
Firmware Download Successful.

Resetting Adapter...
Adapter Successfully Reset.

Executing Operation: Flash BIOS Image

Validating BIOS Image...
BIOS Header Signature is Valid
BIOS Image has a Valid Checksum.
BIOS PCI Structure Signature Valid.
BIOS Image Compatible with the SAS Controller.
Attempting to Flash BIOS Image...
Verifying Download...
Flash BIOS Image Successful.
Updated BIOS Version in BIOS Page 3.

Finished Processing Commands Successfully.
Code:
LSI-P20-sas2flash.efi -listall

Num    Ctlr          FW Ver        NVDATA          x86-BIOS           PCI Addr
-------------------------------------------------------------------------------------------------------------------
0 SAS2116_1(B1)    20.00.07.00      14.01.40.00          07.37.01.00         00:07:00:00

Finished Processing Commands Successfully.
Afterwards, I followed the remaining two steps from the Supermicro .bat
Code:
sas2flash -b x64sas2.rom
sas2flash -o -sasaddhi 5003048
There was a sticker with the remaining 9 digits of the SAS Address on the card.

Now, it looks like this is not in IT Mode. But at least I am out of the "Chip is in FAULT state"

[Edit]

Ah, so perhaps this card indeed only has IT mode:
Code:
LSI-P20-sas2flash.efi -c 0 -list

Adapter Selected is a LSI SAS: SAS2116_1(B1)

Controller Number: 0
Controller: SAS2116_1(B1)
PCI Address: 00:07:00:00
SAS Address: 5003048-x-xxxx-xxxx
NVDATA Version (Default) :14.01.40.00
NVDATA Version (Persistent): 14.01.40.00
Firmware Product ID: 0x2213 (IT)
Firmware Version: 20.00.07.00
NVDATA Vendor: LSI
NVDATA Product ID: LSI2116-IT
BIOS Version: 07.37.01.00
UEFI BSD Version: 07.27.01.00
FCODE Version: N/A
Board Name: LSI2116-IT
Board Assembly: N/A
Board Tracer Number: N/A
Remaining step will be to erase the "Boot Services" (the Bios), since I don't need this for ZFS/HBA. I will do this once I could thoroughly test the card. This is the command:
Code:
sas2flash -o -e 5
Conclusion(s):
  • Yes, it appears to be quite hard to brick these cards, even with sas2flash -o -e 7 (Erase complete flash).
  • Also: Don't fear UEFI, I did not need megarec nor the DOS variant of sas2flsh. All of this was done on a consumer mainboard (Asus M5A97 Evo 2.0)
  • There are many types of HBA Adapters around, with different branding/versions even for a single product range such as 9201-16e/SAS2116.
  • In my case, all issues related to the card variant coming from Supermicro, which apparently only works with their ROMs.
  • It looks like someone before me tried to flash it with the wrong firmware and, apparently, did not succeed. Which is perhaps why the card was only EUR50

Now I can also enter the SAS configuration utility on regular start:
success.jpg
 
Last edited:
  • Like
Reactions: Sleyk and Stefan75

FrogForHireX

New Member
May 7, 2022
2
2
3
I had been fighting with a SAS2116 that I purchased as a MJFDPLSI Dell Compellent MJFDP 9201-16e 6Gbps Quad Port SAS HBA Card off and on for a few months. It was detectable by the OS, listed as in IT mode, and would never detect any drives or shelves. I was able to upload firmware to it (i thought) via FreeBSD's mpsutil and sas2flash.

Code:
sas2flash -list
LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

        Adapter Selected is a LSI SAS: SAS2116_1(B1)

        Controller Number              : 0
        Controller                     : SAS2116_1(B1)
        PCI Address                    : 00:07:00:00
        SAS Address                    : 5000d31-0-reda-cted
        NVDATA Version (Default)       : 14.01.00.07
        NVDATA Version (Persistent)    : 14.01.00.14
        Firmware Product ID            : 0x2213 (IT)
        Firmware Version               : 20.00.07.00
        NVDATA Vendor                  : LSI
        NVDATA Product ID              : SAS9201-16e
        BIOS Version                   : 07.39.02.00
        UEFI BSD Version               : 07.27.01.01
        FCODE Version                  : N/A
        Board Name                     : SAS9201-16e
        Board Assembly                 : H3-25519-00A
        Board Tracer Number            : SV25300984

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.
Eventually, I created an UEFI boot disk and made the first meaningful change, I erased the whole thing (sas2flash.efi -o -e 7 ) , but that version of sas2flash.efi would never write any of the ROMs to the device. Also, booting to FreeBSD became very difficult because of the driver errors scrolling by for long periods of time about the card being reset.

Basically, the card was 'dead'. But I had hope because I had read this thread.

Using the ISO from the forum was able to re-flash the card (it booted nicely from the iDrac6 of the Dell r710)

No need to repeat the steps as they are covered in this tread and the blog

The result:

Code:
 sas2flash -list
LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

        Adapter Selected is a LSI SAS: SAS2116_1(B1)

        Controller Number              : 0
        Controller                     : SAS2116_1(B1)
        PCI Address                    : 00:07:00:00
        SAS Address                    : 5000d31-0-reda-cted
        NVDATA Version (Default)       : 14.01.40.00
        NVDATA Version (Persistent)    : 14.01.40.00
        Firmware Product ID            : 0x2213 (IT)
        Firmware Version               : 20.00.07.00
        NVDATA Vendor                  : LSI
        NVDATA Product ID              : LSI2116-IT
        BIOS Version                   : N/A
        UEFI BSD Version               : N/A
        FCODE Version                  : N/A
        Board Name                     : LSI2116-IT
        Board Assembly                 : H3-25519-00A  <-- I set this
        Board Tracer Number            : SV25300984  <-- I set this

        Finished Processing Commands Successfully.
        Exiting SAS2Flash.
Now the controller finds the Enclosure and 7 of the 10 drives (which is my next task to resolve)

I posted all this as 'thanks' and hopefully breadcrumbs that one would likely need to boot in to UEFI or DOS to erase and re-program your device.
 
  • Like
Reactions: Helmut101

Helmut101

New Member
Sep 28, 2021
11
3
3
> Using the ISO from the forum was able to re-flash the card (it booted nicely from the iDrac6 of the Dell r710)

This is what I had to use, too (and described in the steps in the blog post). I did not entirely understand what you did differently, but apparently it worked for you :thumbsup:
 

FrogForHireX

New Member
May 7, 2022
2
2
3
> Using the ISO from the forum was able to re-flash the card (it booted nicely from the iDrac6 of the Dell r710)

This is what I had to use, too (and described in the steps in the blog post). I did not entirely understand what you did differently, but apparently it worked for you :thumbsup:
I think that I made an incorrect UEFI boot drive or used an incorrect sas2flash.efi program. They were all from downloads from Broadcom. The downloaded sas2flash.efi was able to erase the card. I'm not anything flashes to this card unless the card was erased. I did save a copy of the FW from the original card... somewhere.

The blog post made me have faith that I could recover the card even if I erased it completely. Since I erased it and then was unable to apply any firmware with the UEFI boot disk I had made, it was a great comfort to know that wasn't 'the end' for the card.

More recently, in an interesting turn of events, I discovered that this cable: "IBM SFF-8470 - SFF-8088 5.5M 1x Ext SAS Cable 00VJ141" does not seem compatible with my SAS9201-16e <--> Dell MD1000 enclosure. I think the 1x means it is not CX4.. or maybe it means it is a single lane and not 4 lanes. I have ordered the correct part. It was causing hard drives to disappear from the controller (but not from ses/sg_ tools). I have replaced it with a much shorter "Monoprice 1m 28AWG External SAS 34pin (SFF-8470) Male w/ Thumbscrews to Mini SAS 26pin (SFF-8088) Male Cable" that has worked for me in the past.

This build is not running SATA drives, but if it were, the shorter cables would help.
 
  • Like
Reactions: Helmut101