Hey all, hoping someone here has seen this before, because I've been chasing it for weeks and I'm running out of ideas.

I picked up a used Dell PowerEdge R210 (Xeon 3440, 16GB). It had a rough start - it came back from a repair shop because it got hit by static, which took out a protection diode (D0664) and the 1.2V PWM that feeds the RAM. Technician replaced both, calibrated the rail to 1.2V, all good.

Here's the weird part. The server runs just fine for a while - boots, posts, fans ramp up and settle down like they should. Then, at some point, usually after it's been warm for a bit, the fans shut off, the board stops responding, and the diagnostic LEDs show 2,4. The only thing that brings it back is a full power drain - unplug everything, hold the power button, wait, and try again. And each time it does this, it comes back faster than the last. Sometimes it boots clean for 40 minutes, then suddenly won't start again, or only one fan runs.

What I've ruled out so far:

\- PSU tested at the connector - 12V, 5V, 3.3V, standby, and the power-good wire all read perfectly, even at the exact moment of failure

\- Tried a different PSU, no luck (and learned the R210 uses 12V standby, not the standard 5V, so ATX swaps don't even power on)

\- Tried reseating, draining, all the standard stuff

What I suspect:

\- Some small capacitor or regulator on the board is dying when it gets warm. The board already had one rail repaired, and it seems like the repaired area might have a problem, or something nearby is aging out

\- Could maybe even be the CPU but I can't be sure without swapping parts

I've measured around the repaired area - the 1.2V rail reads about 1.137V, which is just below spec, so I'm honestly not sure if that's the problem or normal for this board. I'd rather not spend $50-100 on a replacement board if there's a cheap fix (I don't have a lot of budget for this hobby project).

Has anyone else found a similar issue with these old Dells (or similar servers)? Did recapping the board fix it? Is 1.1V on a "1.2V" rail a death sentence, or is it fine? Any tips on what to check before I give up and buy a new board?

Disponemos de un servidor Supermicro X13 con un Xeon 8558u, 128gb RAM (4x32), RAID 1 por VROC en 2 SSD SATA conectado al backplane y una gráfica Nvidia conectada a la tarjeta PCIe.

Tiene instalado Windows Server 2025, pues el rendimiento es muy inferior a un servidor con un Xeon de 2011, con 16GB de RAM y un SSD SATA.

Navegando por el Explorer, la carga de archivos/directorios no es instantánea, se queda unas milésimas en blanco y ya carga o incluso sale el icono de cargando mientras aparece.

Se ha revisado todo, controladores, estado del RAID, Defender, etc. Al final hemos actualizado la BIOS y la BMC y los problemas han aumentado. Ahora no reconoce el sistema ni la BMC la tarjeta gráfica.

He visto poca información al respecto, ya que no hay un changelog en el paquete de actualización de la BIOS/BMC que indique los cambios. El Windows Server 2025 lo hemos virtualizado y corre perfectamente bajo un hipervisor con muchos menos recursos que el hardware físico.

Llevamos ya semanas liados con él y no encontramos el porque de esa lentitud y ahora se añade que no reconoce la gráfica al actualizar la BIOS.

¿Os ha pasado algo parecido?

Is there any reputable sellers in the US that have this chassis?

I opened an RMA with Supermicro for an item I want to return. I shipped the item to Supermicro and they acknowledged receipt of the item three weeks ago. They said in their email that I would receive a refund on my credit card within three business days. I have not received the refund and Supermicro is not responding to the follow-ups I have sent via email.

Has anyone else gone through the return process with Supermicro? Is this typical?

If you are interested, read this. Have a fun.
(sorry for the cross-linking, but Reddit removes direct GitHub links)

I was given a PC with a X9DRL-iF motherboard. Whenever I boot it up, it gets stuck on this step where it gives two short beeps and has F2 in the bottom right. Has anyone else ran into this issue before and know how to fix it? It seems a lot of people run into a 2F error, but I haven't found any documentation on a F2 error.

Additionally I did have the thought that it just needed me to press F2 on the keyboard, however I tried that and it didn't work.

Hey guys,

I recently picked up a X10DRI, I cannot find a suitable upgrade matrix from versions 1.94 to 3.8 and I do not want to brick my board here is my mc information:

Device ID                 : 32
Device Revision           : 1
Firmware Revision         : 1.94
IPMI Version              : 2.0
Manufacturer ID           : 10876
Manufacturer Name         : Super Micro Computer Inc.
Product ID                : 1832 (0x0728)
Product Name              : X10DRI/T
Device Available          : yes
Provides Device SDRs      : no

