gigabyte server motherboard bios recovery jumper

[spyroot]

Hi Folks,

Did anyone do BIOS recovery from Flash? I have an MS33-AR0 board. It was initially posted but after the BMC update.
The BIOS is completely gone. Neither BMC nor IPMI or Redfish works. (It always uploads, and seq shows it done,
but BIOS never loaded)

Either Gigabyte posted BMC that is incompatible with this board's latest BIOS or something.
I tried to switch from the default state BIOS RECOVERY ( to default, I'm not sure
is a bug or a typo).

But none of mentioned step access a flash with ROM file.

 

[spyroot]

Yeah, I tried to recover four different methods, but none of them worked. (It was not clear from the initial my msg). I upload RBU ( that gigabyte call bios), set PIN 2/3, shut down the system, and power on, but I don't see any reads happening from Flash. ( I use a flash driver with a small led, so I see that during power on no read).

In the Java tool, you actually need to pass a zip.

java -jar GbtUtility-2.1.61.jar -H 192.168.254.18 -U admin -P my_serial update bios auto server_mb_bios_MS33-AR0_F17.zip
...

in the end, see Success (in practically BIOS dead) in BMC, no link, no VGA output from build in VGA port.

[192.168.254.18] Close session success.
update process complete ... (1/1)
********************************************************************
* GIGABYTE(TM) CLI "update" Command Executions Summary *
********************************************************************
Target IP: | Command Name: | Status: | Total elapsed times:
192.168.254.18 | update | Success | 1 mins, 39.673 sec.
Total success nodes : 1 fail nodes : 0
********************************************************************


Notice.

```
PICMG HPM.1 Upgrade Agent 1.0.9:

-------Target Information-------
Device Id : 0x20
Device Revision : 0x81
Product Id : 0x0179
Manufacturer Id : 0x3c0a (GIGA-BYTE TECHNOLOGY CO., LTD)


--------------------------------------------------------------------------
|ID | Name | Versions |
| | | Active | Backup | Deferred |
--------------------------------------------------------------------------
|* 0|BOOT | 13.05 00000000 | ---.-- -------- | ---.-- -------- |
|* 1|APP | 0.00 00000000 | ---.-- -------- | ---.-- -------- |
|* 2|BIOS | 0.00 00000000 | ---.-- -------- | ---.-- -------- |
|* 3|BOOTM | 13.05 00000000 | ---.-- -------- | ---.-- -------- |
|* 4|APPM | 13.05 02000000 | ---.-- -------- | ---.-- -------- |
|* 5|CPLD | 0.00 00000000 | ---.-- -------- | ---.-- -------- |
|* 6|BIOSM | 0.00 00000000 | ---.-- -------- | ---.-- -------- |
|* 7|BOOTFW | 0.00 00000000 | ---.-- -------- | ---.-- -------- |
--------------------------------------------------------------------------
```

I did update via IPMI and BMC, This stupid Java tool has the same story.

From the Java tool they provide.

[192.168.254.18] Flashing..., progress : 95% done
[192.168.254.18] Flashing..., progress : 97% done
[192.168.254.18] Flashing..., progress : 97% done
[192.168.254.18] Flashing..., progress : Complete
[192.168.254.18] Close session success.
update process complete ... (1/1)
********************************************************************
* GIGABYTE(TM) CLI "update" Command Executions Summary *
********************************************************************
Target IP: | Command Name: | Status: | Total elapsed times:
192.168.254.18 | update | Success | 3 mins, 0.651 sec.
Total success nodes : 1 fail nodes : 0
********************************************************************

But it never switches a BIOS, so it never does full POST.

 

[spyroot]

There is no BIOS, or it is in some strange state. ( check output in IPMI, BMC also shows nothing).
(here, after BMC firmware, you should see the BIOS version, which is gone after the BMC upgrade.

That way, I asked about the jumper recovery procedure, but it does read a ROM file from flash.

 

[spyroot]

: ) Well, that way, I asked.

