Happy Saturday fellow Unraiders. I have been reluctant to create a new post for this and have tried find a resolution via others' pain. But, I'm out of ideas and fear that my system has a hardware problem. Any insight would be welcome. My server has never really been stable. Constant crashes/freezes which force unclean reboots.

 

The most recent crash last night was while booted into safemode (non GUI). The only plugin I had active was Community Apps. My Plex docker was running and the system was performing parity check. Nothing else was running. I have captured syslogs, diagnostics and a screenshot of the kernel panic but nothing obvious sticks out to my eyes. Any thoughts or ideas of what to try next? Thanks in advance.

 

Things attempted to resolve so far:

BIOS update

BIOS settings for AMD systems (disabled C-States globaly)

Docker configured for ipvlan

Boot into safe mode (Community Apps being the lone exception)

 

rocinante-diagnostics-20240106-1030.zip syslog

Edited January 7, 20242 yr by MACGoof
Wrong attachment

Had another crash. New screenshot and logs. It ran fine in safe mode for ~9hrs today. After it completed parity, I rebooted normally and within about an hour, it crashed. So I guess I will remove all plugins and reboot. Then re-add one at a time until it crashes. Unless anyone can see something here that points to another culprit.

 

 

 

syslog

Edited January 7, 20242 yr by MACGoof
Wrong attachment

Just realized I attached the incorrect screenshot. Apologies. Below is the correct one.

And here is a screen grab from today’s kernel panic.

 

I ran memtest this weekend and it passed.

Tested with some other ram I have and it crashed then as well. I wiped my flash and recreated it just in case something went wrong on initial creation. It ran half the day today but crashed again just after dinner.

 

What are normal temps for the drives? Most are ~35 C but my parity drive can get ~45 C. Just trying to think of anything here. 
 

Hopefully someone with more experience will chime in on if anything stands out in this grab or logs.

On 1/7/2024 at 11:13 AM, MACGoof said:

It ran fine in safe mode for ~9hrs today.

 

2 hours ago, MACGoof said:

I ran memtest this weekend and it passed.

Tested with some other ram I have and it crashed then as well.

 

Does use Unraid build-in memtest ? You must solid pass memtest 1st.

 

I check your diagnostic, the memory config have problem. no reason memory stick would run at 3200MT/s but just 1.2v. ( Pls tuning BIOS memory setting or simple disable XMP, so it will clock down the memory )

 

    Configured Memory Speed: 3200 MT/s
    Minimum Voltage: 1.2 V
    Maximum Voltage: 1.2 V
    Configured Voltage: 1.2 V

 

 

2 hours ago, MACGoof said:

What are normal temps for the drives? Most are ~35 C but my parity drive can get ~45 C. Just trying to think of anything here. 

This not a problem.

Edited January 9, 20242 yr by Vr2Io

22 hours ago, Vr2Io said:

 

 

Does use Unraid build-in memtest ? You must solid pass memtest 1st.

 

I check your diagnostic, the memory config have problem. no reason memory stick would run at 3200MT/s but just 1.2v. ( Pls tuning BIOS memory setting or simple disable XMP, so it will clock down the memory )

 

    Configured Memory Speed: 3200 MT/s
    Minimum Voltage: 1.2 V
    Maximum Voltage: 1.2 V
    Configured Voltage: 1.2 V

 

 

This not a problem.

 

Thank you so much for your input! Was starting to think I broke a forum rule or something since no one has replied.

 

Yes, used the built-in memtest. Two cycles and it passed. Should I let it run for longer?

 

Regarding the BIOS settings. I just now manually configured memory speed to be 3200MT/s and flck speed to be 1600MT/s per the recommendations I could find. Other than that, see attached for what I could find on voltages. I'm guessing you are referring to DRAM voltage which is set to Auto. Should I manually change that to something else?

 

I didn't post my system specs, my fault. XMP is intel. AMD calls that DOCP and that setting is not enabled. It is set to Auto as well. Options are Auto/Manual/DOCP.

 

