No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


System Is Stuck at the LSI MegaRAID SAS-MFI BIOS Screen When the RAID Controller Card of RH2288 V3 Is Being Read

Publication Date:  2019-04-23 Views:  534 Downloads:  0

Issue Description

The RH2288 V3 serves as a computing node. After the OS is installed and restarted, the system is stuck at LSI MegaRAID SAS-MFI BIOS screen soon after the Huawei logo disappears. After five minutes, the system cannot be found.

Alarm Information

The BMC does not report any alarm.

Handling Process

1. Apply for spare mainboards, CPUs, DIMMs, and RAID controller cards and perform tests on site. Analysis on the collected information and logs shows that no problem is found.

2. Perform cross tests by replacing the single- and dual-CPU, DIMM, and mainboard, or reinstalling the supercapacitor, RAID controller card, and SAS cable. No problem is found.

3. Perform minimization test to the module level. After the TF card is removed, the system can start normally. Therefore, it can be concluded that the fault is due to the TF card. After a spare TF card is used to replace the faulty TF card on site, services are restored.

Root Cause

During the server startup, the RAID controller card is not detected when it is read. As a result, the server fails to start up. The possible cause is that the TF card is faulty or the connection to the RAID controller card is disconnected.


1. Log in to the BMC and check whether an alarm is generated. If yes, handle the alarm. If no, go to the next step.

2. Remove and insert the RAID controller card, SAS cable, TFM card, and supercapacitor to locate the fault. If the fault persists, go to the next step.

3. Perform cross and minimization tests to identify the faulty component.


If the system is stuck at the RAID controller card screen, the problem is probably specific to the RAID controller card. In this case, check the RAID controller card and the modules that are connected to the RAID controller card.