I recently moved my Unraid from a Ryzen 5600g to an intel 14500 and ever since I have been having issues with it freezing up between 12-28 hours. The time frame is never exact but it doesn't seem capable of running for more than 48 hours.  The only thing that works is to hit the power button and initiate an unclean shutdown.  The last few days I happened to notice a single core (not the same one) red line at 100%. I do not know if that is the cause but it seems suspicious. I have attached my syslog and diagnostics. Can someone please help me, I only have 1 day left to start a return on some parts I bought. Thank you so much for you assistant

syslog-previous pleasedontbreak-diagnostics-20250329-2000.zip

Edited March 30, 20251 yr by jnosa899

There are constant call traces logged, I would recommend starting by running memtest.

I have run memtest 5 times and each time it passes. Before running the preboot memtest I installed the memtest docker container and that failed. Not sure why the more thorough test would pass and the janky container test would fail.

23 minutes ago, jnosa899 said:

I have run memtest 5 times and each time it passes. Before running the preboot memtest I installed the memtest docker container and that failed. Not sure why the more thorough test would pass and the janky container test would fail.

If either test fails I would think you have a problem with your RAM.

 

You mention a docker version - did you mean that?   There is the Live Memory Tester plugin which is what you may mean?   As far as I know that is at least as good a tester as the memtest from the boot menu, with the drawback being that it cannot test all the RAM as it is restricted to what the OS allows it access.

Yes, that plug-in is what I meant. At this point I would be ecstatic if it was just replacing the memory, I am not sure how many more unclean shutdowns my array can take.

Edited March 30, 20251 yr by jnosa899

I just ran that memory tester plugin on 16/64 GB of my ram and this is the error I got. Is this a memory error or is something wrong with my processor?

 

Mar 30 11:04:59 pleasedontbreak memtester-runner: memory testing started with parameters: 16G
Mar 30 11:15:38 pleasedontbreak kernel: memtester[22831]: segfault at ffffffffd3400ba0 ip ffffffffd3400ba0 sp 00007ffc81a1cbb0 error 15 likely on CPU 2 (core 4, socket 0)
Mar 30 11:15:38 pleasedontbreak kernel: Code: Unable to access opcode bytes at 0xffffffffd3400b76.
Mar 30 11:15:38 pleasedontbreak memtester-runner: memory testing has finished with errors (code: 139)

Edited March 30, 20251 yr by jnosa899

9 minutes ago, jnosa899 said:

I just ran that memory tester plugin on 16/64 GB of my ram and this is the error I got. Is this a memory error or is something wrong with my processor?

 

Mar 30 11:04:59 pleasedontbreak memtester-runner: memory testing started with parameters: 16G
Mar 30 11:15:38 pleasedontbreak kernel: memtester[22831]: segfault at ffffffffd3400ba0 ip ffffffffd3400ba0 sp 00007ffc81a1cbb0 error 15 likely on CPU 2 (core 4, socket 0)
Mar 30 11:15:38 pleasedontbreak kernel: Code: Unable to access opcode bytes at 0xffffffffd3400b76.
Mar 30 11:15:38 pleasedontbreak memtester-runner: memory testing has finished with errors (code: 139)

That is not a RAM fault.  It could be a program fault, but I would think if anything that is more likely to indicate a CPU or memory controller issue. Might be worth wating to see if anyone thinks different.

Update I tested the ram and the boards ram slots... What a pain and time sink to get to the problem. It turns out ram slot A2 is defective and my ram is fine. Thank you everyone for your help, I was able to initiate a return on Amazon just in time before the return window closed. While I am optimistic that a new board will fix the problem, I will post back if the issue continues in a few weeks.

New board came and I installed it. Rock stable for three days now.  Never have I had a bad memory slot.