Firmware version P21?

[Nucshuco]

Just updated to the latest FreeNAS-9.10.1 (d989edd) and I get this message

Does anybody know where I can find P21 firmware?
I checked
http://www.avagotech.com/support/download-search#tab-current-Firmware
The highest they have is P20

 

[dlavigne]

I'll check with the devs to see if the alert is wrong or if the docs (which still say v20 is the latest) are wrong.

 

[TXAG26]

I just checked the update release notes and there is nothing mentioned about the LSI/Avago drivers being updated. However, I did notice this:
#15087 Bug Nice to have FreeNAS VMXNet 3 Driver

 

[billgreenwood]

I have the same issue. I could not find an updated driver anywhere.
Supermicro still have v20 on their site.

 

[striker79]

I am having the same issue. Cannot find the P21 firmware anywhere...

 

[mrichardson03]

Same issue here. I've reverted to FreeNAS-9.10-STABLE-201606270534 until they figure this out.

 

[Zpid]

Same issue here, using a LSI SAS 9220-8i flashed with LSI SAS 9211-8i IT firmware 20.00.06.00

dmesg shows that it is driver P21:

Code:

mps0: <Avago Technologies (LSI) SAS2008> port 0xe000-0xe0ff mem 0xdf3c0000-0xdf3c3fff,0xdf380000-0xdf3bffff irq 17 at device 0.0 on pci2
mps0: Firmware: 20.00.06.00, Driver: 21.00.00.00-fbsd

And could not find a newer than 20.00.07.00 version on http://www.avagotech.com/products/server-storage/host-bus-adapters/sas-9211-8i#downloads

 

[ElGusto]

Same problem here...
This makes me feel afraid about my data!

Code:

[root@freenas] ~# dmesg | grep mps
KLD file mpslsi.ko is missing dependencies
mps0: <Avago Technologies (LSI) SAS2008> port 0x5000-0x50ff mem 0xfd4fc000-0xfd4fffff,0xfd480000-0xfd4bffff irq 19 at device 0.0 on pci11
mps0: Firmware: 20.00.07.00, Driver: 20.00.00.00-fbsd
mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
mps0: SAS Address for SATA device = 371a444564969459
mps0: SAS Address from SATA device = 371a444564969459
mps0: SAS Address for SATA device = 371a4445656d863a
mps0: SAS Address from SATA device = 371a4445656d863a
mps0: SAS Address for SATA device = 371a4445656c8835
mps0: SAS Address from SATA device = 371a4445656c8835
mps0: SAS Address for SATA device = 371a4445658a8f39
mps0: SAS Address from SATA device = 371a4445658a8f39
da2 at mps0 bus 0 scbus3 target 0 lun 0
da3 at mps0 bus 0 scbus3 target 1 lun 0
da4 at mps0 bus 0 scbus3 target 2 lun 0
da5 at mps0 bus 0 scbus3 target 3 lun 0
KLD file mpslsi.ko is missing dependencies
mps0: <Avago Technologies (LSI) SAS2008> port 0x5000-0x50ff mem 0xfd4fc000-0xfd4fffff,0xfd480000-0xfd4bffff irq 19 at device 0.0 on pci11
mps0: Firmware: 20.00.07.00, Driver: 21.00.00.00-fbsd
mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
mps0: SAS Address for SATA device = 371a444564969459
mps0: SAS Address for SATA device = 371a4445656d863a
mps0: SAS Address for SATA device = 371a4445656c8835
mps0: SAS Address for SATA device = 371a4445658a8f39
mps0: SAS Address from SATA device = 371a444564969459
mps0: SAS Address from SATA device = 371a4445656d863a
mps0: SAS Address from SATA device = 371a4445656c8835
mps0: SAS Address from SATA device = 371a4445658a8f39
da2 at mps0 bus 0 scbus3 target 0 lun 0
da3 at mps0 bus 0 scbus3 target 1 lun 0
da4 at mps0 bus 0 scbus3 target 2 lun 0
da5 at mps0 bus 0 scbus3 target 3 lun 0
KLD file mpslsi.ko is missing dependencies
mps0: <Avago Technologies (LSI) SAS2008> port 0x5000-0x50ff mem 0xfd4fc000-0xfd4fffff,0xfd480000-0xfd4bffff irq 19 at device 0.0 on pci11
mps0: Firmware: 20.00.07.00, Driver: 21.00.00.00-fbsd
mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
mps0: SAS Address for SATA device = 371a444564969459
mps0: SAS Address for SATA device = 371a4445656d863a
mps0: SAS Address for SATA device = 371a4445656c8835
mps0: SAS Address for SATA device = 371a4445658a8f39
mps0: SAS Address from SATA device = 371a444564969459
mps0: SAS Address from SATA device = 371a4445656d863a
mps0: SAS Address from SATA device = 371a4445656c8835
mps0: SAS Address from SATA device = 371a4445658a8f39
da2 at mps0 bus 0 scbus3 target 0 lun 0
da4 at mps0 bus 0 scbus3 target 2 lun 0
da3 at mps0 bus 0 scbus3 target 1 lun 0
da5 at mps0 bus 0 scbus3 target 3 lun 0
KLD file mpslsi.ko is missing dependencies
mps0: <Avago Technologies (LSI) SAS2008> port 0x5000-0x50ff mem 0xfd4fc000-0xfd4fffff,0xfd480000-0xfd4bffff irq 19 at device 0.0 on pci11
mps0: Firmware: 20.00.07.00, Driver: 21.00.00.00-fbsd
mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
mps0: SAS Address for SATA device = 371a444564969459
mps0: SAS Address for SATA device = 371a4445656d863a
mps0: SAS Address for SATA device = 371a4445656c8835
mps0: SAS Address for SATA device = 371a4445658a8f39
mps0: SAS Address from SATA device = 371a444564969459
mps0: SAS Address from SATA device = 371a4445656d863a
mps0: SAS Address from SATA device = 371a4445656c8835
mps0: SAS Address from SATA device = 371a4445658a8f39
da2 at mps0 bus 0 scbus3 target 0 lun 0
da3 at mps0 bus 0 scbus3 target 1 lun 0
da4 at mps0 bus 0 scbus3 target 2 lun 0
da5 at mps0 bus 0 scbus3 target 3 lun 0
[root@freenas] ~#

 

