I suspect my issue is related to Plex and transcoding. A couple of weeks ago I let a friend access my Plex (remotely) and this problem seems to coincide with when this started happening (it's happened 3 times so far in the last month or so) They watch on an iPad that requires transcoding for some media. I could be completely wrong but that is the only thing that's really changed. I turned on Syslog server and things were fine for a couple of days but then this morning I couldn't access Plex on my local network and the UnRaid GUI was showing all CPUs pinned at 100% and was unresponsive (I had left a browser tab open). I suspect this is the pertinent error in the log:

Mar 21 04:07:35 NAS kernel: Plex Media Scan[20791]: segfault at 0 ip 0000148e546fdeed sp 00007fffa7536610 error 4 in libavcodec.so.59[148e54587000+3e1000] likely on CPU 4 (core 4, socket 0)
Mar 21 04:07:35 NAS kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f
Mar 21 04:09:15 NAS kernel: Plex Transcoder[21501]: segfault at 0 ip 000014ea52efdeed sp 00007ffd32840310 error 4 in libavcodec.so.59[14ea52d87000+3e1000] likely on CPU 4 (core 4, socket 0)
Mar 21 04:09:15 NAS kernel: Code: 41 56 41 54 53 0f 57 c0 0f 11 46 20 0f 11 46 10 0f 11 06 48 c7 46 30 00 00 00 00 8b 6f 10 48 8b 17 89 e9 48 89 e8 48 c1 e8 03 <8b> 04 02 0f c8 80 e1 07 d3 e0 8d 4d 10 8b 57 18 c1 e8 f0 39 ca 0f

I could be completely wrong as I am not knowledgeable about this sort of thing. I have attached a diagnostics and the syslog hoping to get some help with this and possibly remedy this issue. Any help, or advice is much appreciated.

nas-diagnostics-20250322-1134.zip syslog-192.168.0.208.log

I'm used to seeing Plex related segfautls in various diags, so that's not always an issue, but don't see anything else relevant logged, does it still happen if you leave Plex disabled?

7 hours ago, JorgeB said:

I'm used to seeing Plex related segfautls in various diags, so that's not always an issue, but don't see anything else relevant logged, does it still happen if you leave Plex disabled?

It happened again last night/this morning. I am able to use some terminal commands such as top but not others such as reboot. I've attached a screenshot of top results in case that might point to something.
 

I looked at the (updated) syslog and there doesn't seem to be anything related to Plex. Can you take a look at the latest syslog and see if you can spot anything? I'll disable Plex and see if that makes any difference though. Thanks.

syslog-192.168.0.208.log

Edited March 23, 20251 yr by denzo

I'm afraid that there's still nothing relevant logged, this can also be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/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, including the individual docker containers.