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

pechkin000 · Oct 28, 2015

I was wondering if someone could point me to the correct firmware to download for my controller? This is my current "sas2flash -listall" output:

Code:

LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

        Adapter Selected is a LSI SAS: SAS2008(B2)

Num   Ctlr            FW Ver        NVDATA        x86-BIOS         PCI Addr
----------------------------------------------------------------------------

0  SAS2008(B2)     16.00.00.00    10.00.00.06    07.29.00.00     00:02:00:00

I appreciate any help on this! Cheers

jgreco · Oct 28, 2015

It depends on the version of FreeNAS you're using. Use P16 for 9.3 and below. Use P20 for 9.3.1 and beyond.

pechkin000 · Oct 28, 2015

I am using 9.3.1 and the sticker on my controller says SAS9220-8i. I understand that I need to get version 20 of the firmware I am just not sure where to go to get it.
Thanks for a quick reply!
I saw links in previous posts but none of them seem to be for 9220 or 2008b..unless its all the same.
For example Avago site has this: http://www.avagotech.com/products/server-storage/raid-controllers/megaraid-sas-9240-8i#downloads
but its for 9240 not 9220, does it matter?

jgreco · Oct 28, 2015

http://docs.avagotech.com/docs/12350530

pechkin000 · Oct 28, 2015

Thank you jgreco. Couple more stupid questions. My card should be in the IT mode right? also do i need to use DOS utility? can i not just use Sas2flash utility on freenas box without booting from the dos disk?

jgreco · Oct 28, 2015

Not a stupid question. It suggests you've read-but-not-done. It is good to be just-a-little-cautious here.

Use the IT firmware. If your card currently has a BIOS, also update the BIOS. You may use the sas2flash utility on the FreeNAS box if (and only if) you do not have the pool mounted; this implies that either you must export the pool and do the work from the console, or do it in singleuser mode. Either way, the use of an external USB thumb drive to hold the firmware eliminates some complexity. After flashing, halt the machine ("halt -q -p") and make sure it powers off. When it comes back, voila, should be P20.

pechkin000 · Oct 28, 2015

@jgreco : you are awesome! Thanks you!

Code:

[root@freenas] ~# sas2flash -listall
LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

        Adapter Selected is a LSI SAS: SAS2008(B2)

Num   Ctlr            FW Ver        NVDATA        x86-BIOS         PCI Addr
----------------------------------------------------------------------------

0  SAS2008(B2)     20.00.04.00    14.01.00.08    07.39.00.00     00:02:00:00

jgreco · Oct 28, 2015

Not a problem

TXAG26 · Oct 31, 2015

Is there a page that shows the driver version status in upcoming versions of FreeNAS? I'd really like to follow this as Supermicro released the PH10 firmware for the LSI 3008, but the current FreeNAS driver has PH9 drivers.

Does anyone know if TrueNAS is on PH10 drivers yet?

The Gecko · Oct 31, 2015

My experiences updating to P20 on an LSI 9200-16e...

For starters, you should learn how to enumerate all the controllers on your server.
Two applications will help you accomplish this: 'sas2flash' and 'sas2ircu'.

In this example, we are upgrading the firmware on an LSI 9200-16e PCIE SAS2 HBA from firmware v6 to v20. There is only one controller present in the machine. According to this post, the 9200-16i can be flashed with the 9201-16i firmware. I thought I would take the chance and flash my 9200-16e to 9201-16i firmware.
https://forums.servethehome.com/ind...s9200-16e-vs-lsi-sas9201-16e.5115/#post-48200

Check the server's FreeNAS home page --> Upper Right Corner --> Blinking Red Light?
Before the firmware upgrade, the light was blinking red. Clicking on it indicated a firmware upgrade was needed on the SAS controller.

No hard drives were installed in the server during this process.

The Operating System used was FreeNAS 9.3.1, build FreeNAS-9.3-STABLE-201509282017.
The applications 'sas2flash' and 'sas2ircu' are already installed on this OS by default.

This was performed on a SuperMicro X8DTE motherboard without UEFI.

#####################################################################
Enumerate all the SAS controllers using 'sas2flash'

sas2flash -listall

Output:

Code:

LSI Corporation SAS2 Flash Utility

Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

  Adapter Selected is a LSI SAS: SAS2116_1(B0)