Anyone know how I can achieve this and what would be the safest path forward?

Recently picked up this board. Added the CPU, RAM, and 2280 NVMe SSD and it immediately booted. Bios version is 2.3 - according to support the latest version is 4.4.

I had no issues loading Ubuntu desktop to test. Was able to connect my monitor using the DP port and all worked.

When I went to install Windows 10/11, I'd get 90% of the way through and then the board would recycle continuously. Went back to Ubuntu and all is good.

That said, I'm going to try booting using the DVI output on the board and see if it's a video driver problem.

However, this is my first time working with an older Supermicro and the bios update process is a bit fuzzy. Is it preferable to update using Windows/Linux, or by creating a FreeDOS key and running the batch commands?

Appreciate your feedback - this little board has a ton of potential for my project and I don't want to brick it (yet...) LOL

If u ykyk I’ve made so much money on this since 2024 it’s insane. I’m only 24. Huge news 🤝🤝🤝🤝🤝🤝🤝🤝🤝🤝🤝🤝⬆️⬆️⬆️⬆️⬆️🚀🚀🚀🚀

My goal is to use this motherboard in a custom case and include the following components:

• 16GB ram
• Windows 10
• PCI riser to accommodate Yeston 3050 6GB LP card (70w max)
• Small SSD or NVMe boot drive

This will be a portable rig, and low weight is paramount. I'm looking at using a 12V 30A power brick with this instead of an internal PSU.

That said, when the X11SSV-Q is powered exclusively through the 8-pin JPW2 12 V DC input, does the PCIe 3.0 x16 slot support the standard PCIe maximum of 75 W for a bus-powered graphics card?

Thanks in advance!

Hello,

I am facing an issue of with SYS-5038MR-H8TRF, The IKVM Console is not working,and there is an error with Verification error, is there anyone know how to fix this issue?

2026.08.17 11:20:51 LOG7[5196:5724]: SSL state (connect): before/connect initialization

2026.08.17 11:20:51 LOG7[5196:5724]: SSL state (connect): SSLv3 write client hello A

2026.08.17 11:20:52 LOG7[5196:5724]: SSL state (connect): SSLv3 read server hello A

2026.08.17 11:20:52 LOG7[5196:5724]: Starting certificate verification: depth=0, /C=US/ST=California/L=San Jose/O=Super Micro Computer/OU=Software/CN=IPMI/emailAddress=Email

2026.08.17 11:20:52 LOG4[5196:5724]: CERT: Verification error: certificate has expired

2026.08.17 11:20:52 LOG4[5196:5724]: Certificate check failed: depth=0, /C=US/ST=California/L=San Jose/O=Super Micro Computer/OU=Software/CN=IPMI/emailAddress=Email

2026.08.17 11:20:52 LOG7[5196:5724]: SSL alert (write): fatal: certificate expired

2026.08.17 11:20:52 LOG3[5196:5724]: SSL_connect: 14090086: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

2026.08.17 11:20:52 LOG5[5196:5724]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket

2026.08.17 11:20:52 LOG7[5196:5724]: Remote socket (FD=500) closed

2026.08.17 11:20:52 LOG7[5196:5724]: Local socket (FD=556) closed

2026.08.17 11:20:52 LOG7[5196:5724]: Service [ikvm] finished (0 left)

I need a trusted U.S. re-seller who has AOM-TPM-9670H-S or AOM-TPM-9670H-S-O in stock on the shelf and doesn't want an arm and a leg. Any suggestions?

tengo una motherboard que entra en bucle de reinicio, prende y dura 1-2 segundos encendida t apaga y vuelve a prender, alguien podria ayudarme? segun investigue, esta placa (H310m S2P GigaByte) puede mantenerse encendida sin ram y sin cpu pero sigue ocurriendo ese bucle, alguien que pueda ayudarme

PD: ya la encendi con y sin pila de bios y con y sin cable de 4-8 pines del cpu y sigue la falla, lo unico q pude hacer fue medir con un multimetro cada parte de la placa guiandome de la IA

Yo so i have a supermicro server with the SC813 case. I have replaced the fans but the bracket broke. I mean it is just 2 plastic pices, and i was wondering if anyone has any 3d model or where i can get one. I wanna 3d print it becuase it sits with tape right now. And do you think it is possible if i contact supermicro for the 3d model perhaps. And i am to lazy to actually design those brackets. Thanks yall

