Supermicro X9QRI-F+ BIOS and Raid Controller

by hostseva

AWS Summit Los Angeles 2024 – Keynote with Dr. Matt Wood, VP of AI at AWS

Can I Get Advice On New Host Instead of Awardspace?

Supermicro X9QRI-F+ BIOS and Raid Controller | Web Hosting Talk

‘);
var sidebar_align = ‘right’;
var content_container_margin = parseInt(‘350px’);
var sidebar_width = parseInt(‘330px’);
//–>

Supermicro X9QRI-F+ BIOS and Raid Controller

Hello,

we have a supermicro server with DEPO stickers everywhere.

its configuration is as follows MB – X9QRI-F+ (BIOS 3.0a), raid controller – LSI MegaRaid SAS 9260-8i (fw – 2-130.403-3066)

There were five disks in the raid basket (SAS, SSD, SAS, SAS, SAS), in that order.

we needed to redo the raid array for other tasks.

we removed the SSD and restored the correct numbering of disks in the basket, after which the raid controller was no longer detected in the BIOS of the motherboard.

We tried to restore it to working capacity by changing the configuration of the disks in the basket, sometimes it was detected in the BIOS.

but when we booted into Windows, the disks were not detected in any way, we used all versions from 2008 to 2022, we used the megarade storage Manager program v. 17.05.06.00_MSM_Windows

I don’t think that the SSD drive served as a kind of stub for the basket to make it work.

we disconnected the wires from the raid controller and it was still not detected in the BIOS.

then we decided to try everything. we pulled out all the memory slots, all other equipment, including IPMI, except CPU.

we inserted the raid controller into another computer. It was perfectly detected in Windows (MB H510m-A PRO), but the BIOS did not see it either

we have updated the BIOS from the motherboard X9QRI-F+ to version 3.0 b

we tried to install different firmware versions on the raid controller which we could find on the site Broadcom, starting from the lowest to the latest.

some firmware was not seen even on a new motherboard.

at the moment we are using firmware 2-120-183-1415. it is well defined on the new motherboard and the program sees it.

when we insert a raid controller into a supermicro, we most often get a blinking cursor, or a BIOS boot stop on the controller BIOS screen. Sometimes with 3-4 attempts, it can boot into Windows, but the program still does not see the controller.

sometimes the bios itself sees the controller and checks the disks, which are now 4 SAS

important note – Windows (SSD) is connected to the motherboard’s internal SATA port

we can go inside the BIOS of the controller to do some actions in its program, but when we boot into Windows, the Mega raid program does not see it and cannot connect to the host

I read a lot of information on similar problems, but I did not find anything concrete on this problem. I did various BIOS settings but it does not help

Unfortunately, I dont know much about what was previously on this server, since Im a new employee, and the old one left a long time ago

Thank you for listening to me, I’m ready to write down the answers.