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

[Ericloewe]

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.

Backplanes don't have any SMART data to share.

The firmware is upgradeable, but expander firmware is much less documented than HBA firmware/driver. I would try to update to the latest version the manufacturer has made available.

 

[Darren Myers]

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.

see here for flashing the backplane https://forums.freenas.org/index.ph...on-1st-freenas-build.28814/page-6#post-196937

 

[YpsiNine]

Backplanes don't have any SMART data to share.

The firmware is upgradeable, but expander firmware is much less documented than HBA firmware/driver. I would try to update to the latest version the manufacturer has made available.

Yes I know that the backplane don't have any smart data to share, this was just to show the version/revision of the backplane.
I cannot find any FW for Supermicro backplanes on their site, either they don't provide it or I am simply just missing it.

Thanks,
Y

 

[Darren Myers]

Yes I know that the backplane don't have any smart data to share, this was just to show the version/revision of the backplane.
I cannot find any FW for Supermicro backplanes on their site, either they don't provide it or I am simply just missing it.

Thanks,
Y

See my post above yours

 

[YpsiNine]

see here for flashing the backplane https://forums.freenas.org/index.ph...on-1st-freenas-build.28814/page-6#post-196937

Interesting, thanks for the link. I have 2 of the BPN-SAS-836EL2 backplanes, so not sure if that 826 FW can be used. Also, I do not run any linux system so it seems very hard to do the upgrade.
In any case, both my HBA's have been updated to FW20 now and it's all good with 9.3.1.

 

[BigDave]

After getting the email regarding the available update to 9.3, I logged in to the GUI and first read the Train Descriptions
and not seeing anything of concern, went ahead with the update procedure. To my surprise the alert came up regarding
the mismatch of the m1015 driver/firmware. At first, I thought I must have missed something in the descriptions of
the pending changes, so I just went back to the previous boot environment and rebooted
I then went back into the System>Boot and deleted the bottom entry of STABLE-201508250051:D just like it never happened!!!
I then discovered the forum posts regarding the move to P20 driver and read all I could regarding what had occured
and how everyone was handling up on things. I have flashed the P20 firmware on my M1015 card and wanted to post
my steps in case someone could benefit, so here goes...
A couple of mentions here before beginning, first off my M1015 has been installed for a long while and has already
been cross flashed (without boot ROM) and has been running without issue with the P16 FW and IT mode and
because of this, my process is much easier and quicker than configuring a "new" card.
Thanks to @cyberjock for his conservative method of protecting the pool from possible issues by unhooking the drives
before flashing the card.
I used my Windows 7 machine and rufus 2.2 to create a DOS boot USB 8GB thumb drive. I then placed two files
on the drive. sas2flash.efi and the 2118.bin which contains 2118it.bin ver: 20.00.04.00 Release date: 21-MAY-15.
I shut down my machine, turn off my power supply and pushed in the start button on the case to bleed any stored power.
I then unplugged the two mini SAS connectors from my card (taking all the drives out of the process) and plugged in
the flashdrive into the onboard USB port (my onboard USB port is empty cause I have an SSD for a boot drive).
Going back to my desktop, I logged in to IPMI and started the remote console.
First I went into the BIOS and made the UEFI the first boot option on my X9SLM -F Mobo.
THE COMMANDS BELOW DO NOT INCLUDE THE < AND THE > ;)
Then using the console I rebooted. Once in the UEFI shell, from the cursor I typed <mount fs0>
at that cursor I typed <sas2flash.efi>
sas2flash started and then allowed me to type <sas2flash -o -f 2118it.bin>
the program flashed the card, initialized it and that was it.(no frikin messin' with SAS address crap):p
I then typed <sas2flash -listall>
The output showed the card to now be on the new firmware.
Exit the shell and shut down your FreeNAS machine, remove the DOS boot drive and using the IPMI remote console,
boot back into your motherboads BIOS and change back the boot order to your regular FreeNAS boot drive.
Boot up your FreeNAS and enter the GUI. Perform the update.
If everything goes well you now have both the new driver (9.3.1) and the new firmware without a mismatch.
Shut down your machine, hook up your mini SAS cables and reboot. I hate mistakes and cause I make my living outside
of the computer world, I tend to tread very soft and slow when it comes to this kind of thing. But my experience was
stress free and I hope yours will be too (or WAS too)
Regards,
Dave

 

[Underwater Mike]

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

Ditto. I just discovered the issue this morning.

I have an AsRock mobo and LSI card. The mainboard doesn't permit DOS-based flash and, given that I don't know squat about Linux, I can't do it from within FreeNAS and have to use the EFI method. Last time I went through this around six months ago -- to downgrade the firmware on the LSI card -- it was a major event for me. I'm hoping that it's a bit easier this time around.

 

[Ericloewe]

I don't know squat about Linux

It's not Linux, and if you have ever used a command line (Be it DOS or *nix), it's easy to follow the instructions.

 

[Underwater Mike]

It's not Linux, and if you have ever used a command line (Be it DOS or *nix), it's easy to follow the instructions.

Sorry I misspoke. Regardless, after a cursory search, I'm still unfamiliar with actions such as creating a temporary directory on the pool, moving and copying files there, etc. Seems to me the EFI method would be safer in my case, no?

 

[Ericloewe]

I prefer UEFI, but using the FreeBSD flasher is also easy, since the parts you'd need to read about (copying, moving, etc) can be done to a share, followed by cd mnt/poolname/sharename/directory.

 

[demon]

For what it's worth, I just did the upgrade on my FreeNAS box (the one with the ASRock C2750D4i and LSI SAS9211-8i from my signature). I ran the upgrade from the command line while FreeNAS was still running (it was idle, as I'm the only user). The firmware update went off without a hitch, and the mps driver rediscovered the SAS board after the reset the 'sas2flash' tool did. I'm running a full scrub now just in case, but 'zpool status' shows all the drives as ONLINE and seems happy (and 0 scrub errors)

