Firmware version 109 does not match driver version 21 for /dev/mps1
Freenas 9.10 Stable (FreeNAS-9.10.2-U1 (86c7ef5))
Supermicro Motherboard: X9DRH-iF
Supermicro Backplane Expander: BPN-SAS2-826EL1
Supermicro Backplane Expander: BPN-SAS2-846EL1
[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 20.00.07.00 14.01.00.08 07.39.02.00 00:04:00:00
Finished Processing Commands Successfully.
Please let me know what other output would be helpful.
#3 Updated by Sean Fagan over 3 years ago
- Category changed from 1 to 129
- Assignee changed from Sean Fagan to Bonnie Follweiler
Not an installation issue, and it is behaving correctly. The OS does not automatically update the firmware (at least not for FreeNAS).
Normally this would have been something to assigned to Josh, but since he's gone, I don't know who handles it.
#7 Updated by Burba Denson over 3 years ago
[root@freenas ~]# sysctl dev.mps.0.driver_version dev.mps.0.firmware_version
[root@freenas ~]# sysctl dev.mps.1.driver_version dev.mps.1.firmware_version
#8 Updated by Alexander Motin over 3 years ago
- Status changed from 15 to Investigation
So it is not a FreeNAS problem. It is somewhere between the firmware and the driver. I don't remember such cases, but I'll take a look on how it works.
I'm curious, why in your original sas2flash output there is only one HBA, while now you show sysctls for two? What sas2flash thinks about both of them? Is the firmware different there somehow?
#9 Updated by Eric Loewenthal over 3 years ago
Now that I think about this, it may be something like that Intel SSD that was actually an SAS2008 with four SAS SSD controllers attached and a somewhat-custom firmware. Another user once managed to accidentally flash his with the regular P20 IT firmware and ruined the thing.
Of course, this is speculation on my part.
#10 Updated by Alexander Motin over 3 years ago
- Status changed from Investigation to Closed: Third party to resolve
Hmm. If there are such alternative things exist, then it seems like there is nothing to do for us here. This warning should just be ignored. Actually those version checks may gone at some point, since Broadcom/LSI is recently released newer generation of cards, that will use existing mpr(4) driver with existing numeration, but with independent firmware versions starting from 1.