Num  Ctlr           FW Ver       NVDATA       x86-BIOS     PCI Addr
----------------------------------------------------------------------------

0    SAS2116_1(B0)  06.00.00.00  06.05.00.04  07.07.00.00  00:06:00:00

  Finished Processing Commands Successfully.
  Exiting SAS2Flash.

#####################################################################
Enumerate the SAS controllers using 'sas2ircu'

sas2ircu list

Output:

Code:

LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.


 Adapter  Vendor        Device  SubSys  SubSys
 Index    Type          ID      ID      Pci Address        Ven ID  Dev ID
 -----    ------------  ------  ------  -----------------  ------  ------
  0       SAS2116_1     1000h   64h     00h:06h:00h:00h    1000h   3030h

SAS2IRCU: Utility Completed Successfully.

#####################################################################
#####################################################################
Next, learn how to extract the SAS Address (WWN) of each controller.
As before, two applications will help you accomplish this: 'sas2flash' and 'sas2ircu'.

#####################################################################
List the SAS address (WWN) of controller number 0 using 'sas2flash'

sas2flash -o -c 0 -listsasadd

Output:

Code:

LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

  Advanced Mode Set

  Adapter Selected is a LSI SAS: SAS2116_1(B0)

  The SAS Address for the controller is: 500605b-0-01ea-5b20

  Finished Processing Commands Successfully.
  Exiting SAS2Flash.

#####################################################################
List the SAS Address (WWN or Logical_ID) of Controller 0 using 'sas2ircu'.

sas2ircu 0 display | grep "Logical ID";

Output:

Code:

Logical ID  : 500605b0:01ea5b20

#####################################################################
#####################################################################
Format the SAS Address by removing all colons and/or dashes.
Never having done this process before, I didn't know if the firmware update procedure would blank out the SAS address. The SAS address was blanked during the M1015 to 9211-8i process. We will hold on to this information just in case.

500605b-0-01ea-5b20 --> 500605b001ea5b20
500605b0:01ea5b20 --> 500605b001ea5b20

#####################################################################
#####################################################################
Flash the new firmware to controller 0.

sas2flash -o -c 0 -f 9201-16e.bin

Output:

Code:

LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

  Advanced Mode Set

  Adapter Selected is a LSI SAS: SAS2116_1(B0)

  Executing Operation: Flash Firmware Image

  Firmware Image has a Valid Checksum.
  Firmware Version 20.00.04.00
  Firmware Image compatible with Controller.

  Valid NVDATA Image found.
  NVDATA Version 14.01.00.00
  Checking for a compatible NVData image...

  NVDATA Device ID and Chip Revision match verified.
  NVDATA Versions Compatible.
  Valid Initialization Image verified.
  Valid BootLoader Image verified.

  Beginning Firmware Download...
  Firmware Download Successful.

  Verifying Download...

  Firmware Flash Successful.

  Resetting Adapter...
  Adapter Successfully Reset.

  Finished Processing Commands Successfully.
  Exiting SAS2Flash.

#####################################################################
#####################################################################
Verify the firmware upgrade by enumerating all the SAS controllers using 'sas2flash'

sas2flash -listall

Output:

Code:

LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

  Adapter Selected is a LSI SAS: SAS2116_1(B0)

Num  Ctlr           FW Ver       NVDATA       x86-BIOS     PCI Addr
----------------------------------------------------------------------------

0    SAS2116_1(B0)  20.00.04.00  14.01.00.07  07.07.00.00  00:06:00:00

  Finished Processing Commands Successfully.
  Exiting SAS2Flash.


The flash process was successful

#####################################################################
Did the SAS address of controller 0 get blanked out?

sas2ircu 0 display | grep "Logical ID";

Output:

Code:

Logical ID  : 500605b0:01ea5b20

No. Therefore, there is no need to set the SAS Address.
If yes, then use this command to set the SAS address on controller 0
Conceptual: sas2flash -o -c 0 -sasadd <SAS_Address>
Example: sas2flash -o -c 0 -sasadd 500605b001ea5b20

