Tristankin

If anyone else stumbles across this. It was a hardware issue. I replaced the PSU and RAM, still got crashes. Ended up being the CPU, crashed whenever it was running a version newer than 6.8.3. I recently replaced the i3-9100 with a i7-9700T and the issue has been solved.

This took me a while to work out so I thought I would share my swag config to hopefully help others in the future. htpasswd configured specifically for the admin section as I would like to be able to add nodes while remote from the server swag htpasswd -c /config/nginx/.htpasswd create a file in proxy-confs, I used headscale.subdomain.conf Both headscale and headscale-admin on my proxynet so containers can be called by name rather than ip. server { listen 443 ssl; listen [::]:443 ssl; server_name hs.[yourdomian.com]; include /config/nginx/ssl.conf; location / { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app headscale; set $upstream_port 8085; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_buffering off; add_header Strict-Transport-Security "max-age=15552000; includeSubDomains" always; auth_basic off; } location /admin/ { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app headscale-admin; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_buffering off; add_header Strict-Transport-Security "max-age=15552000; includeSubDomains" always; auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; } } Also some changes need to be made to the headscale config as described here: https://gist.github.com/Und3rf10w/1cd618f0656191b7db30fb29aaa35678

Yeah, good idea to check hardware. I have been through the ram replacement route myself (and PSU, and sata card). My system seems particularly sensitive to crashes which forced me to stick to 6.8.3 for 5 years. 7.0.1 was the first new release that seems stable. Crashes occurred as soon as I went to 7.2.2 but I haven't tried the versions between yet. The other things that I tried were to move the transcode directory from /dev/shm to a tmpfs mount in the go file and pining all services off CPU 0 to leave that for unraid itself.

I think 7.2.2 isn't playing nice with the intel iGPU, try rolling back the OS. https://forums.unraid.net/bug-reports/prereleases/69x-611x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-not-alder-lake-r1674/page/14/?tab=comments#comment-36452

I think its a 7.2 issue, I had the same problem with crashes, pretty sure its linked to the intel iGPU https://forums.unraid.net/bug-reports/prereleases/69x-611x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-not-alder-lake-r1674/page/14/?tab=comments#comment-36452

It might be 7.2? Try rolling back the version. I had a similar issue with 7.2.2 https://forums.unraid.net/bug-reports/prereleases/69x-611x-intel-i915-module-causing-system-hangs-with-no-report-in-syslog-not-alder-lake-r1674/page/14/?tab=comments#comment-36452

Try blacklisting the gpu and removing intel gpu top. You may be experiencing the following issue.

Let us know how you fare.

Hi All, Just wondering if I could get a little help creating a Profile override in plex. I have created the profiles folder in the appdata directory for Plex Media Server, but I am not sure where in the logs I am meant to be checking to see if the override is being loaded. Old forum posts point to a dlna service debug log but I am assuming this is an older way the logging worked. Let me know where I am meant to be looking and that would be great.

I can confirm that transcoding does not need to be in use to cause the crash.

@Thanassos @Migz93 @dlandon I have submitted a bug report for this

For those who want to follow the bug report or to add their own findings, here is the link.

Yeah, seems to be many people in the same boat with the i915 module on 6.9.x and 6.10 releases. Probably would be a good time to submit a bug report, and it would also be good if the mods and community stop blaming these hangs on hardware issues when the system shows empty logs on intel hardware with the i915 module loaded. All pretty easy touchpoints to pick up on in the diagnostics report.

Which version of unraid did you end up running? Sorry no one reached out to help.