9.3.1 Update with alert Firmware version 16 does not match driver version 20 for /dev/mps0

[mccann73]

For anyone who is interested, my system is BIOS based and I have 2 LSI cards in my Freenas box, one on the supermicro motherboard (X8SI6-F) and one LSI 9201-16i card.
I have always used the LSI supplied BIOS instead of supermicro firmware without issue.

SAS2FLASH Readme
http://www.lsi.com/sep/Documents/oracle/files/SAS2_Flash_Utility_Software_Ref_Guide.pdf

SAS 9201-16i Host Bus Adapter
Downloaded - 9201_16i_Package_P20_IT_Firmware_BIOS_for_MSDOS_Windows

SAS LSI 2008 8-Port 6Gb/s (on board)
Downloaded - 9211_8i_Package_P20_IR_IT_Firmware_BIOS_for_MSDOS_Windows

• Built a usb DOS boot disk (rufus), copied the firmware files into a single folder for each card on the usb drive to make DOS access easier.
• Booted into the USB drive
• Ran sas2flsh -listall to find the id numbers of the controllers, 9201 = 1, 9211 = 0 and confirm firmware versions
  
• Then erased existing firmware (no reboots before flashing new firmware), use erase 6, safer than 7 that can remove manufacturer information, see sas2flash link above. -c is select controller (for multiple controllers)
  
• sas2flsh -o -c 0 -e 6
• Then flashed firmware for BIOS mode
• sas2flsh -o -c 0 -f 2118it.bin -b mpt2sas.rom
• Now reboot before flashing next firmware (important)
  
• sas2flsh -o -c 1 -e 6
• sas2flsh -o -c 1 -f 9201-16i_it.bin -b mpt2sas.rom
• Rebooted and all good :)

Cheers

 

[crumbz]

I upgraded to 9.3.1 first, not knowing about the new firmware version requirement/recommendation.

I have a Supermicro X10SL7-F board which I upgraded with this firmware:

ftp://ftp.supermicro.com/Driver/SAS/LSI/2308/Firmware/IT/PH20-IT.zip

following the instructions here:

http://blog.widodh.nl/2014/10/flash-lsi-2308-to-it-mode-on-a-supermicro-x10sl7-f-mainboard/

I did this all remotely, not having physical access to the server I can't rely on USB drives to update the firmware.

Everything went really smooth.

 

[kspare]

Has anyone determined if it's worth doing this upgrade at this point? I just went through all the posts and I thought I saw someone say P20 was slower?

Thanks to all the people taking the plunge!

 

[j_r0dd]

Just wanted to pass along an update from ASRock. They will be working with LSI on a P20 IT firmware for the E3C224D4I-14S. No ETA.

 

[Ericloewe]

Just wanted to pass along an update from ASRock. They will be working with LSI on a P20 IT firmware for the E3C224D4I-14S. No ETA.

Thanks for the info.

 

[cyberjock]

@Scareh,

The issues with the 'older' P20 firmwares were related to booting from the LSI controller and sometimes some disks would not be available.

For the 'beta' I can't vouch for precisely what version was tested, but I can say that we weren't testing builds before the were released. :P

I personally have high confidence in 20.00.04 being stable and works properly. If I had my systems up and running right now I'd upgrade without hesitation.

 

[cyberjock]

Oh, I talked to AsRock Rack. @j_r0dd is right. They are working on a P20 based on my request and I think his. My POC at AsRock Rack told me they will start working on a P20 IT firmware, but they have no ETA. But.. they *are* working on it so the only recommendation I can provide for AsRock users is to wait patiently for AsRock Rack to do their thing and provide the new firmware.

 

[adrianwi]

Doesn't the iXsystem FreeNAS Mini use an AsRock motherboard? Surely a bit of an own goal releasing an update that people who've bought the inhouse solution can't run?

 

[danb35]

The ASRock motherboard in the FreeNAS Mini does not include an LSI controller, so there's no issue.

 

[diedrichg]

Subscribed for future reference.

 

