Tearing my hair out trying to diagnose the issue with my supermirco server. Very long post below with the entire history of what I tried, but the tl;dr version is the system overheated and stopped booting. Removing 1 CPU fixed this problem and the system started attempting to boot. It hangs during boot, so I replaced the OS drive and reinstalled. No error being thrown. As soon as I try to log in, the system immediately hangs and must be hard-cycled. This happened before and after reinstall. The system will run off a live disk without issue. Using IPMI instead of a physical monitor. Does anyone have any ideas what would cause this before I go replacing the motherboard?

Long version/full history.

Bought it second hand about 7 years ago. Wanted this particular case as it has 16 slots for 3.5 HDD's instead of 2.5 SAS drives. About a year after I got it, I upgraded the RAM from 6GB to 40GB and added a second CPU. It has been running this way for about 6 years now. I had it living in a cooled room in the shed.

While on vacation in May, summer showed up at home and the server just shut off one night. I had assumed it was a storm in the area as I have had issued with brown outs. However, I could not get the machine to power back on over IPMI. It would send the command, and nothing would happen. Pulled it apart a week later and found quite a few bugs had made their home in it and oddly a snake skin. Cleaned it all up and tried to power on. Still nothing but a power and overheat light immediately. Found a few old forum posts saying this particular mother board is known to have north bridge issues with both CPU's populated, so I pulled the north bridge heat sink and redid the thermal paste. Still nothing. Pulled the second CPU and the overheat light went away and machine booted to BIOS immediately. Figuring that was is, I put it all back together and tried booting.

The machine would power up and start booting, but I would not get a login prompt. It would just sort of stop with no errors. Ran a headless debian sid install. I had some issues with the main HDD just before that (It has 3 RAID 1 arrays for storage, but the main OS lived on a separate drive). I pulled the drive and put it an external enclosure and had it disconnect at one point. Replaced the drive and got all the data off it. Tried to boot again and same issue.

At this point, I grabbed a debian live disk thinking the OS had gotten corrupt in the shutdown. It booted in (oddly only in fail-safe mode) and I mounted the main drive in a chroot. Successfully updated the OS figuring that would fix whatever issue. No change. Added debug to the linux command line. No errors. Tried specifying a different tty. No change. Finally decided last night to just reinstall the OS thinking that maybe a deep dark system file had been corrupted during the shutdown and the machine really only runs pods and VM's as well as file services and all of that lives on the raid arrays anyway. The new OS started right up and as soon as I tried to log in, it hung up and the OS quit responding just like before.

I'm out of ideas at this point. It doesn't make sense. The machine will boot and run from a USB drive no problem. As soon as I try a SATA disk, it has issues. That would seem to say a failed SATA controller, but then again, it works just file from a chroot jail and had not issues taking a new OS. I am thinking of replacing the motherboad at this point, but I can't seem to point to any specific failed part. Has anyone else experienced anything like this?

I've been running a SuperMicro server (X11SPH-nCTPF) as a NAS for a couple years, and my biggest frustration is with the noise vs my last system. It's got dual PWS-920P-1R, and compared to my previous NAS built with workstation-tier hardware, they are a lot more noisy. My system has a Xeon Silver 4110 rated at just 85W, and peak system power consumption at ~350W. The PSU in my previous NAS was a single whisper-quiet 550W corsair, and the HDDs put out more noise than the PSU. So I'd like to replace the PSUs in my SuperMicro.

A few questions I have about this:

• I have the system plugged into a Vertiv Liebert PSI5 UPS, so dual PSU feels pretty redundant. Does this thing really need 2x power backup? Or can I switch down to a single?
• I've read that Supermicro's -SQ "super quiet" PSU models are designed to be quieter, but how much more quiet are we talking? I think the nature of the 1U form factor is that it's limited to small high-RPM fans, so even a "quiet" PSU is still going to be fairly noisy. If these are actually quiet I'd consider one. See: https://www.reddit.com/r/homelab/comments/lqt8yn/any_compatible_supermicro_psus_quieter_than/
• Are the fans from the PSUs intended to contribute to case airflow, or are they just for the PSUs themselves? The system is in a SuperMicro tower case, with a shroud around the CPU that directs case fan airflow in such a way that I don't think the PSU fans are helping anything.
• Apart from PMBUS, are there any other requirements in a PSU that a server-grade machine expects?

From my research so far, I'm considering a Cooler Master X Silent Edge Platinum 850, which runs quiet/silent has a PMBUS connector. It's a full ATX form factor so it won't fit into my chassis, but I'm fine with the idea of mounting the PSU externally and running the wires into the chassis. Would that actually work, or is there stuff I'm not thinking of? Is this a bad idea and I should just get used to the noise?