#####################################################################
#####################################################################
Reboot the server
Check the server's FreeNAS home page --> Upper Right Corner --> Blinking Red Light?
Before the firmware upgrade, the light was blinking red. Clicking on it indicated a
firmware upgrade was needed on the SAS controller.
After the firmware upgrade and system reboot, the blinking red light turned into a solid green light.

Done!

The Gecko · Oct 31, 2015

My experiences updating to P20 on three M1015 controllers simultaneously...

#####################################################################
#####################################################################
For starters, you should learn how to enumerate all the controllers on your server.
Two applications will help you accomplish this: 'sas2flash' and 'sas2ircu'.

In this example, we are upgrading the firmware on three IBM M1015 PCIE SAS2 HBAs from firmware v6 to v20. All three controllers were installed simultaneously in the machine. The M1015 is almost identical to the LSI 9220-8i and LSI 9211-8i. These three M1015 controllers were already changed to IT mode using this How-To:
http://www.servethehome.com/ibm-serveraid-m1015-part-4/

Check the server's FreeNAS home page --> Upper Right Corner --> Blinking Red Light?
Before the firmware upgrade, the light was blinking red. Clicking on it indicated a firmware upgrade was needed on the SAS controller.

No hard drives were installed in the server during this process.

The Operating System used was FreeNAS 9.3.1, build FreeNAS-9.3-STABLE-201509282017.
The applications 'sas2flash' and 'sas2ircu' are already installed on this OS by default.

This was performed on a SuperMicro X8DTE motherboard without UEFI.

#####################################################################
Enumerate all the SAS controllers using 'sas2flash'

sas2flash -listall

Output:

Code:

LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

  Adapter Selected is a LSI SAS: SAS2008(B2)

Num  Ctlr         FW Ver       NVDATA       x86-BIOS  PCI Addr
----------------------------------------------------------------------------

0    SAS2008(B2)  16.00.00.00  10.00.00.06  No Image  00:09:00:00
1    SAS2008(B2)  16.00.00.00  10.00.00.06  No Image  00:06:00:00
2    SAS2008(B2)  16.00.00.00  10.00.00.06  No Image  00:05:00:00

  Finished Processing Commands Successfully.
  Exiting SAS2Flash.

#####################################################################
Enumerate the SAS controllers using 'sas2ircu'

sas2ircu list

Output:

Code:

LSI Corporation SAS2 IR Configuration Utility.
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved.


 Adapter  Vendor        Device  SubSys  SubSys
 Index    Type          ID      ID      Pci Address        Ven ID  Dev ID
 -----    ------------  ------  ------  -----------------  ------  ------
  0       SAS2008       1000h   72h     00h:09h:00h:00h    1000h   3020h

 Adapter  Vendor        Device  SubSys  SubSys
 Index    Type          ID      ID      Pci Address        Ven ID  Dev ID
 -----    ------------  ------  ------  -----------------  ------  ------
  1       SAS2008       1000h   72h     00h:06h:00h:00h    1000h   3020h

 Adapter  Vendor        Device  SubSys  SubSys
 Index    Type          ID      ID      Pci Address        Ven ID  Dev ID
 -----    ------------  ------  ------  -----------------  ------  ------
  2       SAS2008       1000h   72h     00h:05h:00h:00h    1000h   3020h

SAS2IRCU: Utility Completed Successfully.

#####################################################################
#####################################################################
Next, learn how to extract the SAS Address (WWN) of each controller.
As before, two applications will help you accomplish this: 'sas2flash' and 'sas2ircu'.

#####################################################################
List the SAS address (WWN) of each controller using 'sas2flash'

sas2flash -o -c 0 -listsasadd | grep "SAS Address"
The SAS Address for the controller is: 500605b-0-094a-8ac0

sas2flash -o -c 1 -listsasadd | grep "SAS Address"
The SAS Address for the controller is: 500605b-0-0809-ff10

sas2flash -o -c 2 -listsasadd | grep "SAS Address"
The SAS Address for the controller is: 500605b-0-094a-8a10

#####################################################################
List the SAS Address (WWN or Logical_ID) of each controller using 'sas2ircu'.

sas2ircu 0 display | grep "Logical ID"
Logical ID : 500605b0:094a8ac0

sas2ircu 1 display | grep "Logical ID"
Logical ID : 500605b0:0809ff10

