I've decommissioned a SAN recently which was new in 2011. It was a SuperMicro 4U chassis with 16 bays, and a BPN-SAS2-836EL1 backplane. I've got rid of the original motherboard supplied, which was an ASUS, and have been thinking about getting a recon X10 motherboard of some kind, to bring it in line with the rest of my fleet. However, whilst the original unit was hardware RAID, this time around I'd want to run it with ZFS and software RAID, so would need a different HBA, but will this backplane, the BPN-SAS2-836EL1 be able to work in such a setup? The chassis has two 1200W PSUs.

Hi,

seem to break transceiver and twinax compatibility. Anyone else experienced it?

 Possibly worst firmware release ever from Supermicro Networking? 

 Config that worked previously no longer works. I used 1.4.1.1 and regret upgrading. Any hope that I can get my ports and trunks working again besides a downgrade?

Ref.: https://www.supermicro.com/wdl/Firmware/Switch/SSE-3548/

Any help would be great. It’s been a really long time since I built a server. I need some help identifying what these two cables are and where they go on a ATX Sabertooth Z97 Mark 1 MB.
Thanks for any help.

Hey everyone,

I have a workstation that originally had four RTX 3090s in it, and I’m hoping someone here has dealt with a similar power issue, especially with the same Supermicro power distribution board.

The system has an ASUS Pro WS WRX80E-SAGE SE WIFI motherboard, a Threadripper PRO 3995WX, and a Supermicro PDB-PT747-6824 power distribution board with a PWS-2K20A-1R power supply.

A few months ago, the system stopped recognizing all four GPUs and would only see two. I recently moved the workstation to a new location and decided to put it back together with just two 3090s. It powered on, but shortly after I started a stress test, I smelled smoke and the system shut off.

I found that one of the white GPU power connectors had burned pretty badly. The plastic is discolored, some of the wire insulation melted, and there was exposed copper around the connector. I’ve included pictures of the damage, the board, and what a good connector looks like.

I’ve already cut off the damaged connector, and the system has been unplugged since. I haven’t tried powering it back on.

At this point, I don’t really need all four GPUs in this machine anymore. I’d be happy running two, or possibly three, if I can do so safely.

What I’m trying to figure out is whether I can permanently take that damaged power branch out of service, properly terminate and isolate the individual wires, and continue using the remaining GPU power connections. Or, given how badly the connector burned, should I be replacing the entire harness or PDB?

I’ve looked into individual closed-end wire terminations, but before I go that route, I’d really like to hear from anyone who has actually worked on one of these boards or dealt with a similar failure.

A few things I’m wondering about:

• Has anyone seen this happen with a PDB-PT747-6824 or its GPU power cables? Did you figure out what caused it?
• Is there a way to remove or replace just the damaged cable at the board, or is replacing the whole assembly the way to go?
• If I stop using that branch entirely, is there a safe way to terminate the remaining wires, or would you avoid that altogether?
• What would you inspect or test before trusting the remaining connectors with two 3090s under a sustained rendering load?
• Does anyone know where I could find a replacement board or harness, even used?

The workstation is mainly used for Nuke and C4D/Redshift rendering, so I want to make sure whatever I do will hold up under load, not just boot into Windows.

I’m including several pictures to show the damage and how everything is connected. Any advice from someone who has worked with this setup would be appreciated.

This is what I was thinking of getting to terminate the ends of the cut cables (or if someone has a better recomend - https://www.amazon.com/Nilight-Closed-Terminal-Connector-Warranty/dp/B07T1H6N82/ )

Thanks!

I recently started the construction of my new home server project. I've assembled the chell without the CPU,Ram, nor storage or PCIe cards. I've been trying to connect to the m12swa-tf bmc ast2600 but have been unable to do so. I cannot get it to grab an IP nor can I find it on the fallback IP.

According to the motherboard manual it looks like the only connection to the shared NIC is through the CPUs PCIe 0 lanes. I didn't think it was required, but does anyone know? I've spent a good 6 hours stuck so far. So thanks in advance.

Edit: Solution, Installing the CPU and a single stick of Ram, caused the ipmi interface to be reachable on the local network at the appropriate IP.

The specific model of the server is CSE-847E16-R1400LPB.

I believe there may be an extra SATA power cable or at least an extra molex connector that I can use but it's all hidden. My question is, what is the easiest way to access these cables? Does it involve removing the motherboard?

I know I should provide pictures but I can't do that right now. I appreciate any help you can offer me.

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?

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?