lenovo_430-x_hba_firmware_BIOS_update.md

Lenovo 430-x HBA Firmware/BIOS Update

What?

Guide on how to update the firmware and BIOS of a Lenovo ThinkSystem 430-x SAS/SATA 12Gb HBA.

References

• Broadcom Support Download Search
• STORCLI SAS3.5 P31
• STORCLI Documentation
• Lenovo Support Search
• Lenovo Storage Host Bus Adapter HBA Windows Firmware

Steps

1. Download the latest STORCLI utility for LSI SAS3.5 Controllers per the reference above.
2. Download the latest HBA (Windows) driver package per the reference above.
3. Extract the packages to a folder on your local (Windows) machine.
4. Copy the relevant files to a FAT32 formatted USB, for example:
   • storcli.efi
   • 16i_24_00_07_00.fw
   • mpt35sas_x64_24_00_05_00.rom
   • mpt35sas_legacy_9_47_03_00.rom
5. Boot to the USB via EFI shell.
6. Identify the relevant (cX) HBA:

   storcli.efi show all

7. Confirm the relevant HBA:

   storcli.efi /c0 show

8. Backup STORCLI output to the USB:

   storcli.efi /c0 show all > backup\output.txt

9. Backup current controller bios, firmware etc. to the USB:

   storcli.efi /c0 get bios file=backup\bios
   storcli.efi /c0 get firmware file=backup\firmware
   storcli.efi /c0 get mpb file=backup\mpb
   storcli.efi /c0 get fwbackup file=backup\fwbackup
   storcli.efi /c0 get nvdata file=backup\nvdata
   storcli.efi /c0 get flash file=backup\flash

10. Update the firmware:

    storcli.efi /c0 download file=16i_24_00_07_00.fw

11. Update the EFI BIOS:

    storcli.efi /c0 download efibios file=mpt35sas_x64_24_00_05_00.rom

12. Update the BIOS:

    storcli.efi /c0 download bios file=mpt35sas_legacy_9_47_03_00.rom

13. Check HBA versions have updated:

    storcli.efi /c0 show

14. Power cycle the machine.

Make sure the "Include Legacy Products" box is checked so it appears.
Man, this is embarrassing! Now I found it, thank you very much!

INFO: Even with Broadcom 9400-16i (P24) Firmware flashed, I couldn't get a Samsung NVMe drive via SFF8643->SFF8639 (U.2) cable and M.2 to U.2 PCIe Adpater to work. Don't know why, even got strange errors with other PCIe devices in my MoBo (AsRock B450M Pro4).
Maybe it works with other setups.

Make sure the "Include Legacy Products" box is checked so it appears.
Man, this is embarrassing! Now I found it, thank you very much!

INFO: Even with Broadcom 9400-16i (P24) Firmware flashed, I couldn't get a Samsung NVMe drive via SFF8643->SFF8639 (U.2) cable and M.2 to U.2 PCIe Adpater to work. Don't know why, even got strange errors with other PCIe devices in my MoBo (AsRock B450M Pro4). Maybe it works with other setups.

As I stated above you need to connect the NVMEs with a compatible cable, these cards do not work with generic SFF8643 to SFF8639 cables due to Broadcom proprietary cable, anyway you can buy a compatible one on Aliexpress, link on my comment above:

https://gist.github.com/buswedg/f94a7978b07c1976e81e6d456ec37853?permalink_comment_id=5208888#gistcomment-5208888

Broadcom genuine:
05-50064-00 or 05-50065-00

https://docs.broadcom.com/doc/12354774

@dgaglioni

does the "capability - NVME" not even show up if the NVME is not connected even after a successful flash?

I wasn't sure if my flashing was successful due to showing only sata and sas.

@dgaglioni

does the "capability - NVME" not even show up if the NVME is not connected even after a successful flash?

I wasn't sure if my flashing was successful due to showing only sata and sas.

You need to cross-flash your 430-16i with 9400-16i firmware in order to have NVME support, for some stupid reason Lenovo removed this feature in their firmware.

