Squid

Try disabling the healthcheck --no-healthcheck Add to extra parameters in the template

@bonienl

Change btrfs vDisk to folder

Yup, being removed from CA

With the binhex preclear container, there's probably some extra command line options you needed to give it for it to be recognized properly Personally, on the very very rare times I preclear a drive I use Unassigned Devices Preclear

With your continuing issues and this: Apr 6 11:36:13 Tower kernel: BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 2042, gen 0 I'd start by running memtest from the bootmenu for at least a couple of passes (By and large "corrupt" on a btrfs drive is because of memory issues) If you're booting via UEFI mode, you will have to temporarily switch to Legacy mode in order to run the memtest

It goes up and down a fair amount. TBH I'm sick of doing plugin updates simply to fix a link

Instead of using an image for the dockers, switch (Settings - Docker) to using a folder. You'll have to install again from Apps, Previous Apps. 2 minute process with no changes to the templates required

You're going to want to post your diagnostics

Try the manual method https://wiki.unraid.net/Articles/Getting_Started#Manual_Install_Method The USB creator tool has some known issues and is currently being revamped

You have a path in there "/path/to/device" that needs to be adjusted to suit (I suppose it's for an attached camera / device), and if you're not using it, remove the path mapping entry in the template

Settings - Notification Settings - Disable checking for plugin updates on a schedule. This happens on 6.9 with poor / inconsistent internet connections with this option enabled. (And since you're running auto update, zero reason for Dynamix to check for updates anyways)

Settings - Display Settings - Show Dashboard Apps

The size you've set for your docker image is 200G of that, 17G is used, which aligns well with your screenshot. Why set it at 200G? Were you having problems previously with the image filling?

This makes no sense at all. Reboot

Not unless you've made a backup of the flash drive. You were obviously though doing this through the Add Template Screen. Easier and safer to handle this through Apps - Previous Apps

On the docker tab? You can already do this on the dashboard

Grab the diagnostics from the command prompt. They'll be saved on the flash drive in the logs folder and you can upload them here so we can see what's happening.

Only way to skip clearing is to stop the array and do a "New Config" and reassign all the drives. Parity has to be rebuilt, because without clearing the new disks have indeterminate data on them.

Who decides what has value? You? Me? If I decide what has value based upon my use cases there would be exactly 6 apps available in CA. And CA is not a "RSS" feed. Your complaint is that certain maintainers do not create the containers themselves. This is quite quite common in CA. Should the official versions of MySQL or MariaDB disappear from CA because MySQL didn't create the template? Template errors happen. On all templates. I regularly scan the various support threads (all of them). If there is egregious problems, it gets handled on CA's end. If I've missed something, let me know in a PM.

Are you transcoding to RAM?

Yup, it's harmless. If you don't click Ignore it will always keep coming back

Without the diagnostics, I can't give any advice

https://stackoverflow.com/questions/23088725/base64-decode-produces-a-string-containing-null-characters ie: remove the null characters and see if it works

First thing to look at would be does the System Event Log (SEL) in the BIOS have any information? Since you're running ECC memory, you'll want to download and run on a separate stick https://www.memtest86.com/ to test the memory for at least a couple of complete passes. (Most systems with ECC if it detects an uncorrectable memory error will stop the system completely to prevent any corruption from propagating itself)