r/supermicro • u/andy-codes • Jun 04 '26
PCH running too hot? No problem.
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 đ¤ˇ
r/supermicro • u/andy-codes • Jun 04 '26
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 đ¤ˇ
r/supermicro • u/hacman113 • Sep 29 '26
Hello everyone â r/supermicro is active again and has had a full community refresh.
This remains an independent, unofficial community for Supermicro servers, motherboards, chassis, storage and BMC/IPMI. It is not operated by Supermicro and it is not a replacement for official support.
Whatâs changed:
- clearer rules covering relevance, civility, commercial activity, confidential information, sensitive details and useful support requests;
- required post flair so troubleshooting, compatibility, firmware, storage, networking and buying-advice posts are easier to find;
- optional user flair for homelab, enterprise and integrator backgrounds, plus moderator-verified employee and partner flair;
- a new community wiki with posting, firmware, compatibility, fan-control, official-support and security guidance;
- improved report/removal reasons and conservative automated checks for obvious sales spam, referral links and exposed sensitive information;
- a cleaned moderation queue, refreshed navigation and new community artwork.
Please read the Start Here guide: https://www.reddit.com/r/supermicro/wiki/index/ before posting. For support requests, include the exact model, firmware versions, components, full symptoms or errors and what you have already tried. Redact credentials, public IPs, serial numbers, licence keys and case/order details.
Commercial participants are welcome to help, but advertising, sales listings, referral links, lead collection and unsolicited âcontact meâ offers are not. Relevant affiliations must be disclosed.
This is a first pass, not a finished monument. What would make r/supermicro more useful? Please comment with feedback on the rules, flair, wiki, recurring threads or any gaps you spot.
r/supermicro • u/Alpha-9-9-1 • Jul 10 '25
smfc 4.0 released with GPU support and free assignment of IPMI zones.
This is a Linux systemd service implementing IPMI fan control for Super Micro motherboards (X10-X13). It can help to minimize your fan noise on your Server / NAS. See more details here:
https://github.com/petersulyok/smfc

r/supermicro • u/furay20 • Jan 29 '24
Good morning,
Through a series of unfortunate events, I ended up purchasing an X10SLH-F motherboard I didn't really want/need. I also accidentally stumbled on a slowly disappearing guide (https://web.archive.org/web/20210801000000*/https://www.win-raid.com/t871f50-Guide-How-to-get-full-NVMe-support-for-all-Systems-with-an-AMI-UEFI-BIOS.html) which referenced NVMe booting on AMI UEFI BIOS's. I saw people referencing X9 boards around the Google, but not many referencing X10. I opted to take the YOLO approach and followed the instructions from Mar/6/2021 (on the Wayback Machine) utilizing the "NvmExpressDxe_Small.rar" package (NvmExpressDxe_Small.ffs - dated 31/03/2018 6:00 PM) and MMTool 4.50.0.23.
I grabbed the latest BIOS (3.4) and tried it, and, it "worked". With the factory BIOS, I could not see the NVMe drive as a bootable option. With the modded BIOS, I could. Linux/BSD installed great, however, I noticed that regardless of whatever Windows installer I used, it would get to the booting screen, turn black, and eventually just reboot. Through some more Google-foo -- I found this: https://forums.servethehome.com/index.php?threads/help-wanted-supermicro-x10sl7-f-now-stuck-in-infinite-boot-loop.33549/ -- which details folks complaining about 3.4, and 3.3 BIOS versions causing this issue.
I located BIOS 3.2 and performed the aforementioned BIOS mod again, and it's been working great. I now have the ability to install Windows onto an NVMe SSD on an X10 motherboard.
I figured I'd share what I found, and hopefully someone comes across this post in the future and it helps them out as well.
Cheers
r/supermicro • u/tjone270 • Jun 19 '26
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.
r/supermicro • u/Alpha-9-9-1 • Mar 07 '26
smfc 5.0 released with support of shared IPMI zones and a new NVME fan controller.
This is a Linux systemd service implementing IPMI fan control for Super Micro motherboards (X10/H10-X13/H13). It can help to minimize your fan noise on your Server / NAS. See more details here:
https://github.com/petersulyok/smfc