@dgaglioni
does the "capability - NVME" not even show up if the NVME is not connected even after a successful flash?
I wasn't sure if my flashing was successful due to showing only sata and sas.

You need to cross-flash your 430-16i with 9400-16i firmware in order to have NVME support, for some stupid reason Lenovo removed this feature in their firmware.

ah gotcha, i'll give lsi one a go, and report back.

Thanks!

But storcli won't let you update the firmware and prints error: "firmware is invalid" when I tried to do so. To circumenvent this (I DO NOT RECOMMEND THIS!), one can append the "force" parameter like so: storcli /c0 download file=/path/to/file.bin force Same procedure for downgrades btw, use: storcli /c0 download file=/path/to/file.bin noverchk

I still have to test if there are any issues with using mixed firmware and mixed devices, but server boots normal and storcli /c0 show all output seems to be ok, reports NVMe capability.

Any issues so far? I'm tempted to do the force flash. I was able to update using the Lenovo firmware but get the firmware image invalid with the (P24) version

Notes for others:
Simply running storcli.efi /c0 download file=HBA_9400-16i_Mixed_Profile.bin on Linux will give you an error saying it can’t read the .bin file.

You have to use the efi mode or

storcli /c0 download file=HBA_9400-16i_Mixed_Profile.bin force

Any issues so far? I'm tempted to do the force flash. I was able to update using the Lenovo firmware but get the firmware image invalid with the (P24) version

Notes for others: Simply running storcli.efi /c0 download file=HBA_9400-16i_Mixed_Profile.bin on Linux will give you an error saying it can’t read the .bin file.

You have to use the efi mode or

storcli /c0 download file=HBA_9400-16i_Mixed_Profile.bin force

I had no issue so far with a crossflashed Lenovo 430-16i with latest P24 Broadcom/LSI firmware. But as mentioned above, presumably because of the missing right/genuine cable couldn't get NVMe drives to work.

NOTE: For force flashing, you need to use a more recent version of storcli. I had the same issue using storcli P24 and could get it force flashed (via Linux shell on host) using storcli P32.

@dgaglioni

do you maybe have a newer, still functioning link to a broadcom cable on ali? your old links are not working anymore and i could not find any on ali.

@dgaglioni

do you maybe have a newer, still functioning link to a broadcom cable on ali? your old links are not working anymore and i could not find any on ali.

For me it still works (link)

hm

@dgaglioni
do you maybe have a newer, still functioning link to a broadcom cable on ali? your old links are not working anymore and i could not find any on ali.

For me it still works (link)

Opening this link gives me this image for a second, then the second image after loading properly. Sad.

Opening this link gives me this image for a second, then the second image after loading properly. Sad.

aliexpress.com/item/4000758187693.html

try only this url.

hm sad. Thats also not working for me. Also tried it while being logged into my account. @dgaglioni how much do these cables cost on ali?

Why are you all making this so hard. Search 8643 sas cable on Amazon.

Why are you all making this so hard. Search 8643 sas cable on Amazon.

It won't work

https://a.co/d/fe6ulfi

Literally the same thing but using sata instead of molex. Good reviews. I am curious why you think it wouldn't work?

Based on the product information, CableDeconn SFF-8643 Internal Mini SAS HD to (4) 29pin SFF-8482 connectors with SAS 15pin power port 12GB/S Cable supports Broadcom controllers. Customers use this cable with LSI Broadcom SAS 9300-8i SATA/SAS Host Bus Adapter and 12G LSI cards.

https://a.co/d/fe6ulfi

Literally the same thing but using sata instead of molex. Good reviews. I am curious why you think it wouldn't work?

I tried it with no-noname (Delock) cables and Startech adapter. I don't know why exactly but it won't work. Presumably something to do with how the pcie-lanes are handed over.

The "cheap" cables are meant for non-raid cards which essentially are adapters from pcie-slot -> sff-8643 and similar. This way, no pcie-lanes must be negotiated with a controller.

It's $13. Just try it. Return it if it doesn't work?

Seems like you could potentially save yourself a lot of hassle here.

Anyway, good luck.

aliexpress.com/item/4000758187693.html

27 USD

