Description

This software is used to upgrade the BIOS version of the R5300 G6 server

Installation steps

Publish Description

Restrictions and cautions

Restrictions

The configuration import function is not available for upgrading the BIOS from a lower version to BIOS-6.00.20 and higher on HDM due to compatibility issues, but is available for upgrades from BIOS-6.00.20 and higher.

To avoid server startup errors, do not use the AFU tool to downgrade the BIOS from BIOS-6.10.XX to BIOS-6.00.XX with the user-configured settings retained.

BIOS-6.00.XX does not support EMR processor upgrade or downgrade on dual-processor servers.

Guidelines

To avoid BIOS boot failures, do not upgrade or reset HDM during BIOS boot.

If the system encounters a black screen and cannot boot after the BIOS firmware upgrade and restart, it may be caused due to the HDM firmware not being compatible. To resolve this issue, upgradeHDM to the version of the corresponding model as shown in Table 4.

Table 4 HDM firmware version for servers

As from the BIOS-6.10.48 for R6700 G6/R6900 G6, the signed firmware version is expanded to 81 M and requires an update in conjunction with HDM2-1.74 or above.

If a server equipped with Intel S4510 & S4520 SATA M.2 SSDs loses drives after a DC cold reboot, update the BIOS firmware to version 6.10.43 or later and perform an AC power cycle.

Version information

Version number

Version 6.10.52

Table 1 Target file name and MD5 checksum

You can access the HDM Web interface of the server to identify the BIOS firmware version in the Device information section of the Dashboard > Summary page, as shown in Figure 1.

Figure 1 Viewing the BIOS version number from HDM

BIOS built-in software version

Table 2 EMR&SPR CPU BIOS built-in software version

Supported languages

English

Chinese

Supported devices

H3C UniServer RXX00 G6

Hardware and software compatibility matrixes

Table 3 Hardware and software compatibility matrix for H3C UniServer R5300 G6

Update suggestions

This version is optional.

Update restrictions and guidelines

Make sure the software versions are compatible with each other.

To update both HDM and the BIOS, update HDM first.

Make sure the server is running in stable state before the update. That is, the server is powered off or has entered the operating system.

If the server enters the OS before the update, you must power cycle the server for the new firmware to take effect.

If you select the Retain or Restore method to update the BIOS, the update occurs during POST after the server is powered on again. During the update, do not disconnect the power source from the server, or forcedly power off or restart the server.

If you select the Forcedly restore method to update the BIOS, do not disconnect the power source from the server, or power off or restart the server.

Selecting the Restore or Forcedly restore method will restore the default BIOS settings, including restoring the boot mode in the BIOS to the default (UEFI).

During BIOS update with Forcedly restore selected, writing BIOS data, such as restarting the system or saving BIOS configuration from the BIOS setup utility, can cause data write errors. This can lead to BIOS ROM integrity check failures and even system starting failures. If the system prompts Flash Image Broken! System Halt!, forcedly power off the server, and then try to update the BIOS with Forcedly restore selected again.

As a best practice of bulk update, make sure you can update one server successfully before you update the remaining servers.

Problems Solved

Resolved problems in BIOS-6.10.52

202504240985

Symptom: R5500G6 server encounters abnormal slot number assignment when installed with SRP MCC processors.

Condition: This symptom might occur if the R5500G6 server is installed with SRP MCC processors.

202504080897

Symptom: After memory is disabled due to Buck Regulator Output Over or Under Voltage Lockout, the memory disable description in the HDM interface shows as "unknown reasons".

Condition: This symptom might occur if memory is disabled due to Buck Regulator Output Over or Under Voltage Lockout.

202504070138

Symptom: On a server with an onboard network adapter, after you set Onboard Port1 PXE to Disabled, the Exit interface still shows the boot option, and attempting to boot using this option results in a PXE disabled message.

Condition: This symptom might occur on a server with an onboard network adapter after you set Onboard Port1 PXE to Disabled.

202504171794

Symptom: After you upgrade the server to BIOS-6.10.51, the VMware boot option is not displayed in the UEFI BIOS Exit interface.

Condition: This symptom might occur after you upgrade the server to BIOS-6.10.51 if a VMware system is used.

New Functions

Version:6.10.52(2025/6/5)

Upgrade recommendations

optional Upgrade

Problems Solved

Resolved problems in BIOS-6.10.52

202504240985

Symptom: R5500G6 server encounters abnormal slot number assignment when installed with SRP MCC processors.

Condition: This symptom might occur if the R5500G6 server is installed with SRP MCC processors.

202504080897

Symptom: After memory is disabled due to Buck Regulator Output Over or Under Voltage Lockout, the memory disable description in the HDM interface shows as "unknown reasons".

Condition: This symptom might occur if memory is disabled due to Buck Regulator Output Over or Under Voltage Lockout.

202504070138

Symptom: On a server with an onboard network adapter, after you set Onboard Port1 PXE to Disabled, the Exit interface still shows the boot option, and attempting to boot using this option results in a PXE disabled message.

Condition: This symptom might occur on a server with an onboard network adapter after you set Onboard Port1 PXE to Disabled.

202504171794

Symptom: After you upgrade the server to BIOS-6.10.51, the VMware boot option is not displayed in the UEFI BIOS Exit interface.

Condition: This symptom might occur after you upgrade the server to BIOS-6.10.51 if a VMware system is used.

New Functions

Version:6.10.51(2025/5/21)

Upgrade recommendations

optional Upgrade

Problems Solved

Resolved problems in BIOS-6.10.51

202502240494

Symptom: A memory fault in the server triggered a CPU DCU alarm, but the DCU alarm information cannot be parsed. The SEL did not report the specific memory slot.

Condition: This symptom might occur if a memory fault in the server triggered a CPU DCU alarm.

202501130827

Symptom: The serial number of the specified CXMT memory module displayed in HDM does not match the information shown in the BIOS Setup interface.

Condition: This symptom might occur if you view the serial number of a CXMT memory module in HDM.

New Functions