Squid

Wrong support thread. But, what it's saying there is that an app you named jellyseer-1 was using .../appdata/jellyseer What is the appdata (/config) path for what the container is you currently have installed?

Nothing to think about. It's there. IE: Can't fix what ain't broke.

FWIW, readability as a whole along with general aesthetics was better previously than now currently. While it is usable, I definitely prefer how it was.

Effectively unlimited compared to the size of drives you can buy. While there may be some limitations somewhere over what the theory is on file system maximums (eg: XFS supports a maximum 8 exobyte drive size), not currently available hard drive even remotely comes close to this size.

Your server is unable to reach either GitHub.com or Limetech's mirror of the application feed. Fix Common Problems, and diagnostics also shows this behaviour. Assuming that there is normally no issues with reaching them due to your geographic location, a complete reboot of your network system (modem, router, all switches) would be the first thing I'd try. Also, if you're using jumbo frames (probably not) then disable them

Does the update work if you switch to English?

If only to rule it out, you should run memtest from the boot menu for a minimum of a couple passes (ideally 24 hours) Hope you mean "new to you". The CPU was introduced in 2012, and long discontinued.

Wrong thread lol

Dashboard considers I/O wait in it's displays. Next time it happens, reply back with your diagnostics before you reboot

You need to contact support. Include a copy & paste (no screenshots) of what shows up within Tools - Registration

Version that you're running is from the new dev.

/mnt/user is a unified view of all the shares. Every share exists within there, along with /mnt/diskX (or /mnt/cache)

Because appdata also exists on disk3. Set the secondary storage to be array with mover action of array --> cache, stop the docker service in Settings -> docker and run mover.

And on a reboot the patch shows as not being installed in the plugins tab (don't worry about the install errors one)

Long standing issue (fixed I believe in 6.13). It also has the net result of whenever you go to the VMs tab it's a given that all/most of your drives will spin up