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

Status
Not open for further replies.

Haysden Smart

Dabbler
Joined
Sep 2, 2015
Messages
20
OK, so i have been over this thread several times looking for an answer and am yet to find one. I have an IBM M1015 Flashed to IT mode V 20.00.04.00.
My FreeNas system returns an alarm saying Driver is 20.00.00.00 - Firmware is 20.00.04.00
I then get many errors returning "mps0: warning: io_cmds_active is out of sync - resyncing to 0
After several of these errors the M1015 appears to re initiate and retrieves the drive ID's
Low and behold 2 minutes later it all happens over and over again.

My Data is safe and my FreeNAS is functioning, however this does delay data access from the drives. I believe it is if the drives have spun down and upon waking them up the card has some fort of malfunction.

I did not install the bios rom image when flashing, only the LSI Firmware.

Somebody PLEASE help.
 

rogerh

Guru
Joined
Apr 18, 2014
Messages
1,111
OK, so i have been over this thread several times looking for an answer and am yet to find one. I have an IBM M1015 Flashed to IT mode V 20.00.04.00.
My FreeNas system returns an alarm saying Driver is 20.00.00.00 - Firmware is 20.00.04.00
I then get many errors returning "mps0: warning: io_cmds_active is out of sync - resyncing to 0
After several of these errors the M1015 appears to re initiate and retrieves the drive ID's
Low and behold 2 minutes later it all happens over and over again.

My Data is safe and my FreeNAS is functioning, however this does delay data access from the drives. I believe it is if the drives have spun down and upon waking them up the card has some fort of malfunction.

I did not install the bios rom image when flashing, only the LSI Firmware.

Somebody PLEASE help.
If that is in 9.3.1-STABLE it sounds like a bug you need to report.
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
iX has contacts with LSI, so they're probably an appropriate first contact regarding LSI SAS problems.
 

barthezz

Cadet
Joined
Sep 17, 2015
Messages
1
@Spearfoot, thank you so much for the instructions at post #48 mate, it worked like a charm, and as @bustersnm mentioned, there is no need to use rufus, just drop the content of the UEFI folder into a USB drive, plug it in, boot into supermicro UEFI and just run the script.
So far, the official 20.00.02.00 from supermicro is working fine on my X10SL7-F and the mismatch is gone.
 
Last edited:

Mynorx

Explorer
Joined
Aug 26, 2014
Messages
62

bgraf2311

Cadet
Joined
Dec 30, 2014
Messages
2
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 :cool:
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

Thanks for the write up. The process that you used worked for me. I'm running an LSI SAS: SAS2008(B2) on a Supermicro X9SCM-F . I was on version 16 and was already flashed to IT mode then realized after my recent upgrade to the latest build of FreeNAS that I needed the firmware upgrade for the controller. I just ejected all of the drives from the front of my Norco case before flashing instead of opening the case and pulling the cables to the controller. The IPMI viewer from Supermicro worked fine with a Rufus FreeDOS formatted USB stick and the files from the p20 zip mentioned earlier. :)
 

theutt

Cadet
Joined
Aug 14, 2015
Messages
2
OK, so i have been over this thread several times looking for an answer and am yet to find one. I have an IBM M1015 Flashed to IT mode V 20.00.04.00.
My FreeNas system returns an alarm saying Driver is 20.00.00.00 - Firmware is 20.00.04.00
I then get many errors returning "mps0: warning: io_cmds_active is out of sync - resyncing to 0
After several of these errors the M1015 appears to re initiate and retrieves the drive ID's
Low and behold 2 minutes later it all happens over and over again.

My Data is safe and my FreeNAS is functioning, however this does delay data access from the drives. I believe it is if the drives have spun down and upon waking them up the card has some fort of malfunction.

I did not install the bios rom image when flashing, only the LSI Firmware.

Somebody PLEASE help.

Having the same issue with a M1015 here. Originally had the card on v16 IT firmware for my initial FreeNAS install some months ago, then a couple days back flashed to IT mode v 20.00.04.00 to support the latest stable release that seemed to require it after installation.

The issue showed up in my freenas.local security run output this evening. Details attached.

No idea where to even start troubleshooting...any assistance welcomed.
 

Attachments

  • freenas_error.txt
    39 KB · Views: 325

rogerh

