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

[Ellimist]

Nah I'm running the 04 version of p20. The comments in the thread where drives were missing were from the 04 version as well. I think P20 most likely still has issues but is mostly stable in operation if you have drives attached that are detected. I will try my other drive types tonight to see.

 

[Ellimist]

Ok so I got a chance to test alot of hard drives. All the drives I had worked from WD Reds to Greens etc. The only one I had an issue with was one that was limited to SATA 1 speeds. Once I removed the jumper that drive got detected. For the others that had missing drives I'd love to know what sort of drives they were and if the issues were resolved.

 

[MoB]

Hello. Building a new server, I try to update my LSI to P20. I am running Freenas 9.10 on a USB key as a boot device.

Unfortunately I got this error when I try any sas2flash command in Freenas:

[root@freenas] ~# sas2flash -listall
/usr/local/sbin/sas2flash: Permission denied.

Usually this kind of error is related to privilege elevation, but I am root ...

Thank for your help.

 

[MoB]

Hello. Building a new server, I try to update my LSI to P20. I am running Freenas 9.10 on a USB key as a boot device.

Unfortunately I got this error when I try any sas2flash command in Freenas:

[root@freenas] ~# sas2flash -listall
/usr/local/sbin/sas2flash: Permission denied.

Usually this kind of error is related to privilege elevation, but I am root ...

Thank for your help.

Ok this is awkward. The sas2flash come with no execute rights on my install.. Very strange so I just chmod the thing...

 

[rogerh]

Ok this is awkward. The sas2flash come with no execute rights on my install.. Very strange so I just chmod the thing...

A known bug:
https://bugs.freenas.org/issues/14304
https://bugs.freenas.org/issues/14221

 

[jgreco]

Ok this is awkward. The sas2flash come with no execute rights on my install.. Very strange so I just chmod the thing...

That's pretty awesome. This would be a reasonable solution, too.

 

[R.G.]

I had to haul out an earlier FreeNAS machine and update it to 9.10. It has the M1015 card in it, and I got the message about the firmware mismatch

Went to Avago and downloaded the firmware, but the current download is listed as 20.00.07.00, not 04.

Any known issues? Should I try to find a copy of 04?

 

[Ericloewe]

I had to haul out an earlier FreeNAS machine and update it to 9.10. It has the M1015 card in it, and I got the message about the firmware mismatch

Went to Avago and downloaded the firmware, but the current download is listed as 20.00.07.00, not 04.

Any known issues? Should I try to find a copy of 04?

.04 is known to work well in most scenarios. .07 is a bit of an unknown, but is supposed to fix a few minor issues on the firmware side.

I'd probably be ok with using .07.

 

[R.G.]

I'm probably good with that. I resurrected an earlier server corpse to get another layer of backup, so at the moment there is nothing in it. I'm still installing/upgrading/setting up stuff, so it won't kill anything.

I may do 04 first, then go to 07. It may be my turn to be the point man; little enough to do for all the trails other have blazed for me.

 

[BWPhx]

I was glad to see this thread is still active. I'm getting a similar message (firmware version 2!) but so far, I didn't see anyone in the thread running the same card I have - LSI 9260-4i. The latest firmware I could find on Avago's site is 12.15.0-0239.

Here is sas2flash -list output:

~# sas2flash -list
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(B1)

Controller Number : 0
Controller : SAS2008(B1)
PCI Address : 00:05:00:00
SAS Address : 5003048-0-0076-0aa0
NVDATA Version (Default) : 00.09.00.02
NVDATA Version (Persistent) : 00.09.00.02
Firmware Product ID : 0x2713 (IR)
Firmware Version : 02.00.50.00
NVDATA Vendor : LSI
NVDATA Product ID : LSI SAS2008-IR
BIOS Version : 07.01.01.00
UEFI BSD Version : N/A
FCODE Version : N/A
Board Name : LSI SAS2008
Board Assembly : N/A
Board Tracer Number : N/A

Finished Processing Commands Successfully.
Exiting SAS2Flash.

It just dawned on me it may actually be referring to the onboard controller, not the card my disks are actually connected to.

I haven't used FreeBSD since the late 90's, so I'm not even sure how to tell what controllers (and associated drivers) are being loaded. It looks like from dmesg output my disks might be using the mfi driver, and FreeNAS is complaining about the mps driver.

If that's the case, is there a way to supress the message from FreeNAS since I don't use the onboard controller?

 

[Ericloewe]