I like to live on the edge.

 

[Underwater Mike]

For what it's worth, I just did the upgrade on my FreeNAS box (the one with the ASRock C2750D4i and LSI SAS9211-8i from my signature). I ran the upgrade from the command line while FreeNAS was still running (it was idle, as I'm the only user). The firmware update went off without a hitch, and the mps driver rediscovered the SAS board after the reset the 'sas2flash' tool did. I'm running a full scrub now just in case, but 'zpool status' shows all the drives as ONLINE and seems happy (and 0 scrub errors)

I like to live on the edge.

If you have a chance, could you tell me how you did that? I'm still struggling with how to even navigate to the correct directory from the command line if I copy the files to a pool drive from Windows.

 

[demon]

If you have a chance, could you tell me how you did that? I'm still struggling with how to even navigate to the correct directory from the command line if I copy the files to a pool drive from Windows.

Sure.

• First, download the appropriate firmware for your LSI SAS board; this was the appropriate page for mine. Download the Phase 20 (P20) firmware bundle (for mine, it was "9211_8i_Package_P20_IR_IT_Firmware_BIOS_for_MSDOS_Windows", under the "Firmware" grouping). That it says "MSDOS_Windows" is irrelevant; they include the firmware updater tools for those, but FreeNAS has the "sas2flash" tool in the path when you log in.
• Next, unzip the ZIP file that you download. Upload (via whatever protocol, I sent it to my user account homedir via scp) the following file(s):
  • Firmware/HBA_9211_8i_IT/2118it.bin - This is the actual adapter ROM image. You will 100% need this.
    
  • sasbios_rel/mptsas2.rom - This is the adapter BIOS. If you have the BIOS already in your card's ROM, go ahead and update it too; if you manually erased the ROM and don't have it on the card, you don't need it.
• (Optional, but recommended) If you think any of the services running on your FreeNAS box might be used out from under you while you're doing this, stop them through the web interface. Use the Services page and (if you're using any plugins) the Plugins and/or Jails pages to stop them.
• SSH into your FreeNAS box - either directly as root, or use 'sudo' or 'su' to become root (depending on how you've set things up). (You should probably be able to run this via the "Shell" feature of the web interface, though via the IPMI console would probably be a better choice if you're not familiar with SSH.)
• 'cd' into the directory where you uploaded the files I mentioned above.
• Run 'sas2flash -listall' to list your adapters (this is from after I updated the firmware):
  
  Code:

  # 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:01:00:00
  
      Finished Processing Commands Successfully.
      Exiting SAS2Flash.

• If you haven't lost your nerve by now, run 'sas2flash -c 0 -f 2118it.bin -b mptsas2.rom' to update the firmware and BIOS ROM (if you don't want/need the BIOS ROM, just run 'sas2flash -c 0 -f 2118it.bin'. Borrowing example from another poster, because I didn't save mine.)
  
  Code:

  # sas2flash -fwall 2118it.bin
  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
  
  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.

  
  
