Squid

You really should post the entire diagnostics.zip file so that the experts ( @JorgeB) can have a gander at them.

Run the File System Check against disk 14

Tools - Diagnostics. Post entire Zip file

Post your diagnostics

Those messages are normal if a container restarts

AMD Ryzen 7 1700X Eight-Core Processor Part Number: F4-3200C16-16GTZKW Configured Memory Speed: 3200 MT/s See here:https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-819173

It most definitely does not touch anything of the sort.

You want to use version_compare $unraid = parse_ini_file("/etc/unraid-version"); if ( version_compare($unraid['version'],"6.9.0-beta35",">") ) { we're running beta36+ } else { we're running <= beta35 }

If it doesn't come with Unraid, I'm not using it in the plugin.

Probably best to run the File system check against disk 17 after reseating the cable to it

You're 11 times more likely to break a nail when typing the latter. Other than that, they're identical. c is simply a shortcut for cpu-shares To prioritize the OS over a container, you're best bet is to explore https://docs.docker.com/engine/reference/run/#cpu-share-constraint and below You can set the priorities to anything you want. Every container has a default setting of 1024. The lower you go (down to 2), the lower the priority of the container is relative to other containers. The higher you go (up to 2048) the higher the priority of the container is. It's easiest to visualize it only considering 3 containers running on a single core CPU.

extra parameters in the template

/var/log total 720 drwxr-xr-x 2 root root 160 Nov 28 04:40 atop Remove atop from NerdPack. It's known to fill up /var/log

What does container size on the Docker Tab report?

@SpencerJ

It uses the built-in tar. IIRC, installing pigz via NerdPack causes compatibility problems...

Depends upon what you're trying to prioritize over another, but this is a start https://forums.unraid.net/topic/57181-docker-faq/page/2/?tab=comments#comment-566087

Yes. But you don't even have to reassign anything. It will all be handled behind the scenes automatically (the same as if you had multiple drives and one failed. You'd still have access to all of your files)

You definitely want to get rid of the -i as that means interactive

You're probably running 6.9 in which case it's already part of the OS

Check any docker apps to see if they reference /mnt/user/cache instead of /mnt/cache

Except that you transferred the registration to the new Kingston. When you upgrade next, this will happen again. IMO, use the Kingston

yes

The system configuration files are stored on the flash drive. Any data for an app (eg: your movie list for plex) is stored within the array, usually on the cache drive. Appdata backup plugin will make backups of your docker apps' appdata on a schedule If you're not using a cache pool (more than 1 device), then XFS is more resilient to any crashes etc of your server. If you have a pool composed of multiple devices, then you have no choice but to use BTRFS currently

As far as I can tell, it works perfectly on 6.9 (otherwise I'm the one who's going to wind up getting spanked by LT - there were other changes in the icon system for it), so just hold tight.