mirror of
https://github.com/lrq3000/lsi_sas_hba_crossflash_guide
synced 2025-03-23 03:36:32 +00:00
upload images
Signed-off-by: Stephen L. <LRQ3000@gmail.com>
This commit is contained in:
parent
0866404cff
commit
f447cba143
@ -48,12 +48,12 @@ Also, know that LSI HBA controllers, are VERY hard to brick, so feel free to exp
|
||||
8. Do NOT do any other command between the sas2flash/sas2hax ones that are advised here, eg, do NOT try to sas2flash -listall in the middle, it may make the rest failbfor some reason as reported by some, sas2flash seems to be finicky and require a precise sequence of actions to work for crossflashing (which is not its primary purpose)!
|
||||
9. `sas2haxp20.efi -o -f 2118IT.BIN -b mptsas2.rom` for fujitsu, sas2flash.efi for others. No need for sas2flash -o -e 6 or 7 beforehand but you can try if you messed up before. Use 2118IT.BIN for IT mode, 2118IR.BIN for IR mode (hardware RAID). IT mode is better if you fant to make a software RAID, and in general it's better for files recovery if you ever get a disk corruption (which WILL happen eventually for any hard drive or storage medium).
|
||||
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! 
|
||||
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! 
|
||||
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 `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! 
|
||||
16. Reboot, and you should see a new POST setup screen for the hba controller and it should show it detects all drives now! 
|
||||
|
||||
### A few helpful rules and tips
|
||||
|
||||
|
BIN
img/img1.jpg
Normal file
BIN
img/img1.jpg
Normal file
Binary file not shown.
After ![]() (image error) Size: 88 KiB |
BIN
img/img2.jpg
Normal file
BIN
img/img2.jpg
Normal file
Binary file not shown.
After ![]() (image error) Size: 131 KiB |
Loading…
Reference in New Issue
Block a user