[m3ki]

Same issue here

Sent from my Nexus 6P using Tapatalk

 

[cyberjock]

Gents,

I just had a discussing with Josh Paetzel on this. The basic gist is that the person who is the official driver maintainer commited a p21 driver for the LSI controllers. This made its way into FreeNAS. Of course, if you look there is no P21 firmware (I just looked). The driver writer for Broadcom/Avago/LSI (Yes, Broadcom now owns Avago) has said that the P21 driver *is* compatible with P20 firmware (especially since P20 is the latest firmware out). FreeNAS is going to be changed to allow this one exception (p21 firmware with p20 driver).

I don't know how this wasn't noticed before now, just go with me on this for now. I'll provide more details if/when I have them and can share.

 

[Mlovelace]

Gents,

I just had a discussing with Josh Paetzel on this. The basic gist is that the person who is the official driver maintainer commited a p21 driver for the LSI controllers. This made its way into FreeNAS. Of course, if you look there is no P21 firmware (I just looked). The driver writer for Broadcom/Avago/LSI (Yes, Broadcom now owns Avago) has said that the P21 driver *is* compatible with P20 firmware (especially since P20 is the latest firmware out). FreeNAS is going to be changed to allow this one exception (p21 firmware with p20 driver).

I don't know how this wasn't noticed before now, just go with me on this for now. I'll provide more details if/when I have them and can share.

Thanks CJ!

Edit: Just as an aside Avago bought Broadcom ;) http://fortune.com/2015/05/28/avago-buys-broadcom-for-37b/

 

[m3ki]

Gents,

I just had a discussing with Josh Paetzel on this. The basic gist is that the person who is the official driver maintainer commited a p21 driver for the LSI controllers. This made its way into FreeNAS. Of course, if you look there is no P21 firmware (I just looked). The driver writer for Broadcom/Avago/LSI (Yes, Broadcom now owns Avago) has said that the P21 driver *is* compatible with P20 firmware (especially since P20 is the latest firmware out). FreeNAS is going to be changed to allow this one exception (p21 firmware with p20 driver).

