Squid

Yeah, I saw that too, but decided that 320MB/s average speed for a 10TB array wasn't even close to being realistic. Was the parity check tuning plugin installed during the initial build of parity? If it was and it paused the initial build and you've reset the system, then it never completed and during a subsequent check (with it installed or not), then the errors would be expected

No... You need reverse

You probably bought forward breakout cabling. You need reverse breakout. They look the same, but are wired differently

Did you ever build parity in the first place? Post your diagnostics.

Post your diagnostics just in case

Calculation is correct. You have 26TB (10 + 8 + 8 )of storage space available. The 10TB parity drive can (in conjunction with other drives) rebuild any data drive that suffers a failure.

Either way works, but running a VM specifically to run something that is available as a docker container is a waste of resources as the OS itself has its own resource requirements and overhead involved. See this for a great introduction to docker.

Many users (including myself) do not use the cache drive to cache any writes to the media shares on the array, and dedicate the cache drive / pool for VM / docker appdata usage exclusively.

Mid 40's aren't anything to really worry about. You can adjust the temperature thresholds within Settings - Disk Settings

I would guess OTOH it's because plex makes extensive use of symlinks, so it has hundreds (thousands) of files within it's appdata that all point to the same file.

It won't get approved unless you change it to ..."._($page)."... and ..."._($display_name)."... Has to be like like for translations that are forthcoming soon(tm)

Tools - UpdateOS

https://github.com/limetech/webgui

Yeah, I'm seeing the same thing. Change it to PLEX_STREAMS

Both symptoms imply you have issues connecting to the internet. Try setting appropriate static DNS addresses in network settings at a start (208.67.222.222 & 208.67.220.220)

By having a space in the file name

CA / FCP does this very extensively (with the dynamix.docker.manager and dynamix.plugin.manager) Only thing you have to be aware of is that there is no guarantee that the functions you want don't change from unRaid version to version. Although this is very rare.

Looks like you're running a scrub or something on the cache pool. What happens when it's finished.

Because the author deletes the containers from dockerhub

01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller [1b4b:9230] (rev 11) Subsystem: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller [1b4b:9230] 01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller [1b4b:9230] (rev 11) Subsystem: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller [1b4b:9230] Marvel based controllers are very problematic Use onboard ports if you can or switch to ASMedia or LSI based controller And maybe peruse this thread

Apr 19 10:45:53 Unraid kernel: [Hardware Error]: Unified Memory Controller Error: DRAM ECC error. Normally I'd say that one of your sticks is going bad, but I can't really determine if you actually have ECC memory or not. Either way, it was one error that was corrected. May just be a cosmic ray thing. Reboot to clear out the error and then see what happens.

If it won't boot at all, then you'll have to pull the stick and edit /syslinux/syslinux.cfg on another computer and remove the vfio section the plugin added. Or boot via GUI mode (or vice versa), and then via Main, Boot Device, click on flash then syslinux configuration and edit the file there.

Was the banner about system notifications being disabled there before the UI went nuts? If not, it's because your flash drive decided to drop offline / have issues

What plugin?

I'm not seeing it... What browser are you using? Can you try a different one? Disable any ad blocks?