Patrick

How to fix: BMC can't force ME to recovery mode when updating BIOS

Patrick

Administrator
Staff member
Dec 21, 2010
12,341
5,469
113
Patrick submitted a new resource:

How to fix: BMC can't force ME to recovery mode when updating BIOS - Tested on a Supermicro motherboard

I recently ran into an issue where I purchased a Supermicro license key for remote BIOS upgrade only to find that the system rebooted to "System initializing" and post code 19. Normally the remote BIOS update key allows you to update BIOS remotely without issue, even when you have some strange POST code failure. Instead, the remote flash would fail and I saw this message:


View attachment 5265
Here was the fix:
  • Power off system completely
  • Unplug system so BMC turns off...
Read more about this resource...
 
  • Like
Reactions: i386 and PigLover

i386

Well-Known Member
Mar 18, 2016
2,992
958
113
33
Germany
If this doesn't work for you, try to update bios with SUM* and the "--force_update" parameter:

Code:
./SUM -i 192.168.0.107 -u ADMIN -p ADMIN -c UpdateBios --file <PATH TO BIOS FILE> --force_update --reboot
*executable is shipped with the superdoctor package, download from supermicro ftp is possible
 

Panagiotis

New Member
Nov 5, 2019
15
3
3
If this doesn't work for you, try to update bios with SUM* and the "--force_update" parameter:

Code:
./SUM -i 192.168.0.107 -u ADMIN -p ADMIN -c UpdateBios --file <PATH TO BIOS FILE> --force_update --reboot
*executable is shipped with the superdoctor package, download from supermicro ftp is possible
You rock. I just recovered the BIOS on my X10dri with this method, also suggested by Supermicro in their FAQs. I tried Patrick's method first, but hadn't considered setting Restore on AC loss to Stay Off before flashing, so that didn't work. Thank you for the reference, bookmarked :)
 

sko

Member
Jun 11, 2021
52
27
18
Thanks for this info!

I just had a X10DRU-i+ here that didn't POST after flashing the latest BIOS (2 similar systems were upgraded last week without any issues..)

Some additional findings: In case SUM will give you this error

Code:
********************************<<<<<ERROR>>>>>*********************************

ExitCode                = 148
Description             = IPMI execution exception occurred
Program Error Code      = 216.55
Error message:
    Other user is updating. Please try again later.

********************************************************************************
Try another (newer) Version of SUM - I had SUM v2.3 lying on my disk which didn't work; the current version 2.8 was able to flash the BIOS.
Also try changing the "ME manufacturing mode select" jumper position. Strangely with the manufacture mode enabled I couldn't flash via SUM (or the web-IMPI), setting the jumper back to 1-2 worked with SUM.
 

oneplane

Active Member
Jul 23, 2021
211
95
28
If I'm not mistaken this is because the ME update and some other classes of signed updates can only be pre-loaded after which a system reset has to happen before the firmware will read the pre-loaded update capsule and then start the update process itself. On top of that, to pre-load an ME update, the ME has to be switched to update mode, reset, then preloaded, then reset again. This mostly happens when a firmware update contains a large jump in ME versions or updater versions because it will do a prep+update first and then once the system resets the ME hasn't gone into update mode yet and can't start the update, but the new firmware expects the new ME firmware so it can't boot either.
 

sko

Member
Jun 11, 2021
52
27
18
The ME wasn't updated on those systems (they were/are on 3.91; 3.94 is the latest). I actually tried to fix the problem on that particular host by also updating the ME/IPMI, which didn't help with the error.