r/supermicro • u/[deleted] • May 24 '24
I decided I wanted to expand my home lab to include a server with remote tools but also wanted something fairly modern and expandable.
This config at Micro Center had the normal motherboard and case and then included a Ryzen 7 7700x, 16GB of RAM which I immediately swapped for 64GB and a 940GB M.2 card. I also tossed a 10Gtek 10GB card in it for good measure.
So, put it in a 1u slot in my rack and fired it up. I haven't ever used IPMI but after about 45 minutes of trying to get it working I figured it out, mounted an ISO of Proxmox and had Ubuntu installed in a VM in about 30 minutes. Amazing. I hadn't touched a server in about 6 years and this is fast and quite quiet for a 1u unit. I have a QNAP NAS also on a 10GBe connection so will be connecting several more VMs and backing up some cloud data to drop usage as cloud providers pull back their storage for free tiers. Great find and love it so far.
r/supermicro • u/T_ro_se • Apr 24 '26
Picked up this combo from a trusted seller on eBay, but Iâm having no luck whatsoever getting VGA signal or any console view via IPMI.
CPU seems to POST, fans are on, and onboard LEDs give healthy green lights. (Yes I have the cooler torqued to the right settings)
Chat says the problem might that POST is stalling halfway through because of an AGESA issue before VGA-init can happen so I canât get console view at all.
Iâve tried the most recent BMC and BIOS versions. Iâve also tried versions 1.6 and still had the same problem.
I have compatible DRAM in slot A1.
Anyone ever dealt with a similar problem?
EDIT: It seems like people think Iâm testing the machine as it is in the picture⌠I have heat sink, RAM, power supply all installed lol
r/supermicro • u/Legal-Pop-1330 • Dec 30 '25
I felt the others I saw were too complicated for me or didnt quite work right for the H13 so I made this: https://github.com/jvdillon/supermicro-h13-linux
r/supermicro • u/morfi717 • Jun 10 '25
I'm so fed up with those subpar desktop motherboards, no matter if its a flagship of particular series or mid-range product, it all has exactly the same issues.
/rant-on (reading is optional)
The BIOS often lacks basic features â sometimes theyâre removed or added between boards with no explanation, and then show up again years later in some obscure patch. Fundamental things like a functioning âsearchâ option are either broken or missing entirely. Want to add a boot entry manually? Forget it.
And then thereâs the hardware. You get some ultra-premium, 0.00001â1000 terahertz, gold-plated onboard audio â except itâs not properly grounded, so you can literally hear your overclocked CPU whine in sync with your mouse movement. Or you get a Wi-Fi module with 20 antennas and theoretical speeds that make fiber blush, but the drivers are so garbage you end up using a $5 2.4GHz USB dongle that just works.
And of course, the IOMMU groups are a complete mess. Everything is shoved into two or three groups, so passing through a single USB controller means handing over your SATA, NVMe, and Ethernet too â because apparently isolating devices is just too much to ask in 2025.
Letâs not forget: RGB vomit in every corner with no kill switch, fan curves that ignore your thermal hysteresis settings, and firmware updates that brick more boards than they fix. And yet we still have "advanced" UEFI systems that crash if you leave a USB stick in during boot.
/rant-off
so.. dear supermicro users. Am I going to be satisfied with some board from supermicro or am I beyond being satisfied considering what hardware is available on the market today? I'd need sth for intel 14 and if I can be so picky I'd like to have as many pci gen4 nvme m2 slots as possible (or at least pci slots where i can plug m2 board). I dont need turbo OC, actually I can go with undervolting because I don't care that much about winning this benchmark contest.
r/supermicro • u/Shypaxi • Oct 08 '26
r/supermicro • u/DefinitelyNotWendi • Jun 23 '25
I cannot figure out why this x10 build is doing this. Near I can tell it is just in a reboot cycle.
r/supermicro • u/Classic-Difficulty32 • Sep 09 '23
Setting up a new X13SAZ-F. Nice board, but trying to set the fan speed is driving me nuts.
I have all Noctua fans. 2 chassis and 1 CPU. At first they were all ramping up and down. I tried setting new thresholds and no matter what I put in there, they appear to be pegged at 100%. 2 of them also show as "critical" in the health state - I'm assuming because the actual RPM is pegged over the upper thresholds.
As far as I can find, there doesn't appear to be any fan control options in the BIOS, so I don't believe that I'm playing tug-of-war between the BMC and the BIOS.
Fan specs per Noctua:
FAN1 - 400 (+/- 20%), 2000 (+/- 10%)
FAN4 - 450 (+/- 20%), 2200 (+/- 10%)
FANA - 300 (+/- 20%), 1200 (+/- 10%)
I believe I'm using the IPMI command correctly: For example:
ipmitool -I lanplus -H 172.16.2.20 -U xxx -P yyy sensor thresh "FAN1" lower 100 200 300
ipmitool -I lanplus -H 172.16.2.20 -U xxx -P yyy sensor thresh "FAN1" upper 1600 1700 1800
Status is currently showing:
FAN1 - 1960 RPM (OK)
FAN4 - 2100 RPM (critical)
FANA - 1120 RPM (critical)
Can anyone help me with what to put in here?
I'm doing something wrong, but have no idea what so far...
r/supermicro • u/mdinisoae • Mar 09 '26
For many years I was well impressed by the technical capabilities, functionalities of SuperMicro motherboards, as well with their support (e.g. based on a hardware compatibility issue reported by me in the first year after MB came on sale, a new BIOS version was released)....and I would like to highlight that behind of those achievements were professional people.
Unfortunately, in the last year I discover the quality of their support became poor and with my recent experience, the test effort to the new firmware & drivers has decreased. In fact this is an approach that many "software" companies adopted long time ago -> let customer face the issue (translated into an outage) and if it is reported, we will fix it ....but not having the issue reported by a "small customer", should be reported by a large Customer/Integrator....and if this happen, customer's engineers should escalate internally till it will reach the CEO level, let the CEOs have a phone conversation as most of them are on a speed dial, and then the CEO send a directive to the Dev team and expediate a fix. If by chance you are working for or cooperate with a small customer/integrator where their CEO doesn't have the Software/HW CEO on speed dial, bad luck.
Back to the issue, working on a upgrade project for one of my customers I wanted to ensure that all drivers and firmware versions are in place prior starting the upgrade process. For few years I noticed that SuperMicro stop providing BIOS updates for H11DSI-NT hw v1.01 (as I own one); starting with the initial BIOS released in 2017 followed by another 2 versions on the same year; 5 BIOS versions released in 2018 and only 2 versions in 2019. Checking the BIOS release notes for the second hardware version of H11DSI-NT I noticed at least 1 new BIOS version released every year and the most important is the one that address security vulnerabilities for AMD Napples family - there are 104 security vulnerabilities CVE-20xx!!! (see the public release notes document).
I created a ticket to SuperMicro to assist me with new set of drivers, the customer support representative who assigned this one was very responsive and he directed me to SuperMicro repository from where I downloaded the latest ISO image, but there is no updated BIOS version for H11DSI-NT hw v1.01. (prior to this step I've created a case with AMD to assist with new drivers as the latest drivers found on Supermicro portal for H11DSI-NT were dated 2021 => AMD directed me to the Supermicro as they are the chipset integrator).
I created a separate case to receive a new BIOS version that covers at least the security vulnerabilities released in the latest BIOS version for hw 2.0 and I received a "cold" answer : "We are sorry but your MBD is revision 1.01 and there is no more follow up for new Bios , only for MBD revision 2.00 and above , see below link for information" being aware of the BIOS memory capacity difference.
Following up on the same as this motherboard support AMD 7001 series and for security point of view I will like to have a BIOS version that cover all 104 security bulletins, the reply was like an ended "conversation":
"Sorry but as TS there is nothing we can do, it has been a decision from our MBD PM to not support any longer the MBD revision 1.01 with new bios"
...and to address the issue to my Supermicro supplier that can make this request on your behalf, of course, supporting the cost for development.
Â
What is wrong with this company? or it is a personnel issue? Anybody else experienced similar issue with Supermicro?
r/supermicro • u/Free-Championship844 • Dec 01 '25
Hello everyone, I have a H14SSL-NT that no matter what i do will not post, I have tried barebones all the way to full populated,
I have had A1 populated with Samsung M321R8GA0PB0-CWMXJ 64GB DDR5 ECC RDIMM
i have 8 on the same Ram sticks, right now all populated in the photo
but i have had it to only one dimm one cpu ( EYPC 9124) and power supply but it still will not post
I am in the BMC and i see post snooping at 0022
I did this with all my ram sticks thinking maybe only one maybe bad but it is the same case with all of them
then someone told me that 9124 is duel channel so i populated A1, G1 with the same setup to see if it would post and cycled between the RAM and still same error code
also this is not the same motherboard i started with, i had initially started on a H13SSL-NT and it was not posting as well i even had a 9575F initially that i thought might not be compatible with the H13 even though it was REV 2.1, i even updated to latest BIOS and still same result
r/supermicro • u/mrcrashoverride • Nov 29 '25
So I know Supermicro makes a universal cable connector CBL-0084L to convert the lights and buttons on the case front to use the motherboard of your choosing.
What Iâm wondering though is the Supermicro pin out on their standard non-universal cable fairly standard to other manufacturers..??
I have a brand new Asrock Motherboard for an upcoming build. Itâs been a decade since I last built my own so Iâm wondering if this has become fairly universal pin out or it isnât thus the universal cable has to be usedâŚ?L
r/supermicro • u/entilza05 • Jun 25 '25
r/supermicro • u/welsh1lad • Oct 11 '24
This was eight years ago, 6 Tb drives where new , so was was the super micro 36 bay chassis. https://youtu.be/30nQfxXwAsQ?feature=shared now look at where we are with 1-6tb nvram and solid state drives . Oh this was running on Lsi raid controllers raid 10 if I remember . Core Os #ubuntu 12
r/supermicro • u/jsunjones • Sep 16 '24
I recently updated my unraid to an X13SAE-F and i7-14700 cpu. Everything went fine except the FANs ramp up and down. From my research it appears others have experienced this and performed ipmitool changes to fix it. I'm running 01.02.01 BMC and it appears this approach doesn't work with LOW NR is showing as N/A. I've re-flashed, reset, power cycled all to no avail.
I'm using Noctua fans, and I switched to some that have a minimum fan speed of 300 rpm and still no change.
So frustrating. this isn't a "server board", why can't I use regular fans. what does it actually expect spec wise? This is as an asinine problem to have. These fans worked fine with my X11 board.
Anybody have ideas?
r/supermicro • u/The_Great_Sephiroth • Aug 10 '24
I do IT for a living. I started in 1996. Needless to say, I have updated firmware and BIOS on systems millions of times. It's easy. Download the file, extract it, put it on a FAT32 USB stick, go into the BIOS, update. Simple, right?
SuperMicro has turned a trivial task into two days of downtime for a business I support. They have an older X10SLL-F system. They literally require DOS to update the BIOS. DOS. On a USB stick. DOS, that cannot see the stick it lives on once booted.
Tis started with an HDD to SSD upgrade and the decision to use RAID1 in Windows. This required an update to GPT disks. No biggy, the board supports UEFI and I enabled it in the BIOS, then did the conversion to GPT. Easy.
Now it won't boot. Why? After hours of digging, you need BIOS version 3 to actually USE UEFI. WTF? Why do I have UEFI options and an EFI shell without the ability to boot EFI systems?
Okay, I downloaded the update. Entered the BIOS and found no way to update. More reading. I need DOS on a USB. Made FreeDOS and DOS 7.1 USB sticks with both Rufus and Ventoy. Neither can see the USB stick with the BIOS update.
Enter nearly two days now of all kinds of attempts to boot and get the update installed. Placing it on the disks in the system fails due to it not seeing said disks. Placing it on the USB stick fails because DOS and USB mass storage don't mix.
Oh wait, IPMI! It never comes up and after researching, it requires a damn license to update over IPMI! What the hell? It ain't cheap either!
Why is this so expensive and difficult with SuperMicro? The hardware is solid but DAMN this is insane!
Does anybody know how to update the BIOS from the EFI shell or how to make a USB drive with DOS that works? I will NOT install random bloatware to make this one drive. I have ImgBurn, 7-Zip, Ventoy, and Rufus already.
r/supermicro • u/[deleted] • Jun 27 '24
No questions or problem reports here, just wanted to say "THANK YOU" to Supermicro for releasing the updated BIOS (2.0a) for H13SAE-MF which fixed the BIOS hang at "Initializing SuperIO" with 10Gbit NIC installed -- I'm using non-certified one, Broadcom 57416, but have seen several reports about the same problem with certified ones over the web. Hope this helps someone (I was reluctant to move everything back to this MB once I got the email about BIOS update, but it paid off).
r/supermicro • u/vdkjones • Feb 29 '24
I have an X13SCH-F motherboard running an Intel Xeon E-2434 CPU. The CPU fan is the stock Intel one and it's hooked to `FAN1`. There are three Arctic P14 PWM fans hooked to FAN2, FAN3, and FAN5.
The Arctic fans support very low RPMs, so the BMI on this board was causing the fans to "surge"âwhen the RPM fell too low, the board thought the fans had stopped so it sent everything to full-speed for to "recover". Once the fans spun up, the board allowed them to slow down again until the process repeated.
To solve this, I used ipmitool to edit the lower-critical fan threshold:
ipmitool sensor thresh FAN5 lower 0 100 0The only value that sticks is the "lower-critical" threshold, which is apparently capped at 140 (you can't go below that). The BMI reports errors when attempting to set *anything* for the other two values:
admin@TrueNAS[~]$ sudo ipmitool sensor thresh FAN5 lower 0 100 200
IANA PEN registry open failed: No such file or directory
Locating sensor record 'FAN5'...
Setting sensor "FAN5" Lower Non-Recoverable threshold to 0.000
Error setting threshold: Command illegal for specified sensor or record type
Setting sensor "FAN5" Lower Critical threshold to 100.000
Setting sensor "FAN5" Lower Non-Critical threshold to 200.000
Error setting threshold: Command illegal for specified sensor or record typeThis stops the fan surging, but the BMI UI shows the fans as "critical" even though their current RPM values are above the lower-critical threshold value:

I'd like to solve this so my BMI event log isn't littered with false warnings. What is the magic voodoo incantation to get supermico boards to play nice with modern fans?
(Note: I *did* try setting the fans to "full speed" so that the board isn't fighting me for control, but when I did so, the fans just ran at full-speed regardless of the limits I set with ipmitool.)
Is there a way to just kick the BMI out of this process altogether and set my own, custom fan curves? Supermicro's fan management leaves a LOT to be desired.
r/supermicro • u/Soggy_Hovercraft_185 • Sep 21 '23
I have trying to download the IPMI view software for a server that I have acquired used. I created an account on Supermicro's website, but whenever I click on the download button for the software, nothing happens. literally nothing. I can click that button over and over and the website does nothing. I have been pulling my hair out trying to figure out what I am doing wrong. Like I said, I am signed into my account, so I an not trying to download as a guest user.