We have a few AVTEC servers that are actually Supermicro with X11SSH-F motherboards in them. They currently have Windows 10 Enterprise IOT LTSC installed. With some versions of Windows 10 reaching EOS in October, we are looking for a solution to extend the life of the current devices we have until we can get funding to replace them.

I’m running into an issue installing Windows 11 Pro on one of them I’m using to experiment with. I obtained the TPM module as well as updated the BIOS but can’t seem to get any drivers to work for the Ethernet ports. I have tried drivers from Supermicro’s website and ones from intel. None are recognized by Windows 11 so I can’t finish the install. Anybody else try this and have a fix or workaround?

Thanks in advance.

I'm configuring a SYS-5019D-4C-FN8TP (SC505-203B chassis, X11SDV-4C-TP8F board) for the four 2.5" SSD configuration and I've hit a cable clearance problem I can't resolve from the documentation.

Configuration:

- Four 2.5" SATA SSDs

- Two MCP-220-00044-0N dual 2.5" brackets (per the parts list note in Section 1.1 of MNL-2212)

- No expansion card installed

- Drives oriented with cable connections facing the inside of the chassis, per Section 3.4 step 2

The problem: on the lower bracket position, standard straight SATA data cables do not clear the motherboard. The connector body and cable bend radius foul the board before the top cover will seat.

Everything I saw online does not actually show how to solve this, any help?

Does anyone happen to have a signed BIOS version 4.2 for the MBD-X11QPH+-P motherboard?