[jjstecchino]

The simple way..... (As always a good backup is always a good thing. Just in case)
My scenario: SM X10SL-7 and an IBM M1015 working properly on firmware 16, updated to 9.3.1 and got firmware mismatch.

SSH to the box

make a temporary dir and go into it

Get firmware for IBM M1015
wget http://www.cstone.net/~dk/p20.zip
unzip p20.zip

Get firmware for 2308 from super micro
wget ftp://ftp.supermicro.com/driver/SAS/LSI/2308/Firmware/IT/PH20-IT.zip
unzip PH20-IT.zip

Run freebsd sas2flash -listall and note the index number for the 2008 (IBM) vs the 2308 (Supermicro) controller then with this info:
sas2flash -c # -f 2118it.bin where # is the index number for your SAS2008 (IBM) controller
sas2flash -c # -f UEFI/2308IT20.ROM where # is the index of your SAS2308 (Supermicro) controller (adjust the path if you unzipped to a different directory)

Do a sas2flash -listall to confirm both controllers are on rev 20 firmware, then reboot

Now both controllers are on Rev 20, pools are loaded ok, no errors. No sweat, no paranoia. (Having a backup helped making me feel brave though)

The SM firmware is indeed slightly older (20.00.02.00) than the LSI (20.00.04.00). I will upgrade when SM comes up with an upgrade or otherwise if either I get problem or somebody else convincingly reports firmware related trouble. I am confident SM would not have left a bugged firmware in the general download for this board and risk irate users calling after losing their data

Cheers

 

[j_r0dd]

ASRock just sent over the 20.00.04.00 IT firmware. He said he sent to @cyberjock as well. Will upload when I'm not mobile. I must say I have been thoroughly impressed with the helpfulness of ASRock every time I have contacted them.

 

[Chupa0]