sas2ircu 2 display | grep "Logical ID"
Logical ID : 500605b0:094a8a10

#####################################################################
#####################################################################
Format the SAS Address by removing all colons and/or dashes.
You might need this later in the process.

500605b-0-094a-8ac0 --> 500605b0094a8ac0
500605b0:094a8ac0 --> 500605b0094a8ac0

#####################################################################
#####################################################################
Flash the new firmware to controller 0.

sas2flash -o -fwall 2118it.bin

Output:

Code:

LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

  Ignoring All other commands except for output flags
  Advanced Mode Set


  Attempting to flash firmware to LSI SAS SAS2008(B2)  :

  Executing Operation: Flash Firmware Image

  Firmware Image has a Valid Checksum.
  Firmware Version 20.00.04.00
  Firmware Image compatible with Controller.

  Valid NVDATA Image found.
  NVDATA Version 14.01.00.00
  Checking for a compatible NVData image...

  NVDATA Device ID and Chip Revision match verified.
  NVDATA Versions Compatible.
  Valid Initialization Image verified.
  Valid BootLoader Image verified.

  Beginning Firmware Download...
  Firmware Download Successful.

  Verifying Download...

  Firmware Flash Successful.

  Resetting Adapter...
  Adapter Successfully Reset.


  Attempting to flash firmware to LSI SAS SAS2008(B2)  :

  Executing Operation: Flash Firmware Image

  Firmware Image has a Valid Checksum.
  Firmware Version 20.00.04.00
  Firmware Image compatible with Controller.

  Valid NVDATA Image found.
  NVDATA Version 14.01.00.00
  Checking for a compatible NVData image...

  NVDATA Device ID and Chip Revision match verified.
  NVDATA Versions Compatible.
  Valid Initialization Image verified.
  Valid BootLoader Image verified.

  Beginning Firmware Download...
  Firmware Download Successful.

  Verifying Download...

  Firmware Flash Successful.

  Resetting Adapter...
  Adapter Successfully Reset.


  Attempting to flash firmware to LSI SAS SAS2008(B2)  :

  Executing Operation: Flash Firmware Image

  Firmware Image has a Valid Checksum.
  Firmware Version 20.00.04.00
  Firmware Image compatible with Controller.

  Valid NVDATA Image found.
  NVDATA Version 14.01.00.00
  Checking for a compatible NVData image...

  NVDATA Device ID and Chip Revision match verified.
  NVDATA Versions Compatible.
  Valid Initialization Image verified.
  Valid BootLoader Image verified.

  Beginning Firmware Download...
  Firmware Download Successful.

  Verifying Download...

  Firmware Flash Successful.

  Resetting Adapter...
  Adapter Successfully Reset.

  Finished Processing Commands Successfully.
  Exiting SAS2Flash.

#####################################################################
#####################################################################
Verify the firmware upgrade by enumerating all the SAS controllers using 'sas2flash'

sas2flash -listall

Output:

Code:

LSI Corporation SAS2 Flash Utility
Version 16.00.00.00 (2013.03.01)
Copyright (c) 2008-2013 LSI Corporation. All rights reserved

  Adapter Selected is a LSI SAS: SAS2008(B2)
 
Num  Ctlr         FW Ver       NVDATA       x86-BIOS  PCI Addr
----------------------------------------------------------------------------

0    SAS2008(B2)  20.00.04.00  14.01.00.08  No Image  00:09:00:00
1    SAS2008(B2)  20.00.04.00  14.01.00.08  No Image  00:06:00:00
2    SAS2008(B2)  20.00.04.00  14.01.00.08  No Image  00:05:00:00

  Finished Processing Commands Successfully.
  Exiting SAS2Flash.


The flash process was successful

#####################################################################
Did the SAS address of each controller get blanked out?

sas2ircu 0 display | grep "Logical ID"
Logical ID : 500605b0:094a8ac0

sas2ircu 1 display | grep "Logical ID"
Logical ID : 500605b0:0809ff10

sas2ircu 2 display | grep "Logical ID"
Logical ID : 500605b0:094a8a10

No. Therefore, there is no need to set the SAS Address.
If yes, then use this command to set the SAS address on controller 0
Conceptual: sas2flash -o -c 0 -sasadd <SAS_Address>
Example: sas2flash -o -c 0 -sasadd 500605b0094a8ac0