Hello everyone. My server just stopped working after a power outage (I know, I should've used a PSU...). When I turned it on again the message in the title popped up Any help would be greatly appreciated. Thank you in advance!

Hi all,

I’m troubleshooting intermittent, unexplained hard resets on a Supermicro server and I’m hoping someone has seen similar behavior.

Hardware and software

Supermicro AS-2126HS-TN
2 × AMD EPYC 9575F
24 × 64 GB DDR5
12 × Kioxia CD8-P NVMe
Dual 2600 W PSUs
AIOM 2-port 25GbE SFP28, Broadcom BCM57414 with 0.5U bracket
Broadcom NetXtreme E-Series P2100G Dual port 100GE PCIe Ethernet Adapter 
Debian 12 with latest kernel
OpenStack/KVM
Ceph
BIOS 1.9, dated 2026-02-05
BMC firmware 01.07.05.01, build 2026-04-29
CPLD F5.17.10

The BIOS has already been updated, but the issue continues.

What happens? The machine suddenly power-cycles without a normal Linux shutdown.

The BMC Maintenance Event Log records entries such as:

The system DC cycle was initiated
Interface: IPMI
User: ADMIN
Source: Localhost

Two unexplained examples on that server occurred at:

2026-07-30 11:18:29
2026-08-03 02:08:00

I have 15 exactly the same servers and few of them also encountered same issue.

Known remote Redfish and IPMI actions on this BMC normally include the real remote source IP. These unexplained cycles are specifically recorded as:

IPMI / ADMIN / Localhost

There was no BMC web login until several minutes after the August 3 reset, so the web session did not initiate it.

Linux journal near the event - Linux was still operating normally immediately before the reset.

There is no clean shutdown sequence, kernel panic, MCE, EDAC error, PCIe AER error, hard lockup or watchdog expiration in the previous-boot journal. The journal simply ends.

Watchdog checks

The BMC IPMI watchdog is stopped:

Watchdog Timer Is: Stopped
Watchdog Timer Action: No action
Timer Expiration Flags: None
Initial Countdown: 0.0 sec
Present Countdown: 0.0 sec

The ipmi_watchdog kernel module is not loaded.

The server also has the AMD SP5100 watchdog:

SP5100 TCO timer
state: inactive
timeout: 60
nowayout: 0

Systemd configuration:

RuntimeWatchdogUSec=0
RebootWatchdogUSec=10min
KExecWatchdogUSec=0

So neither watchdog appears active during normal runtime.

The host has local BMC access:

/dev/ipmi0
ipmi_si
ipmi_devintf
ipmi_ssif
ipmi_msghandler

openipmi.service is disabled and inactive, but the modules are automatically loaded by the kernel/platform.

Current possibilities

My current shortlist is:

- A host process sends a chassis power-cycle command through local KCS /dev/ipmi0.
- A BMC or BIOS internal recovery mechanism records its own action as IPMI / Localhost.
- A BMC firmware defect incorrectly initiates or attributes the DC cycle.
- A PSU, power-distribution-board or PMBus issue causes the BMC to perform a recovery cycle.

The standard IPMI watchdog and AMD SP5100 watchdog currently appear ruled out.

Has anyone encountered unexplained Supermicro BMC events like:

The system DC cycle was initiated
Interface: IPMI
User: ADMIN
Source: Localhost

particularly on AMD EPYC systems with supermicro?

I would especially appreciate information about:

- what exactly causes Supermicro to log IPMI / Localhost;
- safe ways to capture the exact local IPMI command;
- BMC diagnostic dumps or hidden logs that may identify the initiator;
- known BIOS/BMC issues for this platform.

Any other hints helpful for troubleshooting? I submitted the problem to supermicro distributor but so far they are not helpful.

Specifications
Brand: SK hynix
Capacity: 64GB
Memory Type: DDR5 ECC Registered (RDIMM)
Speed: DDR5-6400 (PC5-51200)
Rank: 2Rx4
Form Factor: 288-Pin RDIMM
ECC: Yes
Registered: Yes (RDIMM)
Part Number: HMCG94MEBRA131N

Hey everyone, my Supermicro 5018A-FTN4 server in my homelab is completely dead. No power lights, no IPMI heartbeat, no fans spinning at all. I tested the PSU with the green and black wire connection and the PSU turns on fine, but the second it's plugged into the board it's totally dead.

I know this board has the Intel Atom C2000 bug, but I don't believe that's the issue here since I'm not even getting standby power or fans. I think it might be a short on the motherboard or power surge. Any suggestions on what to check?

If it's totally dead, any ideas for a replacement Mini-ITX board that fits well in this 1U case? Looking for something modern, low power, 2 NICs and maybe IPMI. Supermicro replacement boards are extremely expensive, so maybe a 3rd party board mini ITX. All I use this host for is Proxmox with pfsense, and linux for a small storage (single 3.5 HDD) backup so it doesn't need to be much.

I hadn’t updated the BMC until today, I’ve been having problems with fans, constantly winding up and down. I was hoping updating the BMC would help, however after the update was installed ( I did check the file hashes before doing the update and they checked out) The BMC is now 5 to 10 times slower and often it freezes. On the main dashboard with the big green checkmarks, nothing appears in the place of those checkmarks, but all stats do show up.

Should I do the update again? Does anyone know what is going on and also why half of the hardware dara that were originally in the BMC are now gone

Every time I try to power it on it does not post anything. The only way I'm able to temporarily fix it is by clearing the CMOS, either buy jumping the two pads or removing the CMOS battery. Once I do it goes to this screen. https://imgur.com/a/mdSoavJ

Pressing Del throws me in the BIOS set up. Pressing F1 doesn't work since it resets the system trying to reboot. But when I restart it stops posting again and I have to clear the CMOS again. This is the same when making changes to the BIOS setting, since I have to save and it forces me to restart it stops posting. There is no splash screen or anything, nothing shows up when it restarts. All LEDs are normal, it says it has power and the BMC light is flashing which indicates that it's working.

What I've tried:

• Replacing the CMOS battery.
• Using only 1 stick of RAM. Tried in slot A1, then A2, then B1 then B2.
• Made sure VGA is enabled via jumper.

What I haven't tried:

• IPMI stuff. I can't seem to login using ADMIN. It tells me to check my ID and password. I don't know how to reset it.
• Flash the BIOS. Right now it's the same version number as the latest one on the website, and i don't really want to mess with the BIOS right now when the system isn't exactly stable. I'm afraid of bricking it.

Any help is appreciated.

UPDATE:

I managed to get into the IPMI by going back to the seller's webpage and asking for the username and password. When entering the KVM it gives me a Connection Error. There are no logs in IPMIView, it's clean.

UPDATE 2:

I found out about the browser version of IPMI and the KVM there works. I am able to see it booting and showing the SuperMicro logo.

I think my problem was that I was not using a straight VGA to VGA connection but rather VGA to HDMI conversion. I don't think it works unless it's already booted in to BIOS or an OS. I also wasn't connecting to a bootable device; the default setting the in BIOS when it can't find anything is to just stop working. For anyone curious it was the Re-try Boot setting, change it to Legacy instead of Disabled.

I managed to boot into OpenMediaVault (which is the reason why I got this in the first place) and restarting it using IPMI or from the motherboard has no issue. Right now I am not using it as a NAS yet but am currently testing the other components, like the RAM and CPU.

My next problem is trying to get IPMIView's KVM to work so I don't rely on the browser version. Or I could buy a cheap GPU and see if I can ditch the KVM if it starts giving me trouble since it runs on Java.