Michael_P

That suggests you're transcoding from the CPU - when you're playing the movie, what does plex show in the now playing dashboard?

OK, you can try moving the movie to the cache drive if you have one and try playing from there to rule out the drive, or try another computer to play the file from, next you can start swapping out network components

Sure, but if you have something else to try you can rule it out Were the windows and mac machinese connected to the same network port as the Apple TV?

this 1- make sure the drive where the video is stored isn't being actively accessed by anything else 2- try another device 3- check your network

Personally, i would ditch the 1070 (this is a no brainer, the iGPU is better in every aspect for media), run 1 SAS card and the expander (SSDs connect to the mobo) - I run 24 spinners and it's plenty. Save power and heat

You can save a ton of power dropping the 1070, don't discount that

It can use either/or for power - if it's in the slot it'll draw power from it and there isn't any need for the molex to be powered, too

Doesn't need the slot, you can mount it anywhere - it only needs molex for power when not in the slot Not better, per se - it'll split up the bandwidth of up to 2 SAS ports and share it between more devices. For spinning rust, you probably won't miss it. @JorgeB did a comparision, it's somewhere around here in the forums

For video transcoding, the iGPU is plenty (and you can do more simultaneous streams, too)

Absolutely Yep, something like the RES2SV240

Oct 3 02:19:42 Hulk kernel: php-fpm invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0 ... Oct 3 02:19:42 Hulk kernel: Out of memory: Killed process 13547 (Plex Transcoder) total-vm:23641336kB, anon-rss:23579300kB, file-rss:0kB, shmem-rss:0kB, UID:99 pgtables:46284kB oom_score_adj:0 That tracks with when it ran OOM at 0219, so try limiting the Plex container (advanced view)

What time is Plex's scheduled maintenance set to kick off?

In standard read/modify/write configuration, only the two parity drives and the drive being written to are active. Having parity drives does nothing to protect the data, just FYI

Just stick to categories if you dont need anything fancy, create a category for each of the 4 types, and then add a path for each category - then when you add a torrent select the appropriate category. I'm not familiar with Qbittorrent but it should be a straight forward process. If you get stuck, there should be a decent guide - i just searched for "qbittorrent categories" and the first result seems easy enough to follow

Not sure about Qbittorrent, but Deluge has a filebot plugin

Diagnostics from the Tools menu or from the command line

That's not going to work. You need to stand up a tunnel that will route incoming requests thru the tunnel to your LAN, that means you need a VPN server 'in the cloud' that's not behind CGNAT. Most people use a VPS provider like Linode or AWS, chuck Wireguard or Tailscale on it and call it a day. Google is your friend here, but if you don't know what you don't know, it can bite you in the ass

You can see what's laying around from the command line with docker ps -a and cleanup dangling with docker image prune -a More info here: https://docs.docker.com/config/pruning/#:~:text=The docker image prune command,%24 docker image prune WARNING!

Have you tried pruning the unused containers? Is it still listed in the docker tab if you enable the advanced view?

Almost always related to cabling, re-seat it or change it out - and they don't go away, so if it doesn't increase, ignore it once you've checked the cables

It used to, there appears to be a bug in the ap for IOS

Try adding this to the the conf proxy_set_header Host $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_buffering off; proxy_max_temp_file_size 16384m; client_max_body_size 0;

Is qbittorrent on libtorrent v2? If so try v1 https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-for-qbittorrent-and-deluge-users-r2153/page/8/?tab=comments

It was back on the 30th of July soif it's not recurring I'd just reboot and monitor it, and appears to be Frigate on your HA setup - either limit the memory it's allowed to have or set up the swapfile plugin