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

[AndreStarTrek]

Well this move to the new driver had put me in a little bit of a problem. I been having some problems with the 3x Kingston DTSE9 G2 32GB USB 3.0 (connected on USB2.0) in mirror. But the stick keeps getting checksum and read/write errors, so I decide to migrate to Sandisk cruzer fit 32GB. But of course this sticks where a little bit smaller than the kingston. So upgraded to the latest FreeNAS and backup the config and installed a new FreeNAS on the sandisk sticks. Upgrade FreeNAS again and load the config, to and up with a warning.

I don't want to play with fire so I rollback to the latest 9.3 stable because I don't want to "try" 20.00.02 on my X10SL7-F after reading the post of cyberjock. So should I wait till Supermicro release 20.00.04, anyone know if Supermicro is working on it?

One thing I know, I lost 3 hours of my time and some risk because this driver change was not mentioned in the changelog. I am very grateful of this great software, but it scared me a little bit for a moment and that for something that was not necessary.

 

[Glorious1]

So should I wait till Supermicro release 20.00.04, anyone know if Supermicro is working on it?

A lot of people, including me with a Supermicro board, have had success with danb35's easy-peasy instructions and pclausen's zip file, which has the 20.00.04 version. It doesn't get much easier in do-it-yourself NAS.

 

[AndreStarTrek]

A lot of people, including me with a Supermicro board, have had success with danb35's easy-peasy instructions and pclausen's zip file, which has the 20.00.04 version. It doesn't get much easier in do-it-yourself NAS.

It is not the flashing that worry me, it is using the wrong firmware and loosing the pool. I don't got all this safety precautions like zfs raidz3, ups, redundant psu, and so on to gamble with a firmware. That 20.00.04 firmware is not released for this board and if Asrock got problems with a firmware on there motherboards than Supermicro theoretically can to.

Better save than sorry.

 

[cyberjock]

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

I'd definitely feel the same way. No way I'm going to learn the hard way if my zpool suddenly was inaccessible. :P

It's not that critical to upgrade to 9.3.1. :P

 

[crusader3k4]

Is there a way I can test my current setup (FreeNas 9.3.1 with SM FW 20.00.02.00) for issues concerning the probably "faulty" firmware? What errors might I expect?

Currently everything runs smoothly. I'm thinking about going back to FreeNas 9.3.0 and SM FW 16.

 

[AndreStarTrek]

Is there a way I can test my current setup (FreeNas 9.3.1 with SM FW 20.00.02.00) for issues concerning the probably "faulty" firmware? What errors might I expect?

Currently everything runs smoothly. I'm thinking about going back to FreeNas 9.3.0 and SM FW 16.

Don't know, but I suspect dropping a disk or corrupting the pool. But that is just guesswork, the point is we don't know what could happen and that is the scary part.

 

[bmac6996]

I wanted to chime in and share a lil bit.

Found out that version 9.3.1 is out. Running ESXi 6.0 on a Supermicro X10SL7-F with a almost-gone production 9.3 VM.

I'm currently have a 9211 running in IT mode with no bios and the onboard 2308 is running in IR mode with a pair of 500GB hd running raid 1 for my datastore for ESXi. Both are version 16. The 9211 is set for hardware passthrough for the FreeNas VM.

So now that 9.3.1. updated drivers for the controllers to version 20, I figured might as well upgrade to 9.3.1 and update both lsi cards to version 20 firmware since none of my arrays have data yet.

Updated the 9211 to 20.00.04.00 and the 2308 onboard to supermicro's firmware of 20.00.02.00. Since the 2308 isn't used for freenas, it shouldn't matter what firmware it's on since freenas shouldn't use it or see it.

