Minisforum MS-01 PCIe Card and RAM Compatibility Thread

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

DataX

New Member
Jun 16, 2023
9
14
3
I've been running the 13900H with the 2x48G Crucial kit at 5200MT/s and so far so good. I've had a few load related crashes which may have been due to the E-cores, but nothing that would indicate memory instability.

I would agree with the other comment, try re-seating or swapping the DIMMs around, and test each one individually. You could also unplug AC and fully drain power from the system between tests, might help ensure memory retrains.

Code: 
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.5.0 present.

Handle 0x0027, DMI type 16, 23 bytes
Physical Memory Array
        Location: System Board Or Motherboard
        Use: System Memory
        Error Correction Type: None
        Maximum Capacity: 64 GB
        Error Information Handle: Not Provided
        Number Of Devices: 2

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

nicoska

Member
Feb 8, 2023
67
11
8
00riddler said:
Get the memtest from Memtest86+ | The Open-Source Memory Testing Tool as ISO and put it on a bootable USB drive with rufus or some other tool.
It will automatically scan the whole memory.
Click to expand...
So I did a full Memtest86+ (10 tests) and found no errors:
1708381425686.png

After the test I swapped the modules.

Now will continue to monitor the situation and let everyone know.
I'd really like to keep the current 96GB other than downgrade to 48GB

Thank you to everybody for the suggestions.
Nico

[EDIT]
After a little bit more testing, I'm able to reproduce the issue: Every time I try to RUN the Windows 11 VM it will restart itself. Maybe the issue is not correlated to the memory error I was getting. This is the log:


Code: 
Feb 19 23:45:58 nicoska2 kernel: vmbr0: port 7(veth106i0) entered disabled state
Feb 19 23:45:58 nicoska2 kernel: vmbr0: port 7(veth106i0) entered disabled state
Feb 19 23:45:58 nicoska2 kernel: veth106i0 (unregistering): left allmulticast mode
Feb 19 23:45:58 nicoska2 kernel: veth106i0 (unregistering): left promiscuous mode
Feb 19 23:45:58 nicoska2 kernel: vmbr0: port 7(veth106i0) entered disabled state
Feb 19 23:45:58 nicoska2 audit[29954]: AVC apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-106_</var/lib/lxc>" pid=29954 comm="apparmor_parser"
Feb 19 23:45:58 nicoska2 kernel: audit: type=1400 audit(1708382758.447:74): apparmor="STATUS" operation="profile_remove" profile="/usr/bin/lxc-start" name="lxc-106_</var/lib/lxc>" pid=29954 comm="apparmor_parser"
Feb 19 23:45:58 nicoska2 kernel: EXT4-fs (dm-11): unmounting filesystem fd237a8e-f4aa-49a7-97b0-c7123fb0c218.
Feb 19 23:45:58 nicoska2 systemd[1]: pve-container@106.service: Deactivated successfully.
Feb 19 23:45:58 nicoska2 systemd[1]: Stopped pve-container@106.service - PVE LXC Container: 106.
Feb 19 23:45:58 nicoska2 systemd[1]: Started pve-container@106.service - PVE LXC Container: 106.
Feb 19 23:45:59 nicoska2 kernel: EXT4-fs (dm-11): mounted filesystem fd237a8e-f4aa-49a7-97b0-c7123fb0c218 r/w with ordered data mode. Quota mode: none.
Feb 19 23:45:59 nicoska2 audit[29981]: AVC apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-106_</var/lib/lxc>" pid=29981 comm="apparmor_parser"
Feb 19 23:45:59 nicoska2 kernel: audit: type=1400 audit(1708382759.415:75): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-106_</var/lib/lxc>" pid=29981 comm="apparmor_parser"
Feb 19 23:45:59 nicoska2 kernel: vmbr0: port 7(veth106i0) entered blocking state
Feb 19 23:45:59 nicoska2 kernel: vmbr0: port 7(veth106i0) entered disabled state
Feb 19 23:45:59 nicoska2 kernel: veth106i0: entered allmulticast mode
Feb 19 23:45:59 nicoska2 kernel: veth106i0: entered promiscuous mode
Feb 19 23:45:59 nicoska2 kernel: eth0: renamed from vethiNJGQT
Feb 19 23:45:59 nicoska2 kernel: vmbr0: port 7(veth106i0) entered blocking state
Feb 19 23:45:59 nicoska2 kernel: vmbr0: port 7(veth106i0) entered forwarding state
Feb 19 23:46:01 nicoska2 kernel: nfs: Deprecated parameter 'intr'
Feb 19 23:46:03 nicoska2 pvedaemon[1951]: <root@pam> successful auth for user 'root@pam'
Feb 19 23:46:06 nicoska2 pvestatd[1921]: modified cpu set for lxc/106: 1-10,12-13,15-16,18-19
Feb 19 23:53:01 nicoska2 pvedaemon[1953]: <root@pam> successful auth for user 'root@pam'
-- Reboot --
 
