Ethernet Products
Determine ramifications of Intel® Ethernet products and technologies
5348 Discussions

X710-T2L stuck in recovery, Cannot restore manufacturing data

zorg
Novice
1,938 Views

Hi,

 

after the update from 09.32/09.20h to 09.40 failed for unknown reason the X710-T2L is in recovery state.

 

Following attempts to flash fail with:

Num Description Ver.(hex) DevId S:B Status
=== ================================== ============ ===== ====== ==============
01) Intel(R) Ethernet Network Adapter N/A(N/A) 15FF 00:007 RECOVERY
X710-T2L failed


Tool execution completed with the following status: Cannot restore manufacturing data.

 

How to proceed?

 

# ethtool -i enp7s0f0
driver: i40e
version: 6.6.13-amd64
firmware-version: 9.40 0x8000ecc3 1.3353.0
expansion-rom-version:
bus-info: 0000:07:00.0
supports-statistics: no
supports-test: no
supports-eeprom-access: yes
supports-register-dump: no
supports-priv-flags: yes

 

 

previous version: firmware-version: 9.20 0x8000d8ae 1.3353.0

Num Description Ver.(hex) DevId S:B Status
=== ================================== ============ ===== ====== ==============
01) Intel(R) Ethernet Network Adapter 9.32(9.20) 15FF 00:007 Update
X710-T2L available

Thank you

 

Martin

Labels (1)
0 Kudos
5 Replies
Irwan_Intel
Moderator
1,886 Views

Hello zorg,


Thank you for the posting in Intel Ethernet Communities.


You can refer to the Feature Support matrix for NVM and software compatibility

https://www.intel.com/content/www/us/en/support/articles/000093197/ethernet-products.html


You may also refer to the recovery guideline below:

https://www.intel.com/content/www/us/en/support/articles/000089896/ethernet-products.html


Quick usage guideline on how to use the update tool.

https://www.intel.com/content/www/us/en/support/articles/000088453/ethernet-products.html


Regards,

Irwan_Intel


0 Kudos
zorg
Novice
1,865 Views

Dear Irwan,

 

thank you for responding.

 

However I cannot find a procedure on how to continue after the recovery fails with error "24 - Cannot restore manufacturing data." in your provided documentation.

 

I tried 9.40 and 9.20 - previous and current version. Both terminate with the same error.

0 Kudos
zorg
Novice
1,845 Views

OK, solved.

 

After power cycle the card is out of recovery mode and back at 9.20, but still fails to update with the linux version of nvmupdate.

 

On a hunch I tried the EFI version from efishell. It first complains about corrupt nvmupdate.cfg. After converting that with dos2unix it successfully updates the card to 9.40.

 

Please fix the 700Series_NVMUpdatePackage_v9_40_EFI.zip package and include the nvmupdate.cfg in unix fileformat.

 

Best regards,

 

Martin

Irwan_Intel
Moderator
1,791 Views

Hello zorg,


Thanks for the information. I will forward it to our Engineering team for a closer look.

Kindl reach out to us if you still have further questions or concerns.


Regards,

Irwan_Intel


0 Kudos
GeneralProbe
Beginner
997 Views

I also got my b3:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ [8086:1583] (rev 02) stuck in Recovery mode as well after a failed update from 9.0 to 9.50.

I used the linux version of nvmupdate64e, which promted me "Error 6 - An error occurred when updating a firmware module."
After that, the tool did not recognize the card anymore.

I then powercycled the system which, as expected, sent the card into recovery mode.

I then tried to flash it again with nvmupdate64e, which detected the card after some time, but failed again with "Error 24 - Cannot restore manufacturing data."

Googling this error ultimately led me to this thread.

As a last Hail Mary, I tried @zorgs idea to run the upgrade in efi mode instead.
Even though producing the same errormessage "Error 24", the card showed in the nvmupdate64e tool instead of N/A a the proper firmware version. So I powercycled the system and my card was working again.

 

I wonder, if there are problems with the linux tool itself, since the efi tool was running much faster and was able to recover the card?
Also @Irwan_Intel  I still had to use dos2unix, since the config file was written in "windows ascii mode".

0 Kudos
Reply