I don't know how this wasn't noticed before now, just go with me on this for now. I'll provide more details if/when I have them and can share.

Is it safe to use the latest freenas build then?
Will there be another update?

 

[QuillOmega0]

Is it safe to use the latest freenas build then?
Will there be another update?

The driver writer for Broadcom/Avago/LSI (Yes, Broadcom now owns Avago) has said that the P21 driver *is* compatible with P20 firmware (especially since P20 is the latest firmware out). FreeNAS is going to be changed to allow this one exception (p21 firmware with p20 driver).

Sounds like it.

 

[adrianwi]

This might be a stupid question, but I'll ask it anyway as this always seems to pop up as an issue :D

FreeNAS works with many different motherboards, processors, disk drives, etc. so why can't it accommodate a number of different SATA/SAS cards?

What's so special here?

 

[QuillOmega0]

FreeNAS is FreeBSD, and to answer your question it DOES accommodate a number of different SATA/SAS cards.

What's so special here is it matches the driver version with the firmware version of the card (in the past both of those have been the same), now a driver has been updated to 21 with the firmware remaining at 20, because this is the first time this has happened, the monitoring software that monitors the version of both detects an inconsistency and pops up the mismatched firmware/driver flag.

 

[adrianwi]

It's not the first time though, as we've been from P14 to 16 to 20 and now 21.

What's so important to match the driver and firmware on these cards? Can't it deal with a mismatch?

Just trying to understand and gain some knowledge (as I have one on my motherboard, although all I know is I can plug some drives into the ports!)

 

[Jailer]

FreeNAS works with many different motherboards, processors, disk drives, etc. so why can't it accommodate a number of different SATA/SAS cards?

What's so special here?

In a nutshell, because ZFS. While there are several other cards that work fine with FreeBSD not all of them play nice with ZFS filesystem. ZFS needs direct disk access and not all FreeBSD compatible SATA/SAS cards provide it.

 

[soulburn]

Gents,

I just had a discussing with Josh Paetzel on this. The basic gist is that the person who is the official driver maintainer commited a p21 driver for the LSI controllers. This made its way into FreeNAS. Of course, if you look there is no P21 firmware (I just looked). The driver writer for Broadcom/Avago/LSI (Yes, Broadcom now owns Avago) has said that the P21 driver *is* compatible with P20 firmware (especially since P20 is the latest firmware out). FreeNAS is going to be changed to allow this one exception (p21 firmware with p20 driver).

I don't know how this wasn't noticed before now, just go with me on this for now. I'll provide more details if/when I have them and can share.

Thanks for the update. Forgive me if I'm reading that wrong, but don't you mean to say that FreeNAS is going to be changed to not throw a warning for P20 firmware with the new P21 driver?

 

[Z300M]

Gents,

I just had a discussing with Josh Paetzel on this. The basic gist is that the person who is the official driver maintainer commited a p21 driver for the LSI controllers. This made its way into FreeNAS. Of course, if you look there is no P21 firmware (I just looked). The driver writer for Broadcom/Avago/LSI (Yes, Broadcom now owns Avago) has said that the P21 driver *is* compatible with P20 firmware (especially since P20 is the latest firmware out). FreeNAS is going to be changed to allow this one exception (p21 firmware with p20 driver).

I don't know how this wasn't noticed before now, just go with me on this for now. I'll provide more details if/when I have them and can share.

Why on earth did they create a P21 driver when there is no P21 firmware?

Can we just backlevel the driver to the P20 version instead of either (a) having mismatched driver versions (but without the warning message) or (b) reverting to the previous version of FreeNAS?

 

[a-freenas-user]

Gents,
I don't know how this wasn't noticed before now, just go with me on this for now. I'll provide more details if/when I have them and can share.

Like here?

https://forums.freenas.org/index.php?threads/9-10-nightlies-p21-lsi-firmware-warning.44775/