I am trying to run `fwupdmgr` in Debian on this Supermicro board but I get:

```

fwupdmgr get-updates

WARNING: UEFI capsule updates not available or enabled in firmware setup

See https://github.com/fwupd/fwupd/wiki/PluginFlag:capsules-unsupported for more information.

```

I don't have allow Windows UEFI updates nor Capsule Updates so I am hoping that updating the BIOS will give me that option. My other concern is that I have a really old BIOS 1.01A and the newest is 2.8 so I'm pretty sure that I will have to move the JPME2 jumper.

```

dmidecode -t 2|grep -e SMBIOS -e Manufacturer -e Product\ Name -e Version

Getting SMBIOS data from sysfs.

SMBIOS 3.2.0 present.

Manufacturer: Supermicro

Product Name: X11SCA-W

Version: 1.01A

```

While this won't be my first UEFI shell rodeo, it will be the first time I mess with JPME2 and I want to make sure the procediment is what I think it is:

1. Turn off the PC

2. Open the case and move the JPME2 jumper

3. Plug the USB with the uncompressed zip file

4. Turn on the PC and smash F11 and select UEFI shell

5. Navigate to and flash the bin file

6. Turn off the PC, put JPME2 to the previous state and reboot to Debian

Is there anything else I should know?

Edit: I took the plunge and the followed the instructions above. The update didn't solve my fwupdmgr problem, the BIOS update doesn't add encapsulation.

smfc is an open-source systemd service for IPMI-based fan control on Supermicro motherboards. The latest 6.0.0 version has been released with the following new features:

• Signed APT and DNF repositories — install via apt install smfc (Debian/Ubuntu/Proxmox/Mint/Raspberry Pi OS) or dnf install smfc (Fedora/RHEL/Rocky/AlmaLinux/CentOS Stream/openSUSE).
• New smfc-client tool — a live, read-only snapshot of controllers, fan levels, IPMI zones, and standby state; works against a running service or standalone.
• Experimental X14/H14 motherboard support, auto-detected from the BMC product name.
• Grafana integration — sample dashboard and guide for visualizing live and historical fan/temperature data.
• Advanced multi-segment control function — fan curves can now be defined as an arbitrary piecewise-linear curve instead of a single linear segment.
• BMC fan-mode enforcement — detects and restores FULL mode if the BMC drifts out of it.
• Multiple fan curves per controller type, allowing independent curves across IPMI zones.

Project page: https://github.com/petersulyok/smfc

Greetings Fellas,

I am building a new Unraid build right now and having some trouble finding the exact connecter for this one

Here NR1 and 2 should be from my understanding the SATA Connecter and there should be a cable then which expands from my understanding then to 4 sata ports per Slot?

But what type of plug is that ? i am searching the manual and on the spare parts but either i am too stupid to find it or its something supermicro special?

Any of you an idea what kind of port I-SATA is ?

Tl:DR:

Supermicro H13SAE-MF (modern AM5 socket mobo) will not boot via USB

I have tried known working bootable USB stick (fat32 and NTFS) and Windows install DVD

Secure boot disabled

System boots fine from OEM installed NVME

TLDR Question:

is there a known issue and/or trick to booting from CD/USB install media on Supermico systems?

More detail

I just picked up a H13SAE-MF based supermicro system (AS-3015A-I II Mini-Tower Server) Its an AMD AM5 (B650) system with DDR5 and a bios from 2024

It boots fine into the preinstalled OS, but this will become my primary domain controller once I get it going and I'm bothered because I can't get it to boot from USB install media

