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

[loic69]

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 ?

 

[SloothNZ]

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]

-----------------------------------------------------------------
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]

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]

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]

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]

Default as far as I know. I haven't touched any BIOS settings since having huge trouble on the earlier releases.

 

[MattRo]

Just checked - yeah 5200 MT/s:

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

 

[Lix]

1.25 running great here as well.

 

[anewsome]

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:

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:

Vendor	American Megatrends International, LLC.
Version	AHWSA.1.24
Release date	6/19/2024

 

[SloothNZ]

Still running fine 2+ weeks on, definitely an improvement with 1.26

Rock solid here for nearly a month, I feel the issue is likely resolved. If I experience any instability from here on I'll reply. Otherwise finally happy with my purchase!

root@pve:~# uname -r
6.8.12-2-pve
root@pve:~# uptime
19:14:07 up 27 days, 23:56, 1 user, load average: 0.92, 0.98, 1.30

 

[Matta]

I was wondering can MS-01 be connected via USB4 to some monitor that outputs 90W+ through type-C ? That way, with one cable be able to get power, audio and video ?
Office use, nothing heavy.

 

[MattRo]

root@pve1:~# uname -a
Linux pve1 6.8.12-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-1 (2024-08-05T16:17Z) x86_64 GNU/Linux
root@pve1:~# uptime
 13:22:16 up 53 days, 19:52,  1 user,  load average: 4.10, 4.05, 3.64

Getting towards 2 months of uptime now, so I think we can comfortably say the problem is resolved, and I'm still on the 1.25 beta BIOS (so as to not upset my uptime!).

Wanted to get a 2nd one of these for my Proxmox cluster to replace an old HPE DL20-gen9 but held off when it seemed unstable. Thinking I might have the confidence to spend more on these now!

Was hoping for a Black Friday discount on Amazon, but there's no joy there yet.

 

[creepingcat45]

upgraded to BIOS 1.26 27 days ago. no crashes since then (knock on wood). my longest run yet.



Crucial 64GB 5600MHz CT2K32G56C46S5
dual WD Black SN770 2TB in RAID1

 

[jpatriarca]

I had a kernel panic a couple of days in one of my machines, but havne't hanged my machine, related with memoery management in one of the VMs. It was a Proxmox and I could migrate what I had there to other machine a make a restart. Before 1.26 the machine would hang and I needed to power cycle it.
I have two machines, one have a 30+ days update. If it wasn't for the hiccup described above, the second machine would have the same uptime

 

[jars1]

Hello,

I'm writing to report a persistent issue with one of my MS-01 machines, specifically with segfault CPU-related error messages. Despite updating to BIOS 1.26, the machine continues to exhibit erratic behavior, including displaying error messages on dmesg, sudden shutdowns, and unresponsiveness to the keyboard and monitor. A reboot resolves the issue temporarily, but it's not a reliable solution. Notably, my other MS-01 unit does not experience this issue, even when running a different kernel version.

I've reached out to Minisforum multiple times via email (support@, contact@, and store@) to initiate the RMA process, but unfortunately, I have yet to receive a response. My concern is the lack of acknowledgment and the uncertain timeline for when I can expect a response from Minisforum. As a customer, it would be reassuring to know if Minisforum is actively working on RMA requests and if there's a standard timeframe for when I can expect a response.

 

[flapj4cks]

1.26 is available on their page: Minisforum Support

Their entire support system & pages are either under construction, incomplete, or non-functional.

I too have complete system halts about every 5-7 days that exhibit as a kernel panic.


Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

The panic originated in the do_exit function, a critical kernel routine for process termination.
A page fault occurred at the address 0x5e654361efa0, which is an invalid user-space memory address, suggesting memory corruption.

 

[AlexHK]

I am testing three Minisforum MS-01 (i5, i9-12, i9-13) in a Proxmox test setup. They are intended to replace my NUCs, which I have been running since Proxmox v5.

I noticed frequent hangs on the screen BIOS screen that says press <DEL> or <ESC> to enter setup (quite boot disabled). At that moment I need to power cycle, nothing else helps. After booting, it will just repeat and hang again. To get out of this, I have to actively press F7 during boot and manually select the boot drive (Proxmox). After that, on the next boot, it seems to work normally again.



I noticed that this hang seems to happen mostly when I first enter the BIOS setup screen. By now, I almost know I have to manually boot and press F7 or power cycle after being in the BIOS.

Sometimes, even after F7 and seeing the (BIOS) boot drives to choose from, it will just flash the screen black then return to the selection (won't boot).



Sometimes I also had a Boot Option Restoration screen, but I am not sure if this is part of the BIOS or Proxmox (I think it is because once I had that screen with more options).



I am wondering if it's actually the BIOS that is frozen at that point, or already GRUB boot loader etc (which is stuff I have no idea about) - I am using ext4 for my boot drive.

It might be completely unrelated to to Proxmox, but I had once or twice simply lost the drive (didn't show up anymore) but after installing over the same drive from USB stick worked again.

Does this sound like MS-01 headache or anything else familiar?

Drives:
#1: U.2 Samsung PM9A3 2.5" U.2 SSD (boot, ext4)
#2: M.2 Micron 7400
#3: M.2 Micron 7400

They are on BIOS v1.26.

I started with the Micron M.2's as boot drive, they exhibited the same behavior.

Edit 2025-01-14:
- It seems this was caused by the Micron 7400 2280 SSDs.
- Now that I replaced them with Samsung 983 the reported issue seems to be gone (been stable for a few days).

 

[timot]

Hello @AlexHK

I am wondering if it's actually the BIOS that is frozen at that point, or already GRUB boot loader etc (which is stuff I have no idea about) - I am using ext4 for my boot drive.

All the screenshots you provided are BIOS related and it's very likely that your problem doesn't come from GRUB or Proxmox.

While I'm unsure if what i encountered was the exact same behaviour, have you tried powering off, unplugging the power cord from the back of the MS-01, wait a few seconds and re-plug & reboot ? (In these cases, I usually press the power button while unplugged, to 'purge the capacitors', no idea if it's still useful but it's a harmless old habit).

Since i did that (and tried to boot directly or maybe checked BIOS boot configuration before), i can reboot my nodes without this boot loop bug thing happening.

Hope it's the same for you.

 

[AlexHK]

All the screenshots you provided are BIOS related and it's very likely that your problem doesn't come from GRUB or Proxmox.

Don't ask me how and why, but I now believe the problem was caused by the Micron 7400 M.2 NVMe drives.

I replaced them with other drives and the problem seems to be gone, at least I hope so.

Now using Samsung PM983 M.2 22110. The Micron's where luckily only temporary anyway for staging and while waiting for the larger PM983.

It has been a few days without the issues reported. I tested a ceph setup for a day or two, then ZFS with replication in a new setup.