Firmware version 15 does not match driver version 21 for /dev/mps0. Please flash controller to P21

[mst]

Experts,

I have just bought LSI 9207-8i, installed with FreeNAS-9.10.2 and the warring pop-ed up. Current firmware revision is 15.00 IT

Thank You,

 

[bigphil]

You need to flash the card to IT firmware P20 for the warning to go away. Firmware download

 

[mst]

I see on Broadcom:

Installer_P20_for_FreeBSD
FreeBSD Installer
Version: 20.00.00.00
File Size: 684 KB
Language: English

I dont see P21

 

[mst]

You need to flash the card to IT firmware P20 for the warning to go away. Firmware download

Thank You, I will start looking for the link with how to flash it.

 

[bigphil]

P20 is what you need.

9207-8i_Package_P20_IR_IT_Firmware_BIOS_for_MSDOS_Windows
Package_P20_Firmware_BIOS_for_MSDOS_WindowsVersion: 20.00.07.00

Easiest way for you since you're already on IT firmware...Create a FreeDOS bootable disk using Rufus and put the files from the zip package in there. If using BIOS:
sas2flsh -list
write down your sas address
sas2flsh -o -e 7
sas2flsh -f 9207-8.bin
sas2flsh -b mptsas2.rom
sas2flsh -o -sasadd <your sas address without the hyphens>
reboot...done.

 

[Ericloewe]

installed with FreeNAS-9.10.2

Are you sure? It's supposed to tell you to use P20.

(Note that firmware P20 goes with driver P21 )

 

[mst]

Are you sure? It's supposed to tell you to use P20.

(Note that firmware P20 goes with driver P21 )

Yes, thats what is says:

WARNING: Jan. 4, 2017, 8:49 a.m. - Firmware version 15 does not match driver version 21 for /dev/mps0. Please flash controller to P21 IT firmware.

 

[Ericloewe]

Yes, thats what is says:

WARNING: Jan. 4, 2017, 8:49 a.m. - Firmware version 15 does not match driver version 21 for /dev/mps0. Please flash controller to P21 IT firmware.

Ok, thanks, I'll file a bug report.

https://bugs.freenas.org/issues/20007

 

[mst]

P20 is what you need.

9207-8i_Package_P20_IR_IT_Firmware_BIOS_for_MSDOS_Windows
Package_P20_Firmware_BIOS_for_MSDOS_WindowsVersion: 20.00.07.00

Easiest way for you since you're already on IT firmware...Create a FreeDOS bootable disk using Rufus and put the files from the zip package in there. If using BIOS:
sas2flsh -list
write down your sas address
sas2flsh -o -e 7
sas2flsh -f 9207-8.bin
sas2flsh -b mptsas2.rom
sas2flsh -o -sasadd <your sas address without the hyphens>
reboot...done.

Thank You for Your help, the only problem I had it was: sas2flsh -o -sasadd <your sas address without the hyphens>

This generates "SAS address not programmed on controller in slot (1)

Should I go through the steps again? Also when I typed sas2flsh -list it gave me SAS address: 0000000-0-0000-0000

 

[SweetAndLow]

The address should be printed on a sticker.

There is no need to create a separate boot disk you can upgrade your firmware from freenas directly. Same command as listed above.

Sent from my Nexus 5X using Tapatalk

 

[mst]

well I could use sas2flash -o -e 6 that would not erase the SAS address, I guess i have to remove the card and will be somewhere on the sticker ......

The address should be printed on a sticker.

There is no need to create a separate boot disk you can upgrade your firmware from freenas directly. Same command as listed above.

Sent from my Nexus 5X using Tapatalk

Cool, all works well now. Dont see any warnings. Next step is configuring the network iscsi

 

[actigner]

P20 is what you need.

9207-8i_Package_P20_IR_IT_Firmware_BIOS_for_MSDOS_Windows
Package_P20_Firmware_BIOS_for_MSDOS_WindowsVersion: 20.00.07.00

Easiest way for you since you're already on IT firmware...Create a FreeDOS bootable disk using Rufus and put the files from the zip package in there. If using BIOS:
sas2flsh -list
write down your sas address
sas2flsh -o -e 7
sas2flsh -f 9207-8.bin
sas2flsh -b mptsas2.rom
sas2flsh -o -sasadd <your sas address without the hyphens>
reboot...done.