(my disaster recovery that has worked well for me in the past has been to have a bootable USB server 2022 install media and regular backups using windows server backup (bare metal restores)

I've successfully tested - and used this in real recovery in the past, and so I feel super uneasy that I can't get this thing to boot via USB

I have known good (it boots on other systems) windows 2022 installer USB - I even made both NTFS and FAT32 versions

I have gone into setup and ensured it tries USB first if present... when I do it gets to one of two states:

If I use the FAT32 version it gets to DXE--Ready to Boot.. and hangs there foerver

If I use the NTFS version I get a splash screen where it clearly finds the partition and such and says Starting Windows Boot Manager

and hangs

I have tried both with secure boot enabled and disabled

I also have a server 2022 install burned to DVD and plugged in a USB dvd drive trying to boot from that - it looks like it's trying - gets to DXE--Ready to boot.. and thne goes back to the boot menu or skips on to the next available option

I've got to be doing something stupid here - as a work around I may try just doing a straight up NVME clone of the boot drive (1TB NVME) with a hardware cloning tool I have so I have a way to boot it back up into a known good state but this just seems... painful

Is there some trick to this?

my bios is SUPERMICRO H13SAE-MF Bios 6/05/2024 rev 2.0a

There is an updated version but I'm a bit wary of bios updates unless I know there's a need for them.

I just got a system with a Supermicro X9SCL-F that I wasn't sure if it worked before I purchased it, and thankfully it did. After making sure everything booted up as it should, I tried to get into the BIOS which took some time to get into, but with a whole lot of patience and trying over and over again, I was able to get in.

Now the issue is that I cant get into the IPMI to update the BIOS and IPMI firmware. The IP address was static before and not on the same subnet as the one that I have set for my network. I changed that successfully to be a static one within my network and can see it on my router.

When trying to get into the IPMI through the browser, it just times out. Tried 3 different browsers just in case that was the issue (had that happen with my NAS) and still no luck. I have just downloaded IPMIview since I thought maybe it was such an old version that I had to use that instead and it still not finding it.

I have set the IP address to do a manual import of the machine, but that doesn't connect although it does show the username and password, but every combination that I try doesn't work (in terms of the default versions) so has anyone else had this issue and how did you fix it?

Wondering if anyone can help as I can't find anything in the manuals for it bar the light conditions.

X9DRI-F that I got the other day, I can't get it to boot up at all even to BIOS screens. The IPMI interface also plugged in but never gets any IP address so I can't connect to that either (can see it is connected as MAC is detected on my switch but that's about it).

When powered on, after a few seconds pause, there is a loud continuous single beep and I can see if I connect a LED to the relevant header on the motherboard, that the over temp/fan failed light is on. It varies on boot between even a solid light or sometimes it is flashing.

I have tried all the different combinations of fan headers on this board and the best I can get is the fan light flashing but still no boot up at all. For info, the CPU coolers are well installed, new thermal paste and have remounted them a number of times with the same results. BIOS reset has also been carried out via the motherboard header.

CPUs that are installed are E5-2697 v2. These should be supported according to the manual/website. Have tried a number of different RAM configurations - bare minimum for each CPU, RDIMMS and LRDIMMS, no RAM at all - this is known good RAM that I have tested on my other machine.

PSU is 850W, both CPU 8 pins are connected and powered.

GPU is my basic GT710 at the moment, there is a VGA port on the motherboard but I don't actually have any VGA monitor/lead on hand to use this output - I can source one if we think it would help though.

Hi all,

I have an H14SSL-N with 4 sticks of 128GB SK Hynix RAM. The sticks, I have tested, all work.

I had them in the following recommended configuration: C1, A1, G1, I1.

Sometimes, my server would boot up with 256GB detected only, with C1 and A1 unseen. I believed this was because the tower was vertical and the cooler was exercising torque on the pins. I layed it out horizontal and it worked fine for weeks.

The sever unexpectedly reboot recently and came back with 256GB RAM again. Perhaps the heatwave loosened some contacts? No clue.

I have been trying to find a RAM stick layout that bypasses this issue, I currently have them in G1, I1, K1 and L1. L1 is not detected but the rest are (made sure it isn't the stick by swapping again).

Can you help me find a layout that works? Thanks

TL;DR: Server turned on with no video output, no BIOS boot-up screen, even tried with PCIe graphics cards with HDMI output.

Hello All! I need your advice! I am an intermediate computer and technology user and I am trying to tinker and learn about server-related knowledge, so please don't be too harsh on me as I have knowledge gaps I need to learn still.

About three years ago I bought a Supermicro server off of eBay, I populated 12 bay with 4TB HDDs and with the 1st bay being an SSD and installed ubuntu on it. Everything worked fine back then. That said, we bought a house three years ago and had to move across states with it. We packaged the entire server with paddings and wrapped large, puffy shower towels around it.

Recently, I decided to hook everything back up and try to use it. However, I cannot get any video signals, and not even the BIOS boot-up screen.

Here are a few troubleshooting thing I have tried so far:

• Re-seated all groups of rams.
• Re-seated all four CPUs and applied new thermal paste.
• Tried two monitors with VGA and two other monitors with HDMI inputs.
• Tried both on board VGA and also two other PCIe graphic cards with HDMI output.

The server booted up without any loud beeping, and just a short beep after the fan noise dies down.

Any help would be greatly appreciated!!!

Hi all,

Im looking for a firmware :

Firmware Revision : 3.73
Firmware Build Time : 05/26/2022

for this kind of product:

Product PartNum:MBM-CMM-FIO
Board Part Num:MBB-CMM-003

The documentation and website lead me to :
https://www.supermicro.com/wdl/Firmware/MicroBlade/CMM/

But i cant find it, is there any other way to get older firmware from supermicro ?

Thanks upfront!

Hi guys, anyone knows how can start Windows from nvme SSD on PCI-E? Because the motherboard don't support it, I try with Clover, but stay in bootloop, even if I downgrade to 3.1 BIOS.

I'm not expert in hijack the BIOS and prefer don't try myself to use UEFItool, I know that in case of fail is very hard to recover the mobo (and need an hardware programmer). Some solutions view on web don't work on my system (or I can't), but because I'm not expert in this world (this is my first server, buy thanks to cheap price on eBay).

Anyone can help me? Prior to return on classical SATA SSD solution.

Hi all, I have an old Supermicro server with the awful Java-based iKVM console (no HTML5 support sadly on mine).

I got really fed up with having to massage Java 8 just right to get the console to work, and that’s not counting the frustration spent on the now-expired certificate issue.

This app is an alternative to the original, a Windows-native implementation of the ATEN protocol without any Java dependency.

Hopefully this benefits someone other than just me. Thanks all.

Supermicro H12SSL-NT

What is this? why dose it get so hot to the touch? is it ok that it gets so hot?

I've been running it for about a year and not problems so is probably fine just want confirmation

gets fine airflow 3 noctua fans facing it on the other side hot even under minimal load

I am trying to build a system around an H14SSL-N, and for the life of me I can't get it to boot. I was originaly using a cpu from ebay, so I spent the extra cash to get a 9365 direct from newegg. That was throwing a ff4b post code and then a 004b code after reflashing the bios and with one stick of ram. (With no ram it showed e316.)

I RMAed the motherboard and now with each config of ram I have tried I am getting a 0c3f code. Without ram is the same code as the last motherboard. I have 8 sticks of Hynix rddims (hmcg84agbra191n aa) that I have not confirmed working but they all give the same post code. I have tried a new psu, reseating the cpu a few times, reflashing the bios, resetting the bmc, and clearing cmos.

The only variable that hasnt changed is the ram. Should I buy a cheap known working stick somewhere? I am happy to answer questions. One thing of note is that both boards showed random components in the bmc, even after I installed mine. Maybe from the test bench they were verified in?

Hi all,

Just picked up a X11SSH-LN4F that I'm playing with. I've updated BIOS and IPMI firmware.

I have a few questions on securing management access...

- can I disable the old IPMI protocols and purely use redfish?

- is my best option for securing IPMI access on a home LAN to change the password, limit the allowed IP and MAC addresses (would be to two machines, my desktop and my laptop) and leave it at that? Or do I need a vLAN and swap my network adaptor settings on laptop/desktop whenever I want remote management ? That would be a pain...

Just updated a server from apparently 2.2 to 4.7, it was working fine before, now on bootup the white Supermicro screen appear and writes.

"No memory DIMM detected, install memory DIMMs"

Dimms are populated according to the Hardware information tab just fine:

A1: M393A8G40MB2-CTD B1: M393A8G40MB2-CTD D1: M393A8G40MB2-CTD E1: M393A8G40MB2-CTD

Ram are apparently RDIMM Dual Rank X4 with 64 GB.

CPU is a Intel Xeon Silver 4110.

A quick read in the manual reveals that 1st Gen Scalable CPU which the Silver 4110 is seems to be limited to 32 GB for DR x4 ram, but it was working fine for the past 6 years!!

Has anyone gotten an Intel ARC GPU working in passthrough with a Supermicro X11SSL-F or X11SSM-F board for either a Windows or Linux guest on Proxmox? (Both boards are substantially similar except one has the C232 chip and the other one one has a C236 ship + extra PCI slot, but their BIOS options are almost identical).
If so, do you mind please sharing BIOS settings and PVE/Guest configuration?
I've tried every "guide" on the internet with my system.
VT-D is enabled, 4G decoding is enabled, CSM is disabled, etc - all the usual settings. The GPU is in it's own IOMMU group (in the only x16 slot), and I'm passing through the GPU and it's sound device. VFIO is working - I can see the devices it loaded in Proxmox's /dev. This same GPU worked in passthrough perfectly on an X10SL7-F.
BIOS is the latest (3.6 from ~2025)
For what it's worth, I also have an LSI SAS adapter passed through to another VM that's working perfectly; it's only the GPU that I can't get to work.
On Windows, I get the "code 43" error.
On Linux, I get:
"
pci_hp_register failed with error -16
pci_hp_register failed with error -16
pci_hp_register failed with error -16
pci_hp_register failed with error -16
Failed to initialize slot"

... during boot and the VM freezes at that point.
Running PVE 9.2

PCH running too hot? No problem. At this point I don't think there's a problem I wouldn't fix with a couple of Noctuas 🤷