Well when i rebooted the server, my raid 1 array broke. Upon investigation, one of the hard drives was not seen/missing now. Very strange. Tired a different port on the 2308 controller and still not seen. Traded cables with the known working port and hard drive, and still not seen by 2308 controller. When I moved the "bad" hard drive to the onboard controller on the MOBO, I checked the bios and it recognized the hard drive. Took the hard drive, connected to another PC via USB and did a "clean" in disk part in Win7 and tried it again.. nothing. Took another spare 500gb HD and replaced the "bad" drive and that was seen by the 2308 controller with no issues.. Rebuilding array now. Very strange issue because the drive is apparently dead according to the 2308 after the firnware upgrade but other controllers say otherwise. Any thoughts?


Once this is done, I will create a new VM for 9.3.1 and see what more issues will come about :/.

 

[Chupa0]

FYI for anyone who is having the Host Boot Failed error and think they may have bricked their m1015.
I followed a guide here using megarec to wipe the flash and was able to rescue my card. Of course this was after I had ordered a 2nd m1015. Now I have a backup on hand I guess! Anyway.. my orgional card is rocking again on p20. GOod luck!

 

[patrick0525]

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.

• 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

What are these steps for? My P20 flash went well without it.

 

[patrick0525]

What are these steps for? My P20 flash went well without it.

Nevermind. It was the other *.bin file.

 

[Chameleon]

This is what I did without any problems for the 2nd time on the same card ( 1st time was to flash to p16 it mode some months ago when building my first freenas setup )

Create a Freedos boot usb
downloaded the files from the SAS2008 link from here
http://forums.laptopvideo2go.com/topic/29059-sas2008-lsi92409211-firmware-files/
copied all the files straight onto the freedos boot usb.
downloaded pclausen's zip file ( See post by Glorious1 above ) and copied straight over to the freedos usb drive again replacing any existing files
Shutdown server and unplugged cables from M1015 and booted from the freedos usb.
Followed the instructions from the following link ( including making note of the 50060b number found on the M1015 card )
http://www.servethehome.com/ibm-serveraid-m1015-part-4/

I DID NOT USE THE '-b mptsas2.rom' option.

For the second time, I have flashed my M1015 and all is working as before.

Transmission, Headphones SABnzb, Couchpotatoe and Sickbeard along with Plex worked from the off ( with the cables plugged back in !!! )

Hope this helps.

 

[freenas4n00b]

So i just did a complete backup of my freenas data.

Can someone who has SM X10SL7-F tell me what instructions you ran to get the p20 firmware working?

I tried a command i saw earlier and it failed.
[root@freenas] /mnt/DATASTORE/ServerStuff# sas2flash -c 0 -f UEFI/2308IT20.ROM
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: SAS2308_1(D1)

Executing Operation: Flash Firmware Image

Firmware Image has a Valid Checksum.
Firmware Version 20.00.02.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 Failed!

Firmware Returned Exception. IOCStatus=0x3, IOCLogInfo=0x0
Due to error remaining commands will not be executed.
Unable to Process Commands.
Exiting SAS2Flash.

 

[BigDave]

Can someone who has SM X10SL7-F tell me what instructions you ran to get the p20 firmware working?

@AdrianWilliamson posted his efforts here in this thread

https://forums.freenas.org/index.ph...sion-20-for-dev-mps0.36536/page-4#post-224102

 

[freenas4n00b]

@AdrianWilliamson posted his efforts here in this thread

https://forums.freenas.org/index.ph...sion-20-for-dev-mps0.36536/page-4#post-224102

I dont have IPMI set up though. Hoping for instructions using sas2flash tool

 

[BigDave]

Having read (for two days) the posts in this thread before performing my own update,
most of the owners of the X10SL7-F board seemed to have used the UEFI shell that is built in...
Perhaps some searching on this thread will either reveal the method you seek,
or you could just learn to use the invaluable tool of IMPI, it's there for times just like this
and is not complicated. Or you could just hook up a monitor/keyboard/mouse and do it
the old tried and true way...

 

[Ericloewe]

The instructions are the same, regardless of the flashing tool used, the only difference being that the DOS version is sas2flsh (no 'a' in "flsh"), due to 8.3 filename constraints. Also, the DOS version may or may not require the DOS4GW runtime environment (Remember that? Thank goodness for real memory management).

 

