dkuhn

I had some pretty heavy transcodes going on for almost the entire week. They finished, and I guess that's when the idle usage happened. It is also crashing during streams, but I attribute that to the fact that the CPU is going back to idle during a plex "throttled" stream as the CPU is faster than the transcode job! (Which, in my book is a good thing, assuming we can get that C state issue fixed)

Model: Custom M/B: ASUSTeK COMPUTER INC. - PRIME B350M-A CPU: AMD Ryzen 5 1600 Six-Core @ 3200 HVM: Enabled IOMMU: Enabled Cache: 576 kB, 3072 kB, 16384 kB Memory: 16 GB (max. installable capacity 16 GB) Network: eth0: 1000 Mb/s, full duplex, mtu 9000 Kernel: Linux 4.9.28-unRAID x86_64 OpenSSL: 1.0.2k Uptime: 0 days, 07:23:50 No overclocks - completely stock. Didn't want to open that can of worms yet. https://puu.sh/vXEIT/475465ab36.rar That's the last log I have at the moment. It hasn't crashed today, will post a new log once it does.

I've been running troubleshooting mode each time it boots back up - will post logs next time it crashes. Logs haven't presented any telling errors so far, they just end. I am indeed running Plex as a docker container, but the transcode location is my cache SSD not /tmp. Docker containers: couchpotato deluge munin-server owncloud PlexMediaServer plexpy sabnzbd sonarr Plugins: Community Applications Dynamix SSD Trim Fix Common Problems Nerd Tools

https://forums.lime-technology.com/topic/57294-unraid-633-crashing/ Linking my post here as I just found this thread. Having stability issues even with Global C State Control set to "disabled". Worked for about a week then it crashed, and has been crashing every day since then.