Was honestly considering returning my MB and converting to an Intel system. I had this AMD processor, graphics card and power supply laying around so I bought the MB, RAM and storage for this build.

 

AMD Ryzen 5 3600

NVIDIA RTX 2060

Asus ROG Strix B550-F

x2 Crucial Pro RAM 64GB Kit DDR4 3200MT/s

x2 WD Black SN850X 1TB cache

x4 Seagate IronWolf Pro NAS 4TB

Seasonic PX-850

 

 

 

Make sure the correct power supply idle control is set, see here:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

 

10 hours ago, MACGoof said:

Yes, used the built-in memtest. Two cycles and it passed. Should I let it run for longer?

 

May be best in 4 passed.

 

10 hours ago, MACGoof said:

Regarding the BIOS settings. I just now manually configured memory speed to be 3200MT/s and flck speed to be 1600MT/s per the recommendations I could find. Other than that, see attached for what I could find on voltages. I'm guessing you are referring to DRAM voltage which is set to Auto. Should I manually change that to something else?

 

I will simple clock down to 2400MT/s, this is a quick way to remove memory problem then 2 passed and going further troubleshoot, you can set back to auto or 3200MT/s later if you confirm problem not come from memory. Not suggest manual set the voltage. I never found a mobo will use 3200MT/s but config in 1.2v instead standard 1.35v.

Edited January 10, 20242 yr by Vr2Io

3 hours ago, JorgeB said:

Make sure the correct power supply idle control is set, see here:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

 

 

Thank you for replying. This was completed prior to posting.

I ran memtest overnight (10 hours) and it passed again with the manual settings I referred to above. (Memory 3200MT/s  and flck 1600MT/s)

 

Booted up and started the array. Then grabbed diagnostics and syslogs attached. Gonna let it run with zero pluggins and only the Plex docker running.

 

 

rocinante-diagnostics-20240110-0547.zip rocinante-syslog-20240110-1353.zip

2 minutes ago, MACGoof said:

I ran memtest overnight (10 hours) and it passed again with the manual settings I referred to above. (Memory 3200MT/s  and flck 1600MT/s)

That's fine, we can assume memory / its setting fine.

 

 

 

4 hours ago, Vr2Io said:

That's fine, we can assume memory / its setting fine.

 

 

 

 

Thanks for confirming. I saw this warning in Docker logs. Is this anything to worry about?

 

time="2024-01-10T05:20:43-08:00" level=warning msg="containerd config version `1` has been deprecated and will be removed in containerd v2.0, please switch to version `2`, see https://github.com/containerd/containerd/blob/main/docs/PLUGINS.md#version-header"

Crashed again about 10 minutes ago. Here is the screen shot of kernel panic, logs and diags. Can anyone see anything relevant or do I have a hardware issue? Community Applications was the only plugin and Plex the only Docker running.

 

What sort of things do you look for in the logs? Just errors I assume? I scan the previous logs and diags but never really see anything that stands out.

 

 

rocinante-diagnostics-20240110-0547.zip syslog

Looks more hardware related to me, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

12 hours ago, JorgeB said:

Looks more hardware related to me, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

 

This is the way I'm leaning as well. I did boot into safe mode last week and it was stable for roughly a day. As soon as I rebooted into normal (no GUI), it started crashing again. I'm going ahead with my plan to return the MB and convert to Intel. Going with a side-grade/maybe slight upgrade i5-12400. This started as a way to use spare parts and has turned into a whole thing

 

Thanks again for your time and help.

I had this issue and it was due to using Firefox and Plex. When I would attempt to watch a movie using Firefox it would use a high amount of resources on either CPU and GPU to transcode. Shortly after the system would crash and become unresponsive. Using Google chrome on the same movies it worked fine. Still not sure why Firefox is causing the problem. Turned off all addons and cleared cookies.