[freenas4n00b]

Weirdness. the command failed through ssh but it worked through mouse/keyboard local to server.

Currently running 20.00.02.00.

Downloaded firmware from SM ftp site and used this command

sas2flash -c 0 -f UEFI/2308IT20.ROM

Also I enabled the wonderful IPMI as you guys suggested.

Thanks!

 

[Jailer]

IPMI is great. You're not going to want to get another motherboard without it.

 

[bustersnm]

Thank you sso much @Spearfoot for your help. After setting up my Freenas I pretty much offloaded all things about firmware updates. Your step by step tutorial helped me resolve my issues. You are correct i didn't have to use Rufus or need the ShellX64.efi. I completed mine per your instructions other then that. Thanks a bunch.

I'll be glad to do so, @HardChargin - I'll try to give fairly detailed instructions; please don't take offense and think I'm being condescending or anything like that if you already know about most of this stuff. :)

I had already installed the update on my FreeNAS server, not realizing that the new version required a firmware update for the on-board LSI HBA. Ooops! I have good backups, so I didn't bother with unplugging the hard disks or taking any of the other steps you described. Your needs may differ in this regard. In any case, my pool loaded up just fine after flashing the HBA.

Before you begin, note that you will need to know the controller's 16-digit SAS address, as the script provided by Supermicro will prompt you for the last 9 digits of it. I had noted down this information when I first constructed the server. If you don't have it handy, you can boot the system and load the LSI option ROM code to get it. (It may also be stamped on the motherboard itself, if feeble memory serves.)

I downloaded Supermicro's P20 firmware zip file (PH20-IT.zip) at this link:

ftp://ftp.supermicro.com/driver/SAS/LSI/2308/Firmware/IT/

Using Rufus on a Windows 7 PC, I created a bootable USB stick and extracted all of the files from the zip archive's \UEFI folder onto its root directory.

I also put a copy of SHELLX64.EFI onto the USB stick, but unfortunately I don't remember where I obtained it - and I don't think this file is required as I used the motherboard's built-in EFI shell. On reflection, I'm not even certain the USB stick needs to be bootable, since, again, I used the built-in EFI shell.

After gracefully powering down the FreeNAS server, I used IPMIView's KVM console on the same Windows 7 PC to mount the USB stick as virtual media on the FreeNAS server. I then powered up the server, entered 'Setup', and loaded the built-in EFI shell:

View attachment 8507

After the UEFI shell loaded, I entered 'fs0:' to select the USB stick as my current drive. (Note that your USB stick may not be located at 'fs0:' and you may in that case have to find it by trial and error.) Here is how my screen appeared after also entering a dir command to show the files on the USB drive:

View attachment 8508

Once you (finally!) get to this point, all you need to do is execute the Supermicro script by entering SMC2308T.NSH at the command prompt. After trundling along and doing its job, the script will eventually ask you for the 9-digit SAS ID. Once it completes you're done and can reboot the system.

Good luck!

 

[Peter Jakab]

Updated the 9211 to 20.00.04.00 and the 2308 onboard to supermicro's firmware of 20.00.02.00. Since the 2308 isn't used for freenas, it shouldn't matter what firmware it's on since freenas shouldn't use it or see it.

Well when i rebooted the server, my raid 1 array broke. Upon investigation, one of the hard drives was not seen/missing now. Very strange. Tired a different port on the 2308 controller and still not seen.
......

I upgraded my new test X9SRH-7F in simple USB UEFI stick way to Supermicro 20.00.02.00 (not the 20.00.04.00) without any problem. Under my upgrade I don't disconnect any disk my raidz2 with 4 disk still reachable without any problem. But this is old 500GB disks could you configuration is not same as my. And this is my test system without any important data. Will reinstalled before productive usage.

I think the best idea was mentioned above (for production boxes) wait for Supermicro provide 20.00.04 and just to 9.3.1 and firmware.

Bye,
Jackson