The manual indicated steps below. . (but another pdf that I just found from the internet, said that I need to put a particular file from the AMI v5 tool, i.e., a 64-bit version AfuEfix64.efi to the SPI_UPD folder.

Because the manual's authors completely ignored this step and probably a bunch of others, it became a combinatorial nightmare.
That way, I asked if anyone had actually done it and knows all the "undocumented steps." The jumper, either on pin 3/2 or 1/2, doesn't do anything. (flash formated fat32, MBR).

BIOS Recovery

The system has an embedded recovery technique. In the event that the BIOS becomes corrupt, the boot block can be used to restore the BIOS to a working state. To restore your BIOS, please follow the instructions listed below:


Recovery Instruction:


1. Copy the XXX.rom to USB diskette.
2. Setting BIOS Recovery jump to enabled status.
3. Boot into BIOS recovery.
4. Run Proceed with flash update.
5. BIOS updated.

-----
For example, in all pdf for this and other server boards, gigabyte indicates that first you do bios update auto and then bios update backupimage.
For UI case (it should present BIOS 1 and BIOS 2), in my case, it never does it take image.rub file and upload it to BMC and reboot.

In the case of tools.

(important at the end)

[192.168.254.18] Completion code : 0x80
[192.168.254.18] IPMI error messages : Command specified code.
[192.168.254.18] Not support update 2nd SPI.
[192.168.254.18] Update BIOS 2nd SPI end.


❯ java -jar GbtUtility-2.1.61.jar -H 192.168.254.18 -U admin -P MGAP5100046 update bios backupimg /Users/spyroot/Downloads/server_mb_bios_MS33-AR0_F10.zip
*******************************************
* GIGABYTE(TM) GbtUtility v2.1.61 *
*******************************************
Get BMC platform information :
{
"Generation" : "AST26xx",
"Chip ID" : "AST2600",
"Architecture" : "x86",
"Platform Vendor" : "Intel",
"Platform Name" : "EagleStream"
}
Device ID : 32
Device Revision : 1
Firmware Revision : 13.05.02
IPMI Version : 2.0
Manufacturer ID : 15370
Manufacturer Name : GIGABYTE(TM)
Product ID : 0179
Platform Name : EagleStream
Device Available : true
Provides Device SDRs : true
Additional Device Support :
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
IPMB Event Generator
No match
Chassis Device
Aux Firmware Rev Info :
0x02
0x00
0x00
0x00
[192.168.254.18] Start to execute preupdate BIOS.
[192.168.254.18] Board Product : MS33-AR0-000
[192.168.254.18] Product Name : MS33-AR0-000
[192.168.254.18] BMC Product ID : 0179
[192.168.254.18] BMC FW Revision : 13.05.02
[192.168.254.18] BMC platform : Grantley
[192.168.254.18] Checksum of "/Users/spyroot/Downloads/server_mb_bios_MS33-AR0_F10/RBU/image.rbu" is 24179
[192.168.254.18] Matched release note : /Users/spyroot/Downloads/server_mb_bios_MS33-AR0_F10/RelNotes_MS33-AR0_F10.pdf
{
"TargetBmcIp" : "192.168.254.18",
"UpdateType" : "BIOS",
"ImagePath" : "/Users/spyroot/Downloads/server_mb_bios_MS33-AR0_F10/RBU/image.rbu",
"BmcVendor" : "ami",
"WithoutAsk" : false,
"ReleaseNote" : "/Users/spyroot/Downloads/server_mb_bios_MS33-AR0_F10/RelNotes_MS33-AR0_F10.pdf",
"Version" : "F10",
"Release Date" : "2023-01-15 00:00:00",
"Long Checksum" : 24179,
"FW folder path" : "/Users/spyroot/Downloads/server_mb_bios_MS33-AR0_F10",
"Support Product" : [
"MS33-AR0-000"
],
"Support Board Product" : "MS33-AR0",
"Short Checksum" : 63088
}
preupdate process complete ... (1/1)

Find suitable FW total success nodes : 1 fail nodes : 0

*******************************************************
__ __ __ ____ ______ __ __
/_/ /_/ /_/ __/_/_/_ /_/_/_/ /_/ /_/
/_/ /_/ /_/ /_/ /_/ /_/___/_/ /_/_/ /_/
/_/ /_/ /_/ /_/_/_/_/ /_/_/_/ /_/ /_/ /_/
/_/_/ /_/ /_/ /_/ /_/ /_/ /_/ /_/_/
/_/ /_/ /_/ /_/ /_/ /_/ /_/ /_/

*******************************************************
You have selected update backup image mode !!
If update backup image process fail or break by accident, it may cause system crash.
Are you sure yo continue? (Y/N)
Y
** Do you want to continue update the success nodes of preupdate (Y/N) ? **
Y
[192.168.254.18] Start update BIOS.
[192.168.254.18] New Rev : F10
[192.168.254.18] Open session success.
[192.168.254.18] Wait for switching to flash mode.......
{
"flash_type" : "BIOS",
"preserve_config" : 0,
"flash_status" : 0,
"backup_flag" : 0
}
[192.168.254.18] Flash chip success.
[192.168.254.18] Keep update progress alive success.
[192.168.254.18] Start upload FW image (RT=300000, CT=20000).
[192.168.254.18] Wait for uploading FW image......
[192.168.254.18] Keep update progress alive success.
[192.168.254.18] Upload firmware success.
[192.168.254.18] Start verify FW image (RT=300000, CT=20000).
[192.168.254.18] Wait for verifying FW image......
[ ]
[192.168.254.18] Upload firmware verification success.
[192.168.254.18] Start to upgrade FW image.
{
"flash_type" : "BIOS",
"preserve_config" : 0,
"flash_status" : 1,
"backup_flag" : 0
}
[192.168.254.18] Firmware upgrade has started.
[192.168.254.18] Flashing..., progress : 0% done
[192.168.254.18] Flashing..., progress : 0% done
[192.168.254.18] Flashing..., progress : 0% done
[192.168.254.18] Flashing..., progress : 0% done
[192.168.254.18] Flashing..., progress : 4% done
[192.168.254.18] Flashing..., progress : 10% done
[192.168.254.18] Flashing..., progress : 17% done
[192.168.254.18] Flashing..., progress : 24% done
[192.168.254.18] Flashing..., progress : 31% done
[192.168.254.18] Flashing..., progress : 37% done
[192.168.254.18] Flashing..., progress : 44% done
[192.168.254.18] Flashing..., progress : 51% done
[192.168.254.18] Flashing..., progress : 58% done
[192.168.254.18] Flashing..., progress : 65% done
[192.168.254.18] Flashing..., progress : 72% done
[192.168.254.18] Flashing..., progress : 79% done
[192.168.254.18] Flashing..., progress : 86% done
[192.168.254.18] Flashing..., progress : 93% done
[192.168.254.18] Flashing..., progress : 99% done
[192.168.254.18] Flashing..., progress : Complete
[192.168.254.18] Close session success.
[192.168.254.18] Starting to execute BIOS firmware backup process...
[192.168.254.18] Completion code : 0x80
[192.168.254.18] IPMI error messages : Command specified code.
[192.168.254.18] Not support update 2nd SPI.
[192.168.254.18] Update BIOS 2nd SPI end.
update process complete ... (1/1)
********************************************************************
* GIGABYTE(TM) CLI "update" Command Executions Summary *
********************************************************************


Image check passed, release they read and parse from file passed, flashing pass, status success, but yet nothing.

Target IP: | Command Name: | Status: | Total elapsed times:
192.168.254.18 | update | Success | 1 mins, 47.050 sec.
Total success nodes : 1 fail nodes : 0
********************************************************************

 

[spyroot]

First of all thank you very much for reading this post and checking logs. Honestly very much appreciated. !

Yes but it same story I was thinking maybe it needed second update so it can finish the update of the BIOS.

With bios auto or WebUI etc it always show success, if I use use RBU file from web GUI it show progress and show success but after reboot nothing really. After full power cycle neither Web GUI nor IPMI etc show BIOS version it just 0.00. So in WebGUI you don't even have option to enter to BIOS nor I do see any video output from VGA ( this board has BMC VGA build in), plus all FRU show no hardware.

My guess BMC reads that after POST, which mean the board has only BMC at moment and no BIOS or it in some strange state. Before that I had on upper corner BIOS link to web interface for AMI, and in dashboard BIOS version in BMC and now it all gone.

Do you know by any chance ssh username and password to BMC (it has sshd runnng so I was thinking maybe I can check internal logs or something) ?

When you set a jumper to recovery, Do you need power on system in some specific way, so it start reading rom
file from the flash disk ?

In GIgabyte docs they said put AfuEfix64.efi file in SPI_UPDin some other docs rename amiboot.bot.
So I did in parallel just in case.

But it never read this flash so maybe it require some sort of special power on sequence ?
.
├── AfuEfix64.efi
├── RBU
│ ├── AfuEfix64.efi
│ └── image.rbu
├── RelNotes_MS33-AR0_F17.pdf
├── SPI_UPD
│ ├── AFUDOS.exe
│ ├── AfuEfix64.efi
│ ├── BgtEfix64.efi
│ ├── README.TXT
│ └── image.bin
├── System Volume Information
│ ├── IndexerVolumeGuid
│ └── WPSettings.dat
├── Tool
│ └── WIN
│ ├── afuwin32
│ │ ├── AFU_Anti-virus_warning.png
│ │ ├── f.bat
│ │ ├── f2BIOS.bat
│ │ └── readme.txt
│ └── afuwin64
│ ├── AFU_Anti-virus_warning.png
│ ├── f.bat
│ ├── f2BIOS.bat
│ └── readme.txt
├── amiboot.rom
├── f.nsh
├── f2BIOS.nsh
└── flashabl.rom

Top jumper is BIOS_RCVR

 

[spyroot]

But I can't go to BIOS. So the motherboard doesn't output from VGA anything, no keyboard response, nothing.
Notice in the screenshot I updated via image.rbu. It reboots, and nothing.

Hence I tried to restore via flash, they put a jumper on the motherboard but didn't indicate a step on how to force the motherboard
to read a flash drive. Because BMC update nuked BIOS during re-flashing.

Second screenshot. No BIOS in the listed firmware, no BIOS link on the left corner, no VGA, keyboard caps.
and the num lock is not responding as well.

 

[spyroot]

I think you are right. I think BIOS probably updated, I downloaded the binary and checked the binary blob and found the right symbols, and as you indicate, it doesn't detect CPU. After I upgraded BMC, I used the latest BIOS according to instructions from Gigabyte, and it looks like that BIOS update also has a microcode update for Sapphire rapids. I asked for support like ten times already. Provide the old BIOS, I know the version, but zero response. Honestly, I would stay away from a Gigabyte server motherboard. No support.

Now I need to figure out how to get the old BIOS.

 

[RageBone]

Do you have a postcode snooping option in the ipmi?
If no, then Giglebyte deserves its name.
My only experience with a dual sock Epyc board from them was that there is 0 info what is currently going on.
If everything is fine, you will eventually, get a video signal once the system is able to enter Bios. After a few minutes in my case.

But i also second Rollos questions, what CPU are you even using and what bios was it on, has everything ever worked before?

 

[spyroot]

Sapphire Rapids Xeon Gold 48 Core.
This one I used to update https://download.gigabyte.com/FileList/BIOS/server_mb_bios_MS33-AR0_F17.zip

I believe the initial bios was F01, so it is probably like MS33-AR0_F01.

And, no Numlock On, Kbd ON doesn't work. This is basically the first test I do, and I did USB behind and USB in mb itself.

 

[spyroot]

great idea,
do you get the Numlock LED of Kbd ON after a while ? this indicates a working BIOS/CPU but no VGA.
have seen issues like no VGA on gigabyte server boards with some BIOS; just plug the VGA after the Numlock LED of Kbd gets ON.

but we need to know:
CPU type ?
working BIOS ver. before update.

So far no result, I asked Gigabyte to provide an initial image F01 for my board but they don't want to.

Regarding the BIOS_RCVR jumper, Intel has instructions, but it doesn't work on a Gigabyte motherboard.

BIOS Recovery Procedure for Current Intel® Server Boards

Steps on how to perform a BIOS recovery on the current Intel® Server Boards.

www.intel.com

I'm not sure is due to a file name or file expected to be in a particular place, but it definitely doesn't read a flash.
I tried to use SATA with FAT32 / MBR same story. I did check the RBU file it is Intel serial flash for PCH ROM,
but it is not just a BIOS and microcode but ME and a bunch of other staff packaged in it.

The part I don't maybe, maybe this BIOS_RCVR must have a particular start seq. i.e., you need to hold something for X second
on the Gigabyte board before you start.

 

[spyroot]

Ok, I managed to get BIOS F01. As soon as I uploaded that, I
saw the VGA output and memory initialization, but it got stuck in the chipset init phase.
(my guess is because F014/17
etc. upgrade ME and microcode; hence I need, I guess downgrade that)

It looks to me like a couple of think. First that all current BIOS (except F01) essentially bust VGA output.
(in the release note in the internal BIOS note, I see that they do patch AST2600). My guess is all new.
BIOS essentially nukes VGA out. ( it is a bit unclear to me how VGA output and AST2600 are wired)

For now, have BMC init, memory init, and chipset init phases on the screen. ( but no USB)

2) The release note states that F014 has a USB fix. ( I don't think they properly
fixed that in none of the releases). Hence none of the USB BIOS restore actually works
since it doesn't detect any USB.