Guru
Joined
Apr 18, 2014
Messages
1,111
Having the same issue with a M1015 here. Originally had the card on v16 IT firmware for my initial FreeNAS install some months ago, then a couple days back flashed to IT mode v 20.00.04.00 to support the latest stable release that seemed to require it after installation.

The issue showed up in my freenas.local security run output this evening. Details attached.

No idea where to even start troubleshooting...any assistance welcomed.

I suggest you need to report it as a bug. You can do this through the 'Support' icon in the GUI, but you have to register at https://bugs.freenas.org first.

Please let us know the issue number in this thread.
 

raidflex

Guru
Joined
Mar 14, 2012
Messages
531
Weird I do not get any notification about a driver mismatch. I have a M1015 IT mode and a X10SL7-F Motherboard. I originally updated the firmware through Freenas for both the M1015 and on-board SAS, not sure if that makes a difference. I am currently on the latest stable build, but previous builds did not give me any issues either.
 

attilahooper

Dabbler
Joined
Jul 4, 2014
Messages
10
I get a weird error when trying to execute smc2308t.nsh in the uefi shell; "shell cannot read from file 800000001f"
Any ideas ?

edit: Fixed, I used RPMprepUSB to create a FAT32 (originally it was ntfs), DO NOT format as harddrive - option unchecked.
Note: I didn't pull drives or cables and all my volumes are hunky-dory, so far as I can tell.
 
Last edited:

Z300M

Guru
Joined
Sep 9, 2011
Messages
882
I suggest you need to report it as a bug. You can do this through the 'Support' icon in the GUI, but you have to register at https://bugs.freenas.org first.

Please let us know the issue number in this thread.
I got this same error at the first reboot ("warm boot") after the update, but after I powered down via IPMI then powered up again all seems to be well.
 

Haysden Smart

Dabbler
Joined
Sep 2, 2015
Messages
20
I have no idea if it is related, however I have installed more RAM (now 64GB 8xKVR1333D3D4R9/8GI) and used the new Internal Software Update. I have not seen the issue for 12 Hours so maybe it has been corrected in an update. I will keep you all posted.
 
Joined
Aug 27, 2014
Messages
13
Does anyone have experience with a Dell H200 running on LSI IT Mode P20? Any problems to be expected with that card and P20?
I had a crossflashed H200 running P16. Flashed it to 20.00.04.00, some of the drives did not show up. Attempted to install the P16 back on - cannot get it to accept it after a sas2flsh -o -e 6.
Due to time constraints, and thinking that the issue may be in the H200, I sourced a LSI9211-8i, flashed it with P16 - all drives present. Flashed it to P20 - again drives dropped off. Controller did not see them.
Luckily had some spares, and only lost 3 in the Raid-z3. I am now waiting if there is any additional news from the dev team. Keeping fingers crossed for now. Volume is showing healthy, although I have some strange critical alerts apparently from SMART, stating currently unreadable (pending) sectors. Waiting for new drive to see if that goes away as well :( I will still try to resurrect the H200, but so far no luck.
 

Radu

Dabbler
Joined
Mar 7, 2014
Messages
45
Upgraded from P16 of M1015 to P20 from LSI/AVAGO website 9211-8i (Version no: 20.00.04.00 Release date: 21-MAY-15)
Upgraded from P16 of on board SM 2308 to P20 from LSI/AVAGO website 9207-8i (Version no: 20.00.04.00 Release date: 21-MAY-15 instead of not recommended version of SM's 20.00.02.00 Release date: Jan, 2015 Revision 1.2)

Al upgraded in UEFI of the MB, all went fine. Pools imported OK, scrub in progress...

Elders, what do you think?
 

Mr_N

Patron
Joined
Aug 31, 2013
Messages
289
Where has it been 'not recommended' to use the manufacturers firmware release?
 

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
Would be nice to have an "official" word on this. I'm running the SM 20.00.02.00 firmware presently without issue but if there is some sort of problem it would be nice to know what the fix is. I understand that the controller on the X10SL7-F is the same as the Avago but who knows what sort of BIOS changes (if any?) are needed to implement different controller firmware versions.
 

Radu

Dabbler
Joined
Mar 7, 2014
Messages
45
So what's worse then, SM 20.00.02.00 on X10 or AVAGO 9207 fw 20.00.04.00 on X10 2308 ?
 

Mr_N

Patron
Joined
Aug 31, 2013
Messages
289
has anyone tried contacting SM and asking these questions?
 
Status
Not open for further replies.
Top