Minisforum ms-01 i9-13900H 96GB with Proxmox

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

loic69

New Member
Oct 25, 2024
4
0
1
Hi all
Which is the last microcode ?
I switched firmaware from 1.24 to 1.26
and install microcode from 0x426 to 0x4122
64 Go RAM with no crash since few month (outside network, see below)

Is the microcode update the Intel network microcode chipset ?
Or is it just the CPU microcode ?
When the network disconnected on my 2.5G ethernet port, the MS-01 reboot or the network interface not up...
I have the same behaviour before updates (BIOS 1.22 and base microcode 0x426)

Were can we found network microcode ?
 
Last edited:

SloothNZ

New Member
May 4, 2024
5
1
3
Thanks for the link, I have the usual configuration of an i9-13900H with 96GB of Crucial RAM running Proxmox 8.2.2. I've been having extremely consistent/ predictable crashes with approximately 7 days of uptime with workloads consisting of onboard graphics SR-VIO (GitHub - strongtz/i915-sriov-dkms: dkms module of Linux i915 driver with SR-IOV support) enabled on a single windows 11 virtual machine (completely idle). If I leave this virtual machine powered down, I'll get 14 days of uptime before reliably crashing. This has been observed over the last few months.

I've now updated to 1.26 from 1.22, I'll reply with my experience each week.
One week on, no crashes with 1.26 (default crutical ram speeds, I didnt modify any bios settings). I'd only been able to achieve this a couple times over the last few months so fingers crossed it continues.
 

EHRETic

New Member
May 16, 2024
4
1
3
-----------------------------------------------------------------
Release Date:
2024/04/12

BIOS Version:
1.23

BIOS Checksum:
B8D0

BIOS Description:
1. Correcting temperature display anomalies
I'm wondering if this correction would not be part of the solution for a few systems... Doesn't the CPU shut down if it reaches a certain temperature?
Just a guess :)

I'll try to install 1.26 over 1.22 but for me, I didn't experience crashes since a while.
Almalinux probably did update a few things, including microcode since my first post.
 

SloothNZ

New Member
May 4, 2024
5
1
3
One week on, no crashes with 1.26 (default crutical ram speeds, I didnt modify any bios settings). I'd only been able to achieve this a couple times over the last few months so fingers crossed it continues.
Still running fine 2+ weeks on, definitely an improvement with 1.26
 

MattRo

New Member
Aug 27, 2024
5
0
1
Another positive reliability report for 1.25 Beta (so far!)... 15 days!

MS-01 i9-13900H with Crucial 96GB Kit CT2K48G56C46S5
Proxmox 8.2.4
microcode : 0x4121

# uptime
18:32:45 up 15 days, 2 min, 1 user, load average: 2.97, 3.05, 3.08

Previously I *might* have had runs this long, but most were far shorter. I've increased the workload a bit over the last week so as to not give it an easy time, so things are looking good. I implemented Proxmox Backup Server at some point after getting the MS--01 and I think my reliability dropped to its worst point after that, likely due to the heavy backup load overnight. This is still running every night right now.
The success continues:

# uptime
10:12:41 up 33 days, 16:42, 2 users, load average: 4.45, 4.16, 3.79

So I've managed over a month now on 1.25 beta still and have increased the Proxmox workload through this time. Seems stable to me.
 

alex501

New Member
May 22, 2024
8
0
1
The success continues:

# uptime
10:12:41 up 33 days, 16:42, 2 users, load average: 4.45, 4.16, 3.79

So I've managed over a month now on 1.25 beta still and have increased the Proxmox workload through this time. Seems stable to me.
memory frequency lowered or 5200 by default ?
 

MattRo

New Member
Aug 27, 2024
5
0
1
Default as far as I know. I haven't touched any BIOS settings since having huge trouble on the earlier releases.
 

MattRo

New Member
Aug 27, 2024
5
0
1
Just checked - yeah 5200 MT/s:

Code:
root@pve1:~# dmidecode --type 17
# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.5.0 present.

Handle 0x0028, DMI type 17, 92 bytes
Memory Device
    Array Handle: 0x0027
    Error Information Handle: Not Provided
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 48 GB
    Form Factor: SODIMM
    Set: None
    Locator: Controller0-ChannelA-DIMM0
    Bank Locator: BANK 0
    Type: DDR5
    Type Detail: Synchronous
    Speed: 5600 MT/s
    Manufacturer: Crucial Technology
    Serial Number: E9486F7B
    Asset Tag: 9876543210
    Part Number: CT48G56C46S5.M16B1
    Rank: 2
    Configured Memory Speed: 5200 MT/s
    Minimum Voltage: 1.1 V
    Maximum Voltage: 1.1 V
    Configured Voltage: 1.1 V
    Memory Technology: DRAM
    Memory Operating Mode Capability: Volatile memory
    Firmware Version: Not Specified
    Module Manufacturer ID: Bank 6, Hex 0x9B
    Module Product ID: Unknown
    Memory Subsystem Controller Manufacturer ID: Unknown
    Memory Subsystem Controller Product ID: Unknown
    Non-Volatile Size: None
    Volatile Size: 48 GB
    Cache Size: None
    Logical Size: None

Handle 0x0029, DMI type 17, 92 bytes
Memory Device
    Array Handle: 0x0027
    Error Information Handle: Not Provided
    Total Width: 64 bits
    Data Width: 64 bits
    Size: 48 GB
    Form Factor: SODIMM
    Set: None
    Locator: Controller1-ChannelA-DIMM0
    Bank Locator: BANK 0
    Type: DDR5
    Type Detail: Synchronous
    Speed: 5600 MT/s
    Manufacturer: Crucial Technology
    Serial Number: E9487593
    Asset Tag: 9876543210
    Part Number: CT48G56C46S5.M16B1
    Rank: 2
    Configured Memory Speed: 5200 MT/s
    Minimum Voltage: 1.1 V
    Maximum Voltage: 1.1 V
    Configured Voltage: 1.1 V
    Memory Technology: DRAM
    Memory Operating Mode Capability: Volatile memory
    Firmware Version: Not Specified
    Module Manufacturer ID: Bank 6, Hex 0x9B
    Module Product ID: Unknown
    Memory Subsystem Controller Manufacturer ID: Unknown
    Memory Subsystem Controller Product ID: Unknown
    Non-Volatile Size: None
    Volatile Size: 48 GB
    Cache Size: None
    Logical Size: None
 

anewsome

Active Member
Mar 15, 2024
121
122
43
I won't be applying 1.26 until one of my nodes crashes. Right now 1.24 has been applied across the cluster. I've only seen 2 crashes with 1.24 and they were before the 1.26 was available. Both crashed nodes have been up 50+ days now. On the next crash, I'll apply 1.26. Here's the uptime report for now:

Code:
06:46:55 up 52 days, 15:31,  2 users,  load average: 2.51, 2.57, 2.74
06:46:55 up 54 days, 4 min,  0 user,  load average: 0.97, 1.22, 1.16
06:46:55 up 77 days, 2 min,  0 user,  load average: 0.50, 0.41, 0.48
06:46:55 up 77 days, 2 min,  0 user,  load average: 0.37, 0.37, 0.42
06:46:56 up 77 days, 2 min,  0 user,  load average: 2.01, 1.91, 1.79
BIOS:

VendorAmerican Megatrends International, LLC.
VersionAHWSA.1.24
Release date6/19/2024