• This will take a couple minutes; most of the time for mine was sitting at "Resetting Adapter..." Once the firmware update is done, and your adapter has reset itself, you'll see stuff like this in 'dmesg' (and on the console):
  
  Code:

  mps0: Reinitializing controller,
  mps0: Warning: io_cmds_active is out of sync - resynching to 0
  [...]
  mps0: Firmware: 20.00.04.00, Driver: 20.00.00.00-fbsd
  mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
  mps0: mps_reinit finished sc 0xfffffe0000a9c000 post 4 free 3
  mps0: Unfreezing SIM queue
  mps0: SAS Address for SATA device = d2694759f4bbd189
  mps0: SAS Address from SATA device = d2694759f4bbd189
  mps0: SAS Address for SATA device = d2675e5bf4e1c88b
  mps0: SAS Address from SATA device = d2675e5bf4e1c88b
  mps0: SAS Address for SATA device = d27d5e4df2c9d785
  mps0: SAS Address from SATA device = d27d5e4df2c9d785
  mps0: SAS Address for SATA device = d2675a4bf2e1d195
  mps0: SAS Address from SATA device = d2675a4bf2e1d195
  mps0: SAS Address for SATA device = d2675a4bf2e0c080
  mps0: SAS Address from SATA device = d2675a4bf2e0c080
  mps0: SAS Address for SATA device = d27d5b53d9bacc93
  mps0: SAS Address from SATA device = d27d5b53d9bacc93

• Take a breath, you're all done. Restart those services you stopped, if you stopped any above.

That's pretty much it.

 

[Underwater Mike]

First, let me say thank you. Second, let me say that, despite a doctorate in a technical field, you lost me at:

• Next, unzip the ZIP file that you download. Upload (via whatever protocol, I sent it to my user account homedir via scp) the following file(s):

• • Firmware/HBA_9211_8i_IT/2118it.bin - This is the actual adapter ROM image. You will 100% need this.
  • sasbios_rel/mptsas2.rom - This is the adapter BIOS. If you have the BIOS already in your card's ROM, go ahead and update it too; if you manually erased the ROM and don't have it on the card, you don't need it.
• SSH into your FreeNAS box - either directly as root, or use 'sudo' or 'su' to become root (depending on how you've set things up).

Etc.

Maybe I'd just better stick to the UEFI method. I appreciate the attempt to move me past knuckle-dragger status, though. ;)

 

[demon]

First, let me say thank you. Second, let me say that, despite a doctorate in a technical field, you lost me at:


Maybe I'd just better stick to the UEFI method. I appreciate the attempt to move me past knuckle-dragger status, though. ;)

Hah, okay, nothing wrong with playing it safe.

 

[boyett]

@BigDave
I got 3 M1015 that needs an FW update, FreeNAS already running 9.3.1. I'll try to follow your FW update procedure, but I need to know where did you get those "sas2flash.efi and the 2118.bin which contains 2118it.bin ver: 20.00.04.00 Release date: 21-MAY-15"? Any help is highly appreciated. Thanks

 

[BigDave]

http://www.cstone.net/~dk/p20.zip
Hope this link works, my iPad is having trouble this morning
and the file only appears for a split second?
If the link is broken, just go to post#14 in this thread (page 1)
and it's right there...

You can also get them here

 

[boyett]

Thanks.. BigDave.

 

[kamal juck]

I've been waiting for a while on this update. I was on v20 and getting errors for a while now. Today I was about to downgrade my M1015 card's driver when found this thread.

Here are my steps (I'm on a Mac and new to freeNAS, and trying to list all the steps for noobs like myself ) they are based on danb35 posts.

• SAS2008(B1) card was on v20.00.00 firmware before the upgrade (yes, a newbie mistake) on a ASUS Z87-A motherboard
  
• I had already downloaded and applied the FreeNAS 9.1 update

1. Downloaded "pclausen's" P20.zip file and unzipped on my Mac. ( just click on the link to find the files)
2. Copied P20 files over to AFP folder on my FreeNAS box (just drag and drop, very simple)
3. using terminal on the Mac, SSH in to the box as root, and navigate folder to where I'd copied the P20 files
4. to upgrade the card type: sas2flash -fwall 2118it.bin -b mptsas2.rom
5. Rebooted the system
6. Logged back into the FreeNAS via SSH typed: sas2flash -listall command to confirm the update worked

This was very painless, I didn't have to create a USB boot etc. Thanks to everyone who has posted here.

Cheers, and best of luck everyone else.
Kamal


Thanks to:
danb35
pcLausen

 

[crusader3k4]

Last Sunday I updated my Supermicro X10SL7-F to FW v20.00.02 from Supermicro's ftp. Updateprocess went flawlessly.