#####################################################################
#####################################################################
Reboot the server
Check the server's FreeNAS home page --> Upper Right Corner --> Blinking Red Light?
Before the firmware upgrade, the light was blinking red. Clicking on it indicated a firmware upgrade was needed on the SAS controller.
After the firmware upgrade and system reboot, the blinking red light turned into a solid green light.

Done!

IanWorthington · Nov 2, 2015

OK, I got this WARNING message tonight after doing a FreeNAS upgrade. IIUC I should NOT run with mismatched drivers/firmware, so I've fallen back to my previous FreeNAS level.

Also, iiuc, updating the firmware is dangerous unless I have a backup of my NAS, which I do NOT.

Is this correct?

Ian

Brosif_My_Nif · Nov 2, 2015

IanWorthington said:
OK, I got this WARNING message tonight after doing a FreeNAS upgrade. IIUC I should NOT run with mismatched drivers/firmware, so I've fallen back to my previous FreeNAS level.

Also, iiuc, updating the firmware is dangerous unless I have a backup of my NAS, which I do NOT.

Is this correct?

Ian

Disconnect your pool from your card before upgrading the firmware and you should not have any problems.

msbxa · Nov 6, 2015

Don't forget to mark the drives and their locations before you disconnect them from the card.

9C1 Newbee · Nov 6, 2015

msbxa said:
Don't forget to mark the drives and their locations before you disconnect them from the card.

Why?

msbxa · Nov 6, 2015

I've read somewhere from this forum. Can't find it where, Maybe someone can confirm this.

danb35 · Nov 6, 2015

There's no need to connect the drives back to the same places they were--ZFS is smart enough to figure that out.

9C1 Newbee · Nov 6, 2015

danb35 said:
There's no need to connect the drives back to the same places they were--ZFS is smart enough to figure that out.

This^^

JTheNASBuilder · Nov 6, 2015

danb35 said:
Using the FreeBSD sas2flash executable (which is part of the FreeNAS base) worked just fine for me once I'd installed the 9.3.1 update (I'm guessing it wouldn't do the flash before the update because I was still running the P16 driver?). Here's what I did:

Download pclausen's P20.zip file and unzip it somewhere on the pool

Install the FreeNAS update and reboot

SSH in to the box as root, and navigate to where I'd unzipped P20.zip

sas2flash -fwall 2118it.bin -b mptsas2.rom

Reboot

This was with an M1015 that was already cross-flashed to IT mode with the P16 firmware. No need to boot from USB sticks, into EFI shells, etc.

You have no idea what a headache you saved me. Huge thanks for this tip, my friend.

pclausen said:
Wow, didn't realize that was possible. Sure would have saved me a lot of time not having to pull out the chassis and pull out each HBA one by one. In cases where you have multiple controllers installed in the same server, would the above sas2flash command update all the controllers at once? Would there be any risks associated with doing it that way with multiple controllers? I know a lot of the M1015 instructions floating around caution to always unplug/remove everything other than the specific controller you want to update. Maybe those instructions were all put together by folks with a healthy dose of paranoia as Ericloewe eluded to? :)

If you have multiple cards it seems to work just fine. I had multiple identical cards and it applied the firmware flash to them sequentially. I have no idea what it would do if they weren't identical? Error out?

STREBLO · Nov 6, 2015

OK, i'm freaking out a bit.

I have the X10SL7-F and when installed FreeNAS I was informed that my firmware did not match version 20. I then tried to update my firmware in the EFI shell using the supermicro SMC2308.NSH file over IPMI. All seem to work ok but then upon rebooting I'm getting a scary message saying 1 of 6 supported devices are present for system boot and I have no idea what's going on. Before all 6 of my drives were being detected fine. Did I just screw something up? I do not have a pool set up and there is no data on my hard drives but they were plugged in during my firmware update, have I screwed something up?

Important Announcement for the TrueNAS Community.

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

Explorer

Resident Grinch

Explorer

Resident Grinch

Explorer

Resident Grinch

Explorer

Resident Grinch

Patron

Dabbler

Dabbler

Contributor

Explorer

Contributor

Patron

Contributor

Hall of Famer

Patron

Dabbler

Patron

Similar threads