* I have 3 CPUs, all from Intel, back from Dec/Jan early testing for SR. They all should work.
I need to try a binary diff and see the microcode in F014/17 and F01 and how different it is.

So this one at least shows the entire POST.

❯ java -jar ./GbtUtility-2.1.61.jar -H 192.168.254.18 -U admin -P MGAP5100046 postcode current
*******************************************
* GIGABYTE(TM) GbtUtility v2.1.61 *
*******************************************
[192.168.254.18] Start to get current BIOS post code.
[192.168.254.18] Post code length : 54
0x01 0x02 0x03 0x04 0x05 0x06 0x23 0x23 0x00 0x02 0x7F 0x48 0x0E 0x49 0x4A 0x4D
0x15 0x52 0x55 0x19 0x31 0x00 0xA1 0xA3 0xA3 0xA7 0xA9 0xA9 0xA2 0xA2 0xA7 0xA7
0xA7 0xA9 0xA9 0xA8 0xAA 0xAE 0xE0 0xE0 0xE0 0xE1 0xE4 0xE3 0xE5 0xAF 0xAF 0xB0
0xBF 0xB5 0x7E 0xCF 0x7E 0xCD 0xB0 0x7E 0xC1 0x70 0xB1 0xB1 0x7E 0xC2 0x7E 0x70
0x7E 0x7E 0xC4 0xB1 0xB1 0xB1 0x7E 0xB4 0x7E 0xB8 0xC5 0xB2 0xC6 0xB3 0xB3 0xB3
0xB6 0xB6 0xB6 0xB0 0xB7 0xB6 0xB7 0xB6 0xB6 0x7E 0x7E 0x7E 0x7E 0xB7 0xB7 0xB6
0xB6 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7
0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7
0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7
0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7
0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7 0xB7
0xB7 0xB7 0xB7 0xB7 0xD8 0xB7 0xB7 0x7E 0xB7 0xB7 0x70 0x70 0x70 0x70 0x7E 0xB7
0x7E 0xB7 0xB7 0xBE 0xBE 0x7E 0x7E 0xD2 0x7E 0xD2 0xD6 0x70 0xB9 0xB9 0xB9 0xB9
0x7E 0xB7 0xB7 0xB7 0xB7 0xB8 0xB8 0xB8 0xD7 0xC9 0xDA 0xD9 0xDB 0xBA 0xB9 0x70
0x70 0x70 0x7E 0x70 0x70 0x7E 0x7E 0xCB 0xBB 0xBB 0xBB 0xBB 0xBB 0xBB 0xBB 0xBB
0xBB 0xBB 0x7E 0x7E 0xD0 0x7E 0xD0 0x7E 0xD0 0x7E 0xD1 0x7E 0xD1 0x7E 0x70 0x7E
0xB7 0xCA 0xCA 0xDC 0x7E 0xCC 0xBC 0xBC 0xBC 0xBC 0xBC 0xCE 0xC6 0x7E 0xBF 0xAF
0xE6 0xE7 0xE9 0xEB 0xEC 0xED 0xEE 0x03 0x23 0x02 0x22 0x00 0x02 0x7F 0x48 0x0E
0x49 0x4A 0x4D 0x15 0x52 0x02 0x22 0x50 0x00 0x04 0x06 0x0B 0x0C 0x0D 0x15 0x7F
0x00 0x7F 0x40 0x41 0x42 0x47
postcode process complete ... (1/1)
**********************************************************************
* GIGABYTE(TM) CLI "postcode" Command Executions Summary *
**********************************************************************
Target IP: | Command Name: | Status: | Total elapsed times:
192.168.254.18 | postcode | Success | 0.184 sec.
Total success nodes : 1 fail nodes : 0
**********************************************************************

 

[i386]

I find it hard to follow/undestand (output of tools/ipmi? mixed with your text/questions)...

Is the system running while you try to flash the bios via ipmi?

 

[RolloZ170]

I find it hard to follow/undestand (output of tools/ipmi? mixed with your text/questions)...

Is the system running while you try to flash the bios via ipmi?

sorry i have deleted my posts because i thought the OP don't want get helped.
he never answered my questions about CPU type in this thread.