LSI Raid Firmware Bios Flashing: Difference between revisions

From Hack Sphere Labs Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 3: Line 3:
Get the firmware
Get the firmware
use the sas2flash.efi
use the sas2flash.efi
*https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#Boot_Process_under_UEFI


  Create a usb key with fat16 and then create the following:
  Create a usb key with fat16 and then create the following:
Line 8: Line 10:
  Get the shell.efi (it sounds like you need the older shell.efi because it supports older versions of EFI specs.)
  Get the shell.efi (it sounds like you need the older shell.efi because it supports older versions of EFI specs.)
  cp shell.efi to /EFI/boot/boot.efi for 32bit/ bootx64.efi 64bit.
  cp shell.efi to /EFI/boot/boot.efi for 32bit/ bootx64.efi 64bit.


use the shellx64.efi
use the shellx64.efi
Line 15: Line 16:


Run the proper command:
Run the proper command:
sas2flash.efi -o -f 2118ir.bin -b mptsas2.rom
sas2flash.efi -o -sasadd 500605bxxxxxxxxx (x= numbers for SAS address)
I switched from IR to IT bios with this command...
I did not write a sas address
If I add another card I have to.  (http://lime-technology.com/forum/index.php?topic=12767.210)
6. Program SAS address in IT-mode:
sas2flsh -o -sasadd 500605bxxxxxxxxx
where "500605bxxxxxxxxx" SAS address from small green sticker on yor card, without "-"
Despite me missing this, it is humming away nicely in my now converted production box on 5.0.12a.
BUT - I now have a second card, that I 'm intending to integrate.
I did the reflash including step 5 on the only machine I have been able to. Then I figured I would reboot to do step 6 - also to read the sticker for the number.
Unfortunately, that machine now can not boot, as it is hanging at the BIOS of the adapter. So I have no option at my disposal to do step 6 on any of the cards.  :-[
Will I have any issues in an unRAID scenario by having two cards that has both not been through step 6 to get individual addresses?
=Notes=
*http://forums.servethehome.com/raid-controllers-host-bus-adapters/433-ibm-m1015-experiences-5.html
*Example of how dos util does not work:  https://plus.google.com/u/0/photos/106386350930626759085/albums/5848192137934097201
*http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/SAS_SATA_6G_P16/readme_SAS2_UEFI_BSD_HII_P16.txt

Revision as of 00:55, 27 April 2013

Best way is to create a UEFI boot disk as you will get command errors if you do not in most situations, at least in DOS.

Get the firmware use the sas2flash.efi

Create a usb key with fat16 and then create the following:
/EFI/boot
Get the shell.efi (it sounds like you need the older shell.efi because it supports older versions of EFI specs.)
cp shell.efi to /EFI/boot/boot.efi for 32bit/ bootx64.efi 64bit.

use the shellx64.efi

Boot into the EFI shell...

Run the proper command:

sas2flash.efi -o -f 2118ir.bin -b mptsas2.rom
sas2flash.efi -o -sasadd 500605bxxxxxxxxx (x= numbers for SAS address)

I switched from IR to IT bios with this command... I did not write a sas address

If I add another card I have to. (http://lime-technology.com/forum/index.php?topic=12767.210)

6. Program SAS address in IT-mode:
sas2flsh -o -sasadd 500605bxxxxxxxxx 
where "500605bxxxxxxxxx" SAS address from small green sticker on yor card, without "-"

Despite me missing this, it is humming away nicely in my now converted production box on 5.0.12a.

BUT - I now have a second card, that I 'm intending to integrate.

I did the reflash including step 5 on the only machine I have been able to. Then I figured I would reboot to do step 6 - also to read the sticker for the number.

Unfortunately, that machine now can not boot, as it is hanging at the BIOS of the adapter. So I have no option at my disposal to do step 6 on any of the cards.  :-[

Will I have any issues in an unRAID scenario by having two cards that has both not been through step 6 to get individual addresses?

Notes