I may have bricked my m1015 :-(

I am stuck with this firmware Host Boot Failed! error.

I am not really sure what went wrong. Any ideas of what I can try to rescue this card?

 

[j_r0dd]

So ASRock sent me a word doc with the zip file embedded with instructions for use with a dos bootable disk. You can't get the zip file using Libreoffice so I had to boot up a VM just to extract it using MS Office. What a pain. I really don't like that they instruct you to use a dos disk either. IMHO it's easier to use an EFI shell, so I'm just including the files and different instructions. One thing I found out was that mptsas2.rom bios is exactly the same file that is on Avago's website included with the 9207_8e firmware. ASRock did not include the UEFI BSD bios update (x64sas2.rom). Is it needed? Probably not. I sent off another email about and am waiting on a response for that. Since the mptsas2.rom was the exact same file I took a chance and I downloaded the UEFI BSD bios from Avago's website and flashed it too, successfully. I take NO responsibility if you choose to do that though, in fact discourage it lol, just sharing my findings. The 9207_8e firmware is not the exact file that ASRock sent, but I wouldn't be surprised if it just could have been flashed as well. ASRock's version is more than likely just re-branded (me thinking out loud).

I followed @cyberjock recommended procedure of updating from here

Flash the firmware like below.

Code:

unzip files to root of a fat32 formatted usb stick and plug it in
go into bios and navigate to the exit tab and choose "launch efi shell from filesystem"
access your usb device by typing fs0:
sas2flash.efi -list (not sure why the listsasadd flag does not work for me)
write down your sas address
sas2flash.efi -o -e 7
sas2flash.efi -f ASR2308_p20.fw
sas2flash.efi -b mptsas2.rom
sas2flash.efi -o -sasadd <your sas address from above without dashes>

 

[Z300M]

I may have bricked my m1015 :-(

I am stuck with this firmware Host Boot Failed! error.

I am not really sure what went wrong. Any ideas of what I can try to rescue this card?

I was getting that same error message when I used the package from LSI, but the upgrade worked fine when I used pclausen's p20.zip package -- see a few pages back.

 

[Ericloewe]

So ASRock sent me a word doc with the zip file embedded with instructions for use with a dos bootable disk. You can't get the zip file using Libreoffice so I had to boot up a VM just to extract it using MS Office. What a pain. I really don't like that they instruct you to use a dos disk either. IMHO it's easier to use an EFI shell, so I'm just including the files and different instructions. One thing I found out was that mptsas2.rom bios is exactly the same file that is on Avago's website included with the 9207_8e firmware. ASRock did not include the UEFI BSD bios update (x64sas2.rom). Is it needed? Probably not. I sent off another email about and am waiting on a response for that. Since the mptsas2.rom was the exact same file I took a chance and I downloaded the UEFI BSD bios from Avago's website and flashed it too, successfully. I take NO responsibility if you choose to do that though, in fact discourage it lol, just sharing my findings. The 9207_8e firmware is not the exact file that ASRock sent, but I wouldn't be surprised if it just could have been flashed as well. ASRock's version is more than likely just re-branded (me thinking out loud).

I followed @cyberjock recommended procedure of updating from here

Flash the firmware like below.

Code:

unzip files to root of a fat32 formatted usb stick and plug it in
go into bios and navigate to the exit tab and choose "launch efi shell from filesystem"
access your usb device by typing fs0:
sas2flash.efi -list (not sure why the listsasadd flag does not work for me)
write down your sas address
sas2flash.efi -o -e 7
sas2flash.efi -f ASR2308_p20.fw
sas2flash.efi -b mptsas2.rom
sas2flash.efi -o -sasadd <your sas address from above without dashes>

Protip: Office openXML files (.docx, .xlsx,...) are actually zipped folders in disguise. You can easily decompress them to obtain raw text, XML formatting stuff and any attached files.

Regarding the extension ROM: It is not required. Its only features in IT mode are allowing you to boot from the controller and seeing the structure of attached SAS devices, similar to sas2ircu.
The old BIOS extension will work with UEFI, just like the old P16 one. The UEFI extension should allow for faster booting and maybe the odd nice feature at the UEFI level.

 

[Chupa0]

I was getting that same error message when I used the package from LSI, but the upgrade worked fine when I used pclausen's p20.zip package -- see a few pages back.

I have been using pclausen's package. I tried the files form LSI as well and still have the same issue. Is it maybe because mine is reading as a (B2) version?

 

[Harsesis]

In ran into the firmware issue with the upgrade as well. I'm using a X10SL7-F board and took a look at the firmware. As already stated, Supermicro provides only the older 20.xxxx.02 firmware and not the .04.

Therefore I decied to stick with the older P16 firmware for now. Did I understand correctly that it is not reccomaned for me to upgrade?

Edit: Another short question: I followed this how to for upgrading the LSI firmware. In the how to you just enter nine times zero as ID of the controller. Someone eles in this topic said he entered a specific number for his controller. Is there any disadvantage of using the "nine zeroes method"?

 

[Ericloewe]

In ran into the firmware issue with the upgrade as well. I'm using a X10SL7-F board and took a look at the firmware. As already stated, Supermicro provides only the older 20.xxxx.02 firmware and not the .04.

Therefore I decied to stick with the older P16 firmware for now. Did I understand correctly that it is not reccomaned for me to upgrade?

Edit: Another short question: I followed this how to for upgrading the LSI firmware. In the how to you just enter nine times zero as ID of the controller. Someone eles in this topic said he entered a specific number for his controller. Is there any disadvantage of using the "nine zeroes method"?

Identifying controllers within the system becomes a pain in the ass, drivers/firmware might not like it and it's just generally bad practice.

 

[YpsiNine]

I have a couple of Supermicro SAS2 backplanes, are these needed to be upgraded in one way or the other?
When checking with smart it says this for both backplanes:

=== START OF INFORMATION SECTION ===
Vendor: LSILOGIC
Product: SASX28 A.1
Revision: 7017
Device type: enclosure
Transport protocol: SAS (SPL-3)
Local Time is: Sat Aug 29 14:06:26 2015 CEST
SMART support is: Unavailable - device lacks SMART capability.