RepoMirrors
/
lsi_sas_hba_crossflash_guide
mirror of https://github.com/lrq3000/lsi_sas_hba_crossflash_guide
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update README.md

This commit is contained in:
Stephen Karl Larroque 2023-06-14 16:45:59 +02:00 committed by GitHub
parent 518d36f37a
commit 9c51741f97
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -47,7 +47,7 @@ Also, know that LSI HBA controllers, are VERY hard to brick, so feel free to exp
10. With fujitsu cards, the whole process should almost complete fine (Firmware download successful, no Mfg page 2 verification failed), but will fail at resetting the adapter with Fault code: 704. This is normal, your card is almost done but not fully yet, you need to reboot and redo the same. It's really necessary to reboot, trying any command in the current shell without rebooting will make the flashing fail and you may have to restart all the steps above.
11. For fujitsu only: Reboot into UEFI shell again (even though you were in it already), and write the same command again: `sas2haxp20.efi -o -f 2118IT.BIN -b mptsas2.rom` - this time it should complete fully, including the adapter reset! ![IMG_20230613_223746](IMG_20230613_223746.jpg)
12. Optional, only necessary if you plan on having multiple SAS HBA card simultaneously on the same motherboard (think about the future) : `sas2haxp20 -o -sasadd 5000xxxxxxxxxxxx` where x are 12 hexadecimal characters, just to make the card unique. You can restore your old id or just make one up. Eg of a basic one you can make up: `5000123456789abc`
13. Do `sas2hax -listall` to check, you should see your card is up! In case you already rebooted, you can always check later by rebooting into UEFI shell.
13. Do `sas2haxp20 -listall` to check, you should see your card is up! In case you already rebooted, you can always check later by rebooting into UEFI shell.
14. Optional, or necessary for fujitsu if you did not use the right sbr (eg, some drives are not detected): Reboot to freedos (no uefi), and do `megarec -writesbr sbr-a11.bin` or a21 for fujitsu, for others no need to, then reboot one last time. If you already used one of these two sbr at the start and you can see all your drives detected at boot POST, then you do not need to do this step. If you cannot see all the drives detected, then try another sbr, no need to reflash the firmware. You can try as many sbr as you want without habing to reflash your hba card with sas2hax, once the firmware is there, it will stay unless you do megarec -cleanflash!
15. If you forgot to include the rom, you won't be able to use sas drives as bootable devices (ie, cannot install an OS on them). But you can always flash the bootable rom later, by rebooting into the UEFI shell and type `sas2haxp20 -o -b MPTSAS2.ROM` (without the firmware 2118IT.BIN).
16. Reboot, and you should see a new POST setup screen for the hba controller and it should show it detects all drives now! ![IMG_20230613_225013](IMG_20230613_225013.jpg)
@ -92,6 +92,7 @@ If a link is dead, try to use the Wayback Machine, I tried to backup all the rel
7. If you have a Supermicro card, use their firmwares, they are very specific
8. Use mpsutil to show current firmware version https://www.truenas.com/community/threads/lsi-sas2008-hba-aka-9211-8i-q-firmware-upgrade-to-stop-bios-detection-fix-hotswap-not-working.84689/
9. If you are stuck at the stage of "no controller detected, need firmware" and you type in the firmware binary, it's not going to work. Even if with sas2flash -o -e 7 it appears to work at first, it will only use the firmware to know how to flash the hba, but then you need to download the firmware on it using sas2flash -o -f 2118IT.bin and then it will again complaint that no card is detected, and then if you again try to input the firmware 2118IT.BIN, it will start and then fail to download the firmware. Normally if you did things right for your hba, this should never happen, the commands should work right away without sas2flash complaining about no controller detected. If that'r the case, it means you need to upload another sbr for your hba using megarec.
10. If you do not have a UEFI shell or get a strange error with `sas2haxp20.efi`, then try to boot into FreeDOS and use `sas2flsh.exe` with the same arguments you would with `sas2flash.efi` or `sas2haxp20.efi`, it should work. If you get a "Not PAL" error, then you need for sure to boot into the UEFI shell.
### Files sourcing