update instructions

Signed-off-by: Stephen L. <LRQ3000@gmail.com>
This commit is contained in:
Stephen L 2023-06-14 17:48:14 +02:00
parent f0cecc8987
commit e6842bfeed
1 changed files with 8 additions and 5 deletions

View File

@ -32,11 +32,14 @@ Also, know that LSI HBA controllers, are VERY hard to brick, so feel free to exp
#### SBR hacking #### SBR hacking
1. Reboot and from the very first screen right away start pressing F12 repetitively for a few minutes until a boot selector appears. If this does not work, reboot and enter BIOS, usually by pressing F2, then it can offer a boot selector on the last tab. 1. Reboot and from the very first screen right away start pressing F12 repetitively for a few minutes until a boot selector appears. If this does not work, reboot and enter BIOS, usually by pressing F2, then it can offer a boot selector on the last tab.
2. Boot into normal (non uefi) option first, freedos. If error memory corrupted, disconnect sas and sata drives that are bigger than 2TB (even if your current sas firmware supports drives bigger than 2TB! Freedos doesn't!). 2. Boot into normal (non uefi) option first, freedos. Note: If you get an error "memory corrupted" with FreeDOS hanging, disconnect sas and sata drives that are bigger than 2TB (even if your current sas firmware supports drives bigger than 2TB! Freedos doesn't!).
3. `megarec.exe -readsbr 0 origsbr.bin` - note: do this only the first time, to save your original sbr in case it's a rare card with special flags necessary to flash it and to detect hard drives slots (such as fujitsu). If you redo the whole flashing process later, skip this to avoid overwriting your original! 3. `megarec.exe -readsbr 0 origsbr.bin` - note: do this only the first time, to save your original sbr (Serial Boot ROM) in case it's a rare card with special flags necessary to flash it and to detect hard drives slots (such as fujitsu). If you redo the whole flashing process later, skip this to avoid overwriting your original!
* CRITICAL NOTE: make sure to make a backup ASAP outside of the USB key, not because of the SAS address as can be read in some places (we do not care about it because a random address can be used instead, its like a MAC address, you just need it to be unique on your system to avoid conflicts), but to backup the whole SBR as it may contain special flags that are unique to your HBA controller, especially if its rarely used by other users online! * CRITICAL NOTE: make sure to make a backup ASAP outside of the USB drive, not because of the SAS address as can be read in some places (we do not care about it because a random address can be used instead, its like a MAC address, you just need it to be unique on your system to avoid conflicts), but to backup the whole SBR as it may contain special flags that are unique to your HBA controller, especially if its rarely used by other users online!
4. `megarec.exe -writesbr 0 sbr-a11.bin` or `sbr-a21.bin` for fujitsu, sbr-empty.bin for others. This sets a new sbr to allow updating to a newer firmware from another brand, we here use hacked sbr mixing data from other brands with a few flags specific to our own original brand (that's why the original sbr can be necessary, in case you need to make a custom sbr yourself as explained here, see below). Note: in FreeDOS, writing filenames and commands in uppercase or lowercase does not matter. 4. Optional but strongly recommended: `megarec.exe -readspd 0 origspd.bin` to save your controllers original SPD (Serial Presence Detect).
5. `megarec.exe -cleanflash 0` to clean the firmware (while keeping the sbr). Note: i think this is equivalent to doing `sas2flash.efi -o -e 7` in the uefi shell, but not 100% sure. * Also try to backup this file outside of the USB drive ASAP!
5. Optionally, you can save your HBA controllers SAS address with `megacli.exe -AdpAllInfo -aAll -ApplogFile AdaptersInfo1.txt` or `sas2flsh.exe -l Adapters.txt -listall`, but any random unique address will be as fine.
6. `megarec.exe -writesbr 0 sbr-a11.bin` or `sbr-a21.bin` for fujitsu, sbr-empty.bin for others. This sets a new sbr to allow updating to a newer firmware from another brand, we here use hacked sbr mixing data from other brands with a few flags specific to our own original brand (that's why the original sbr can be necessary, in case you need to make a custom sbr yourself as explained here, see below). Note: in FreeDOS, writing filenames and commands in uppercase or lowercase does not matter.
7. `megarec.exe -cleanflash 0` to clean the firmware (while keeping the sbr). Note: i think this is equivalent to doing `sas2flash.efi -o -e 7` in the uefi shell, but not 100% sure.
#### Crossflashing the firmware of another hba controller #### Crossflashing the firmware of another hba controller