F5F Stay Refreshed Hardware Desktop Issue with Supermicro Barebone 1029GQ-TRT not booting, no POST and no screen display.

Issue with Supermicro Barebone 1029GQ-TRT not booting, no POST and no screen display.

Issue with Supermicro Barebone 1029GQ-TRT not booting, no POST and no screen display.

R
RussAbeJr
Junior Member
8
11-08-2025, 01:18 AM
#1
Hello, I am setting up a server using the Supermicro Barebone 1029GQ-TRT and facing a problem where the system fails to POST and no output appears on the display. The machine is brand new, and I have gone through all the troubleshooting steps, but the issue persists. Below are the complete details:

System Specifications:
- Motherboard: X11DGQ (Supermicro Barebone 1029GQ-TRT)
- CPUs: 2x Intel Xeon Platinum 8259CL (24 cores, 2.50GHz)
- RAM: 32GB 2Rx4 PC4 - 2933Y - RB2 - 12 (RDIMM, 2933MHz) from SKhynix
- GPUs: 2x NVIDIA RTX A5000
- Storage: Samsung 870 EVO 1000GB (OS) + Samsung PM893 1920GB (Data)
- Power Supply: 2000W redundant provided by the Barebone

Symptoms:
- No POST: The system powers on but no display output is visible (no POST screen, no BIOS screen).
- Fan behavior: Fans spin at full speed initially, then slow down or stop occasionally.
- IPMI access: I can connect via IPMI, but the Hardware Information tab shows inconsistent data (likely from prior testing), and no POST codes appear.
- No beep codes: I have disconnected components one by one, yet no beep sounds are produced.

What I Have Attempted:
- Swapped and reinserted CPUs in different sockets.
- Removed and reinserted RAM, testing with only one stick in various slots.
- Ran the server without RAM or CPU (no display, abnormal behavior, powers down after a few seconds).
- Tested with just 1 RAM and 1 CPU (same issue).
- Verified IPMI login using default credentials.
- Reset CMOS via jumper (no visible effect).
- Rechecked CPU socket and RAM placement for proper contact (appears intact).
- Confirmed power connections are correct and internal.

Questions:
- Is it typical to not hear beep codes even when RAM and CPU are missing?
- Are there additional steps I should follow to diagnose this further?
- Could the BIOS version be contributing to this issue? Should I attempt an update, even without a functioning POST?
- Might a faulty CPU or RAM cause the system to fail to POST without any beep sounds?
- Is there a possibility of CPU incompatibility (despite being v3, should it support backward compatibility)?
- Please refer to the Mainboard Manual and IPMI Manual for guidance.

Thank you in advance for your assistance and advice. I look forward to your response.
R
RussAbeJr
11-08-2025, 01:18 AM #1

Hello, I am setting up a server using the Supermicro Barebone 1029GQ-TRT and facing a problem where the system fails to POST and no output appears on the display. The machine is brand new, and I have gone through all the troubleshooting steps, but the issue persists. Below are the complete details:

System Specifications:
- Motherboard: X11DGQ (Supermicro Barebone 1029GQ-TRT)
- CPUs: 2x Intel Xeon Platinum 8259CL (24 cores, 2.50GHz)
- RAM: 32GB 2Rx4 PC4 - 2933Y - RB2 - 12 (RDIMM, 2933MHz) from SKhynix
- GPUs: 2x NVIDIA RTX A5000
- Storage: Samsung 870 EVO 1000GB (OS) + Samsung PM893 1920GB (Data)
- Power Supply: 2000W redundant provided by the Barebone

Symptoms:
- No POST: The system powers on but no display output is visible (no POST screen, no BIOS screen).
- Fan behavior: Fans spin at full speed initially, then slow down or stop occasionally.
- IPMI access: I can connect via IPMI, but the Hardware Information tab shows inconsistent data (likely from prior testing), and no POST codes appear.
- No beep codes: I have disconnected components one by one, yet no beep sounds are produced.

What I Have Attempted:
- Swapped and reinserted CPUs in different sockets.
- Removed and reinserted RAM, testing with only one stick in various slots.
- Ran the server without RAM or CPU (no display, abnormal behavior, powers down after a few seconds).
- Tested with just 1 RAM and 1 CPU (same issue).
- Verified IPMI login using default credentials.
- Reset CMOS via jumper (no visible effect).
- Rechecked CPU socket and RAM placement for proper contact (appears intact).
- Confirmed power connections are correct and internal.

Questions:
- Is it typical to not hear beep codes even when RAM and CPU are missing?
- Are there additional steps I should follow to diagnose this further?
- Could the BIOS version be contributing to this issue? Should I attempt an update, even without a functioning POST?
- Might a faulty CPU or RAM cause the system to fail to POST without any beep sounds?
- Is there a possibility of CPU incompatibility (despite being v3, should it support backward compatibility)?
- Please refer to the Mainboard Manual and IPMI Manual for guidance.

Thank you in advance for your assistance and advice. I look forward to your response.

T
tlasitz
Junior Member
14
11-09-2025, 08:04 PM
#2
The BIOS must be version 3.2 or newer to work with the 2nd Gen Intel® Xeon® Scalable processors (Cascade Lake-R).
T
tlasitz
11-09-2025, 08:04 PM #2

The BIOS must be version 3.2 or newer to work with the 2nd Gen Intel® Xeon® Scalable processors (Cascade Lake-R).

P
pedro_tkf
Senior Member
643
11-11-2025, 10:24 AM
#3
Firmware Update: 1.76.39
Build Details: Released on 10/13/2021
BIOS Information: Version 3.5, Built 07/19/2021
Redfish Specification: 1.0.1
CPLD Model: 01.b2.14
P
pedro_tkf
11-11-2025, 10:24 AM #3

Firmware Update: 1.76.39
Build Details: Released on 10/13/2021
BIOS Information: Version 3.5, Built 07/19/2021
Redfish Specification: 1.0.1
CPLD Model: 01.b2.14

A
ARMADAE
Member
66
11-12-2025, 07:33 PM
#4
I discovered this information about the Intel Xeon Platinum 8273CL. I gained a lot of knowledge this way, through trial and error, which wasn't a pleasant process. However, I hope this thread provides useful details to help others avoid the same difficulties I faced. Some context: I was...
A
ARMADAE
11-12-2025, 07:33 PM #4

I discovered this information about the Intel Xeon Platinum 8273CL. I gained a lot of knowledge this way, through trial and error, which wasn't a pleasant process. However, I hope this thread provides useful details to help others avoid the same difficulties I faced. Some context: I was...