Minisforum ms-01 i9-13900H 96GB with Proxmox
- Thread starter homelabenthusiast
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
Any update after another week? I'm at the tipping point of returning this machine if 1.25 doesn't resolve the issue. I requested access to the GDrive but it hasn't been approved after 2 days.
Same here, I have 4x MS-01 i9-13900H running Proxmox on 96GB Crucial on BIOS v1.22 and they have been pretty unstable. One of the instance is able to go for 5 to 10 days, but the other three froze every few days. @JaxJiang I would like to test the 1.25 BIOS to see if it is providing better stability. All instances are running the latest microcode.
So I'm running the 1.25 firmware and it seems stable.
However, the latest revision (revision2) of 1.25 disables all power modes like C states etc, I re-enabled the C states to keep the CPU not running at full peak as well as changed the CPU performance to max instead of max turbo.
Otherwise I was getting 85c+ on CPU and fans whirring
However, the latest revision (revision2) of 1.25 disables all power modes like C states etc, I re-enabled the C states to keep the CPU not running at full peak as well as changed the CPU performance to max instead of max turbo.
Otherwise I was getting 85c+ on CPU and fans whirring
I have successfully installed the BIOS version 1.25 and the MS-01 with the 96GB Crucial RAM has not crashed since then. However, I can no longer run virtual machines in Proxmox, it seems. If I do, the VM crashes after 15 minutes at the latest, the fans get extremely loud and only a shutdown of the VM helps. All LXC containers run without any problems, even in the crashed VM state. Could this have something to do with the BIOS? Have any of you noticed this? Now I am also a Proxmox beginner, which is not so helpful for troubleshooting.
I think you'll find it's overheating.
Go into the BIOS and re-enable the CPU C states. Also chnage thr CPU performance from Max turbo to just MAX (it's the middle option in the drop down list).
They have disabled all power saving functions and the cooling just can't keep up.
Let us know how you go?
I have reactivated CPU C-States, set the CPU to MAX (non Turbo) and throttled the RAM to 4400 MHz. Nevertheless, the Home Assistant VM hangs again after 19 minutes this time.
I can actually use Windows 11 as a VM, but the fans spin up enormously. It's frustrating that I can't even get Home Assistant VM to run (I've recreated the VM countless times)...
I can actually use Windows 11 as a VM, but the fans spin up enormously. It's frustrating that I can't even get Home Assistant VM to run (I've recreated the VM countless times)...
Were you able to figure out the issue ? Temperatures can be checked in the shell and I guess it is not related to temps.
The temperatures were not to blame, no. I don't really know what's going on and I haven't had time to do any in-depth research. But I was able to help myself by migrating the Home Assistant VM to another node (Intel NUC) in the cluster. I have 2 x MS-01 and 1 x Intel NUC in the cluster and now it works for the time being in that the MS-01 no longer has to deal with Home Assistant.
This is getting a bit frustrating.
I have been using so far ESXi-8.0U3-24022510 on my MS-01 with 13th gen CPU and I am getting, on an average, weekly PSODs.
Now, the idea was moving to Proxmox but I see there are a lot of issues here also.
I am starting to think buying this product was not the brightest idea.
Nevertheless, I will have to make the move to Proxmox and see what results I will get because for sure ESXi with this setup is not reliable anymore.
I have been using so far ESXi-8.0U3-24022510 on my MS-01 with 13th gen CPU and I am getting, on an average, weekly PSODs.
Now, the idea was moving to Proxmox but I see there are a lot of issues here also.
I am starting to think buying this product was not the brightest idea.
Nevertheless, I will have to make the move to Proxmox and see what results I will get because for sure ESXi with this setup is not reliable anymore.