Last edited:
F

FingerBlaster

Active Member
Feb 27, 2019
101
47
28
i've got 2 of my 3 systems in hand from amazon. my early bird pre-order from minisforum direct is nowhere to be found. I have 1 with the crucial 96gb memory kit and the other with the mushkin redline 96gb kit. I can confirm that the mushkin kit works too. I just completed memtest86+ on both systems. the mushkin kit does have slightly better timings.
 
H

homelabenthusiast

Member
Feb 19, 2024
31
40
18
nicoska said:
Nope, same problem. System hung himself. This was the error I was able to grab:
View attachment 34789

Do you think it's a memory problem or more serious a CPU?
Thank you
Nico
Click to expand...
I also have MS-01(13900H) running proxmox with 96GB memory from crucial like yours (just not kit bought 2 48GB separately because it was cheaper) and i also have the same problem but my server behaves normally. I do not experience random reboots or anything. I just see the errors. I tried memtest86+, tried unplugging external devices and I tried running single ram (tried each ram) and not running any vm at all. But i still see the errors still. I also tried updaating and dowgrading the kernel but it made it just worse! Like i saw Memory failure every second! That was teribble! Running kernel 5.15.136-1-pve i see the error only every minute. Maybe someone else can help? For me it would be enough to see any reponse that you are running MS-01 with 96GB crucial and it is working without the hardware or memory error. I also want to know if you are seeing the errors. Just want to know exactly if this is normal behavior or not. I would be really happy for any help. :) I see this:

1708417491282.png
 
Last edited:
S

skipper ohms

Member
Jan 24, 2024
35
26
18
nicoska said:
After a little bit more testing, I'm able to reproduce the issue: Every time I try to RUN the Windows 11 VM it will restart itself. Maybe the issue is not correlated to the memory error I was getting. This is the log:
Click to expand...
Things I would try:

1) Try power limiting the CPU. Mini PC PSU bricks are often underpowered.

2) If you have TLP try:
Code: 
RUNTIME_PM_ON_AC="on"
RUNTIME_PM_ON_BAT="on"
3) Try latest Linux 6 kernel. General guideline is kernel release date should be after CPU release date, especially for mobile CPUs.
 
  • Like
Reactions: nicoska
N

nicoska

Member
Feb 8, 2023
67
11
8
skipper ohms said:
Things I would try:

1) Try power limiting the CPU. Mini PC PSU bricks are often underpowered.

2) If you have TLP try:
Code: 
RUNTIME_PM_ON_AC="on"
RUNTIME_PM_ON_BAT="on"
3) Try latest Linux 6 kernel. General guideline is kernel release date should be after CPU release date, especially for mobile CPUs.
Click to expand...
This evening I'll try those tests. About TLP, where should I insert those flag?

About the kernel, I believe I'm running the latest: uname -r output:

6.5.11-8-pve

Btw, another random reboot this morning, without any VMs trigger, here is the latest log:

Code: 
Feb 20 09:17:01 nicoska2 CRON[281696]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 20 09:17:01 nicoska2 CRON[281697]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Feb 20 09:17:01 nicoska2 CRON[281696]: pam_unix(cron:session): session closed for user root
Feb 20 09:18:58 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 20 09:21:37 nicoska2 pvedaemon[1935]: <root@pam> successful auth for user 'root@pam'
Feb 20 09:25:11 nicoska2 pveproxy[249943]: worker exit
Feb 20 09:25:11 nicoska2 pveproxy[1949]: worker 249943 finished
Feb 20 09:25:11 nicoska2 pveproxy[1949]: starting 1 worker(s)
Feb 20 09:25:11 nicoska2 pveproxy[1949]: worker 287436 started
Feb 20 09:31:54 nicoska2 pveproxy[266452]: worker exit
Feb 20 09:31:54 nicoska2 pveproxy[1949]: worker 266452 finished
Feb 20 09:31:54 nicoska2 pveproxy[1949]: starting 1 worker(s)
Feb 20 09:31:54 nicoska2 pveproxy[1949]: worker 291984 started
Feb 20 09:34:01 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 20 09:34:03 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 20 09:34:15 nicoska2 kernel: RAS: Soft-offlining pfn: 0x10b3e10
Feb 20 09:34:15 nicoska2 kernel: Memory failure: 0x10b3e10: unhandlable page.
-- Reboot --
 