Try googling:

2SFF8643 to 2SFF8639 12Gb/NVMe MiniSAS HD to U.2 80CM Cable Length 20CM Large 4Pin PowerLine For Broadcom 94xx HBA/RAID Card

Try other browser than Chrome as well.

https://a.co/d/fe6ulfi

Literally the same thing but using sata instead of molex. Good reviews. I am curious why you think it wouldn't work?

With the cables I mentioned above you can connect U.2 NVMEs on a 94XX controller, the ones you mentioned are for SATA/SAS disks.

https://www.broadcom.com/support/knowledgebase/1211219217821/nvme-cables-and-information-

Thank you for making this guide. I purchased an Avago 430-16i from AliExpress. Not sure whether it's a clone or refurbished original or what, but it seems to be working as expected. I crossflashed to LSI 9400-16i FW as mentioned by others in the thread. Just one question, is it normal for the "Product Name" in storcli to remain "430-16i" after flashing to 9400-16i? All of the other info, such as "FW Version" "BIOS Version" "NVDATA Version" all seemed to have changed appropriately, and I now see NVME in Capabilities/Supported Drives, I just wasn't sure if the "Product Name" should be changing to 9400-16i or not.
Thanks again.
Edit: I knew I forgot to mention something else.. although the HBA seems to be working fine, (I did some speed tests in Windows) I am not able to boot into the HBA BIOS. Have tried changing many settings in host BIOS to accomadate legacy/EFI/CSM etc. and the most I'm seeing is a "Broadcom MPT35 HBA BIOS" splash screen on boot, where it "initializes" and then checks for disks attached to the HBA, but It never shows the option to load the BIOS with "Ctrl + C". It just finishes checking for disks and then the server boots into the OS.
Anyways.. I'm a noob with this stuff so I'm assuming I've done something wrong but hopefully someone can help. Thanks again.

I purchased an Avago 430-16i from AliExpress. Not sure whether it's a clone or refurbished original or what, but it seems to be working as expected.

Very likely to be a clone. I purchased one and found it to be, and it had severe issues.

Just one question, is it normal for the "Product Name" in storcli to remain "430-16i" after flashing to 9400-16i?

I am unable to verify this, as I do not have a lenovo variant, so take it with a grain of salt. I am pretty sure that is normal. The only thing that seems to have changed is what is updated, which is the firmware.

I am not able to boot into the HBA BIOS.

Possibly an issue with the update. I had one with one of my clones. After an update, it spat out nothing but gibberish. I could get into the bios, though, so ymmv.

I bought two of these off of ebay and neither shows in in the preboot. No way to get into the lenovo/LSI firmware menu like all the other LSI cards I own. Is this normal? I tried on two Supermicro x9scm-f boards and on an ASRock board. If i run lspci in linux, neither card shows up. Any ideas?

@MatrixInfosec

I bought two of these off of ebay and neither shows in in the preboot. No way to get into the lenovo/LSI firmware menu like all the other LSI cards I own. Is this normal? I tried on two Supermicro x9scm-f boards and on an ASRock board. If i run lspci in linux, neither card shows up. Any ideas?

Go back to the supermicro board and boot into built in uefi with the usb and storcli.efi utility. Ensure that the slot is not disabled and is set to load an oprom in the pcie settings, and is set to the right lane configuration (probably in cpu settings). When booted into the built in uefi, navigate to the flash drive (using the command fs0: probably, use map -b to see storage devices if it didnt print it initially) and use the command storcli.efi show to list the controllers and storcli.efi /cx show ("x" being the card num shown in storcli.efi show) to list the properties for the card. After you are at that point, you can probably flash it with the above commands.

Your storage controllers may have been flashed improperly, or could be without a rom of a certain type. You can try the different oprom types by changing the oprom to legacy or uefi for the pcie slot in the supermicro motherboard bios.

Additionally, make sure that your x9 motherboard is updated to the latest firmware. Sometimes, x9 boards can have issues flashing firmware. This does not relate to detecting these cards, however, so it should work at least for that.

If you have any questions about this, @ me and I will do my best to respond promptly.