Tried this and it bricked my HP H220 HBA card when I tried to flash it to firmware version 20. Here's what I got after I entered sas2flsh -f 9207-8.bin which started out well but then I got ERROR: NVDATA Image does not match Controller SubSystem ID! and ERROR: No compatible NVDATA Image(s) found! and then the utility closed out. I restarted the flash utility and tried just to list the controller and once again it issued many doom and gloom messages and said I needed to input a valid firmware file but would still not accept it without failing. At this point my controller is DOA and I was really bummed since I just purchased it. Here is what I saw.


That's the bad news. The good news is that I fixed it after i found someone's similar experience (with FreeNASversion 9.3 and LSI firmware 16) and how they resolved it. It seems that the newer version of the flashing utility (probably starting at version 16) performs this Subsystem ID check and older versions did not. His fix involved using the flash utility from version 14 to flash the board to firmware version 16 and like magic it worked. Just to be safe, and praying this would work for me, I just used the firmware version 14 package "as is" to try and get my board functioning again. Just like magic my board was successfully re-flashed to version 14 and all was good. Now that I knew I could "un-brick" the board if need be I decided to see if I could update the board to version 20 using the version 14 flash utility and like "manna from heaven" it worked perfectly. Here's a shot of my current status.


Of note, I believe that the command sas2flsh -o -e 7 possibly contributed to the "bricking" as it wiped out any old code that might have been reverted to after these errors were detected. I say this only because when I applied version 20 on top of 14 I did not do the erase beforehand and it did not seem to care.

I did find one additional tidbit (note it is for the sas3flash utility) and that is if you add the parameter "-nossid" to the end of the command string as shown below it may ignore that check and not fail. I have not tried it on version sas2flash but it may solve this issue. The root of the issue apparently has to do with a newer rev of the LSI board that supports PCI Express 3.0 and this is somehow related even though both the old and new hardware versions support the new firmware.

sas3flsh –o –e -6
sas3flsh –o –f <firmware> -b <bios> -nossid

I hope this helps someone. Here's the full post that I found that I used to fix my problem https://www.willglynn.com/2014/11/10/lsi-sas-firmware-nonsense/

 

[actigner]

Tried this and it bricked my HP H220 HBA card when I tried to flash it to firmware version 20. Here's what I got after I entered sas2flsh -f 9207-8.bin which started out well but then I got ERROR: NVDATA Image does not match Controller SubSystem ID! and ERROR: No compatible NVDATA Image(s) found! and then the utility closed out. I restarted the flash utility and tried just to list the controller and once again it issued many doom and gloom messages and said I needed to input a valid firmware file but would still not accept it without failing. At this point my controller is DOA and I was really bummed since I just purchased it. Here is what I saw.
View attachment 18240

That's the bad news. The good news is that I fixed it after i found someone's similar experience (with FreeNASversion 9.3 and LSI firmware 16) and how they resolved it. It seems that the newer version of the flashing utility (probably starting at version 16) performs this Subsystem ID check and older versions did not. His fix involved using the flash utility from version 14 to flash the board to firmware version 16 and like magic it worked. Just to be safe, and praying this would work for me, I just used the firmware version 14 package "as is" to try and get my board functioning again. Just like magic my board was successfully re-flashed to version 14 and all was good. Now that I knew I could "un-brick" the board if need be I decided to see if I could update the board to version 20 using the version 14 flash utility and like "manna from heaven" it worked perfectly. Here's a shot of my current status.
View attachment 18241

Of note, I believe that the command sas2flsh -o -e 7 possibly contributed to the "bricking" as it wiped out any old code that might have been reverted to after these errors were detected. I say this only because when I applied version 20 on top of 14 I did not do the erase beforehand and it did not seem to care.

I did find one additional tidbit (note it is for the sas3flash utility) and that is if you add the parameter "-nossid" to the end of the command string as shown below it may ignore that check and not fail. I have not tried it on version sas2flash but it may solve this issue. The root of the issue apparently has to do with a newer rev of the LSI board that supports PCI Express 3.0 and this is somehow related even though both the old and new hardware versions support the new firmware.

sas3flsh –o –e -6
sas3flsh –o –f <firmware> -b <bios> -nossid

I hope this helps someone. Here's the full post that I found that I used to fix my problem https://www.willglynn.com/2014/11/10/lsi-sas-firmware-nonsense/

I was able to test the "-nossid" parameter and it DID NOT work as I had hoped it would so I had to use the older SAS2Flash utility (from release 14) to install version 20 of the firmware. Here's the link I was using as my reference. https://www.broadcom.com/support/kn...44/flashing-firmware-and-bios-on-lsi-sas-hbas