H

homelabenthusiast

Member
Feb 19, 2024
31
40
18
nicoska said:
After a couple of testing ( i9-13900H - 96 GB RAM - 1 NVME SSD - SFP+ Ehternet module - Proxmox 8.1.4) I'm keep getting those errors and the system itself reboot:

Code: 
Feb 19 12:25:46 nicoska2 kernel: RAS: Soft-offlining pfn: 0xb2c66e
Feb 19 12:25:46 nicoska2 kernel: RAS: Soft-offlining pfn: 0x10e2a5b
Feb 19 12:25:46 nicoska2 kernel: Memory failure: 0x10e2a5b: unhandlable page.
...
...
Feb 19 12:26:51 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 19 12:26:51 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 19 12:26:51 nicoska2 kernel: Memory failure: 0x10e1bdf: unhandlable page.
Feb 19 12:26:59 nicoska2 kernel: mce: CMCI storm detected: switching to poll mode
Feb 19 12:26:59 nicoska2 kernel: RAS: Soft-offlining pfn: 0x10e1b32
Feb 19 12:26:59 nicoska2 kernel: RAS: Soft-offlining pfn: 0x10209d
Feb 19 12:26:59 nicoska2 kernel: RAS: Soft-offlining pfn: 0x942368
Feb 19 12:26:59 nicoska2 kernel: Memory failure: 0x10e1b32: unhandlable page.
Feb 19 12:26:59 nicoska2 kernel: Memory failure: 0x10209d: unhandlable page.
Feb 19 12:28:12 nicoska2 kernel: mce_notify_irq: 27 callbacks suppressed
Feb 19 12:28:12 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 19 12:28:20 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 19 12:29:57 nicoska2 kernel: mce_notify_irq: 2 callbacks suppressed
Feb 19 12:29:57 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 19 12:29:57 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 19 12:31:03 nicoska2 kernel: mce_notify_irq: 1 callbacks suppressed
Feb 19 12:31:03 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 19 12:31:32 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 19 12:31:42 nicoska2 kernel: RAS: Soft-offlining pfn: 0x10e1b37
Feb 19 12:31:42 nicoska2 kernel: Memory failure: 0x10e1b37: unhandlable page.
Feb 19 12:32:49 nicoska2 kernel: mce_notify_irq: 1 callbacks suppressed
Feb 19 12:32:49 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
Feb 19 12:32:51 nicoska2 kernel: mce: [Hardware Error]: Machine check events logged
-- Reboot -
Those are the additional hardware I put inside:

  • Lexar NQ790 2 TB PCIe 4.0 SSD Interno, M.2 2280 PCIe Gen4x4 NVMe 1.4
  • Crucial RAM 96GB Kit (2x48GB) DDR5 5600MHz
  • 1/2.5/5/10Gb SFP+ RJ45 Transceiver

Any idea? Doing a google search resulted in two different discussions where the poster said it was a faulty CPU. I'm e little bit scared :/

Thank you for your help
Nico
Click to expand...


maybe the reboot is caused by

  • 1/2.5/5/10Gb SFP+ RJ45 Transceiver
I only see the errors but no reboots on mine
 
  • Like
Reactions: bakhtar
B

BlueChris

Active Member
Jul 18, 2021
156
60
28
54
Athens-Greece
Just recieved a reply from Minisforum in germany with a sorry and a tracking number from DHL, offcourse DHL hasn't got the machine in hands yet but you can call that a progress at least :)
 
T

Tsatsar

New Member
Nov 12, 2023
11
6
3
  • Like
Reactions: nicoska, homelabenthusiast and BlueChris
H

homelabenthusiast

Member
Feb 19, 2024
31
40
18
Last edited:
S

stich86

Member
May 24, 2023
40
14
8
has anyone able to enable AMT? i've put password on the bios, the IP is reacable, but port 16992 doesn't respond
@JaxJiang any advice? thx
 
Last edited:
You must log in or register to reply here.
Top Bottom