from dmesg output my disks might be using the mfi driver,

Oh dear, you're screwed.

Are your disks identified by /dev/mfiX handles or /dev/daX handles?

 

[BWPhx]

# geom disk list
Geom name: mfid0
Providers:
1. Name: mfid0
Mediasize: 1999844147200 (1.8T)
Sectorsize: 512
Mode: r1w1e2
descr: 1
ident: 1
fwsectors: 63
fwheads: 255

Geom name: mfid1
Providers:
1. Name: mfid1
Mediasize: 1999844147200 (1.8T)
Sectorsize: 512
Mode: r2w2e5
descr: 1
ident: 1
fwsectors: 63
fwheads: 255
... and so on...

 

[Ericloewe]

You definitely want to migrate your pool off of those disks and onto disks attached to an HBA.

If you tell us what hardware and storage setup you're using, we can suggest the easiest way out of this predicament.

I'll note that the LSI SAS 9260 (-4i? That's silly, but you own it, so we'll work with it) can make a fine HBA, after it's crossflashed.

I'll note that you have a suitable controller already, as evidenced by the output of sas2flash.

Also, the output of the following commands would be useful:

• sas2ircu list

For all adapters listed there:

• sas2ircu $(controller_#) display

 

[jgreco]

No, the 9260 cannot be crossflashed to be an HBA. It's a full LSI RAID controller, not an entry-level HBA/RAID controller like the 9240.

 

[Mirfster]

No, the 9260 cannot be crossflashed to be an HBA. It's a full LSI RAID controller, not an entry-level HBA/RAID controller like the 9240.

Believe it or not, I have 3 of these. I didn't see a way to cross-flash them either. If someone is willing to correct me I am all ears.

 

[Ericloewe]

No, the 9260 cannot be crossflashed to be an HBA. It's a full LSI RAID controller, not an entry-level HBA/RAID controller like the 9240.

D'oh, absolutely right, it's an SAS2108. I was misled by the output of sas2flash.

Good news is that there is a suitable controller in your system, OP, as evidenced by the output of sas2flash.

 

[BWPhx]

So I'm running a Supermicro X8DTH-6F board that has the LSI 2008 controller on it that I believe is what FreeNAS is complaining about. I do not use it. The LSI 9260-4i is hooked to a 24 port SAS846EL1 backplane.

# sas2ircu list
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:05h:00h:00h 1000h 0072h
SAS2IRCU: Utility Completed Successfully.

So it looks like it doesn't even see the 9260-4i with that command. As you can see, no physical devices on that card:

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

Read configuration has been initiated for controller 0
------------------------------------------------------------------------
Controller information
------------------------------------------------------------------------
Controller type : SAS2008
BIOS version : 7.01.01.00
Firmware version : 2.00.50.00
Channel description : 1 Serial Attached SCSI
Initiator ID : 0
Maximum physical devices : 125
Concurrent commands supported : 3167
Slot : 0
Segment : 0
Bus : 5
Device : 0
Function : 0
RAID Support : Yes
------------------------------------------------------------------------
IR Volume information
------------------------------------------------------------------------
------------------------------------------------------------------------
Physical device information
------------------------------------------------------------------------
------------------------------------------------------------------------
Enclosure information
------------------------------------------------------------------------
Enclosure# : 1
Logical ID : 50030480:00760aa0
Numslots : 8
StartSlot : 0
------------------------------------------------------------------------
SAS2IRCU: Command DISPLAY Completed Successfully.
SAS2IRCU: Utility Completed Successfully.

Thanks!

 

[Ericloewe]

Here's a summary of what you should do:

• Flash the 2008 to P20 IT mode
• Migrate the pool to drives controlled by the SAS2008

The second point is tricky. The only thing that comes to mind as a viable solution is to migrate the data off the pool, destroy it and then move the disks over.
Either that, or you grab another SAS expander and a bunch of breakout cables, which you can use as a temporary solution to have more than eight drives connected to the SAS2008, until all drives have been migrated and you can go back to using the chassis backplane for all drives.

 

[R.G.]

Meanwhile... I'll go mess with the 04 to 07 thing as soon as the ^@$@$_(** replication finishes.

Now in its 4th day.

 

[Ericloewe]

Meanwhile... I'll go mess with the 04 to 07 thing as soon as the ^@$@$_(** replication finishes.

Now in its 4th day.

If you happen to have ancient SATA 1.5Gb/s drives laying around, could you tell us if they're recognized with the .07 firmware?