BMC FW via BMC don't worked.Dm
Damn I need to wait for something else again I'm considering just updating the BIOS via IPMI at this point so annoying![]()
but
I used BMC to flash it and it was fine. I have an OVH board.
BMC FW via BMC don't worked.Dm
Damn I need to wait for something else again I'm considering just updating the BIOS via IPMI at this point so annoying![]()
I used BMC to flash it and it was fine. I have an OVH board.
I believe they were referring to updating the BMC firmware using the the beta version on the product pageBMC FW via BMC don't worked.

correct in earlier post, but later he sayd BIOS 5.05 via BMC workedI believe they were referring to updating the BMC firmware using the the

Catching up on this thread since I purchased the same E3C252D4U-2T/OVH motherboard (and bought a xeon e-2314 at the same time). I had the same webui password issues and had to use a Linux Live backdoor to reset the BMC passwords, but everything posted fine eventually.View attachment 48206
Update was successful, now trying to boot with G6400, if successful, will try to boot with E-2324G again.
Seems to work fine with G6400. Replacing CPU with E-2324G now.
E-2324G doesn't POST with non-ECC memory. Trying again with ECC memory. Still not posting.
I guess it's a CPU defect. Damn it. I should've known the deal 20€ for a E-2324G was too good to be true - though the G6400 for 10€ came from the same seller, yet it's functional.
BIOSCan you point me to them? See the BIOS file in your image but not BMC...did you update it too in the web ui?
Nice job with the Linux Live backdoor thingy, do you have any resource I could read up on that?Catching up on this thread since I purchased the same E3C252D4U-2T/OVH motherboard (and bought a xeon e-2314 at the same time). I had the same webui password issues and had to use a Linux Live backdoor to reset the BMC passwords, but everything posted fine eventually.
Currently running similarly old versions of BIOS (1.21.OV01) and BMC (1.09.00) with Microcode 00000044. Reached out to ASRock Rack for recent BIOS .ROM file and BMC .ima file, but it sounds like you already received those files. Can you point me to them? See the BIOS file in your image but not BMC...did you update it too in the web ui? Not sure if I need to change anything in the files - newish to this.
It will reset BMC settings. I used it to reset the password initially but BMC itself is the same.I will try what @MSameer had posted about resetting BMC from BIOS (though not sure if resetting would just set it to the original OVH version of it, let's see)


Thank you for the heads up. I could spin up a bluetooth keyboard and vga monitor but I'm not sure if it will be what @randomusername1 would be expecting to achieve.It will reset BMC settings. I used it to reset the password initially but BMC itself is the same.
DO NOT try it if you do NOT have a keyboard and monitor attached to the board. You WILL LOSE ACCESS.
It's not that. It's from the BIOS. I can attach a screenshot later as I have the board offline now.Not sure if this is what @MSameer meant when they said "Load default bmc settings" in Step 2 of their comment
I got there vıa Maıntenance > Reset
View attachment 48239
View attachment 48240
sudo apt update
sudo apt install ipmitool -y
sudo modprobe ipmi_msghandler
sudo modprobe ipmi_devintf
sudo modprobe ipmi_si
sudo ipmitool user list 1
sudo ipmitool user set password 2 <new_password>
I remember now, why I didn't go this route. It was becasue the board wasn't posting so I couldn't boot up anything anyway.@MSameer @TransistorResultConsumer
1. Did either of you find that the BMC sensor information changed after restarts or FW updates? Lots of sensors with no information in the web interface and I can't tell if it's because the motherboard lacks sensors, I need to somehow activate the sensors (there are many pins on the board that appear to be sensor-related that I've completely ignored), or it's a BIOS or BMC firmware issue (and perhaps the updated FW populates more of the information).
2. The BIOS has a "reset to default" option you can select. It resets some things but it does not appear to reset the login/password for the BMC. If it does, it resets it to some login/password option I didn't try. I tried most combinations of admin, ADMIN, Admin, Administrator, admin123, etc. with no success. You can easily view the BIOS by plugging in a monitor (easiest with a native VGA monitor and a VGA-to-VGA cable) and keyboard, powering on your PSU and shorting the power pins. I didn't find resetting CMOS etc. mattered but did it before all of the steps below that led to success.
3. The BMC web ui also has a "reset to default" option you can select. I believe this resets passwords to defaults. However, (a) using this option requires you to be able to log into the web ui (which would not be possible if you didn't already know the password!) and (b) I am not 100% certain of this because I just instead used the Linux Live approach below to set the passwords.
4. Below is the Linux Live approach to resetting the BMC password, courtesy of Gemini.
# LINUX LIVE APPROACH
This approach is essentially a "backdoor" into your motherboard's management system. Since you have physical access to the hardware, you can use the operating system to talk directly to the BMC (Baseboard Management Controller) chip over the motherboard's internal data bus (the KCS interface). This bypasses the need for a network connection, a browser, or knowing the current password. The BMC is a separate computer-on-a-chip (that ASPEED chip you can see in your motherboard photo). While it usually guards itself behind a login screen over the network, it is designed to trust the "Host" (your CPU/OS) by default. By running ipmitool directly on the machine, you are acting as the "root" owner, and the BMC will obey the command to change its own password without asking for the old one.
1. What you’ll need
2. The Step-by-Step Process
- A spare USB flash drive (8GB or larger).
- A tool like Rufus or BalenaEtcher to "burn" the ISO to the drive.
- A Linux ISO (I recommend Ubuntu Desktop because it’s user-friendly, or SystemRescue because it’s lightweight).
Step A: Create the Bootable USB
Download the Ubuntu ISO and use Rufus to flash it onto your USB drive. This creates a "Live" environment that runs entirely off the USB and won't touch your SSD.
Step B: Boot the Server from USB
Step C: The Linux Commands
- Plug the USB into one of the blue ports on the back of your motherboard.
- Restart the server and tap F11 (usually the Boot Menu key for ASRock/AMI) or enter the BIOS.
- Select the USB Partition 1 as the boot device.
- When prompted, choose "Try Ubuntu" (do NOT click Install).
Once you are at the Linux desktop, you need to open a Terminal (Ctrl+Alt+T) and run these commands.
1. Install the Tool: First, connect the server's main LAN port (not the IPMI port) to your internet source temporarily, or use a WiFi dongle if you have one, to grab the utility:
2. Load the Drivers: Tell Linux to talk to the motherboard's management chip:Code:sudo apt update sudo apt install ipmitool -y
3. Find the Admin User: Check which user ID is the administrator (usually it's ID #2):Code:sudo modprobe ipmi_msghandler sudo modprobe ipmi_devintf sudo modprobe ipmi_si
4. Reset the Password: Replace <new_password> with whatever you want your new password to be (keep it under 16 characters):Code:sudo ipmitool user list 1
Code:sudo ipmitool user set password 2 <new_password>
- It's for a home SFF NAS (sagittarius nas case) with 8 HDDs in raidz2 on baremetal Debian w/ zfs + cockpit etc.I remember now, why I didn't go this route. It was becasue the board wasn't posting so I couldn't boot up anything anyway.
Thank you nonetheless for the guide.
If you don't mind me asking. What is your plan with this mainboard/cpu combination? What are you going to use it for?
Misc: I've learned that for the future I'd want to utilize the onboard SATA connections to save power (no HBA card) and therefore use SATA drives instead of SAS.
I've also realized that even though the board has 2x 10GbE onboard, I'm not sure if it would've been better power consumption wise to have bought a network card that can do SFP+ and some other cable that uses less energy (not sure about this either yet because I don't know about them enough yet, still adding it as food for thought because I picked it up somewhere)
This. You'll need 2 SFP+ LAN ports on your switch if you want to go NAS <-> SWITCH <-> COMPUTE and SFP+ ports on both the NAS and COMPUTE. You could instead use NAS <-> COMPUTE but you'll need to set up inter-VLAN routing ideally (need a L3 managed switch for that), SFP+ ports on both NAS and COMPUTE, and will need to use a different cable to the switch for other network connections.You may save a few watts by going for SFP+, and a low power NIC (so maybe not an Intel X520).
BUT if you have a 10GBase-T NIC onboard, a short Cat. 6a/7 cable to the switch just works… and keeps a PCIe slot free, which may be very relevant for a small NAS. Simplicity is good too.
And then make sure you have the right mix of ports in your switch—which may mean picking up the right switch in the first place.
*cough* Fractal Design Define 7 *cough* small NAS * cough*You may save a few watts by going for SFP+, and a low power NIC (so maybe not an Intel X520).
BUT if you have a 10GBase-T NIC onboard, a short Cat. 6a/7 cable to the switch just works… and keeps a PCIe slot free, which may be very relevant for a small NAS. Simplicity is good too.
I'm sorry for all the *cough*ing but... I don't have a 10GbE switch yet.. Everything is either connected to the routers ports or a small 5 port Netgear GS105And then make sure you have the right mix of ports in your switch—which may mean picking up the right switch in the first place.