Squid

Update FCP

Hi there. What is this pool named cache_zfs_test Is it actually a ZFS pool? If so, it should not be mounted within /mnt Use /mnt/disks instead It appears at first glance that the ZFS plugin wasn't properly unmounting it, possibly because everything within /mnt should be reserved for OS managed devices only (hence use the /mnt/disks/... instead)

That file doesn't exist anywhere on my systems, but try the update

Can you post your diagnostics Also what happens with this command ping -c3 google.com

If it's any plugin, it would be the MyServers plugin. I have no idea how often it performs tests like this. Perhaps @ljm42 could offer some suggestions

You have to narrow it down to which exact container its coming from and then ask within it's support thread (click on the icon, select Support)

Plugins don't particularly worry me. We're a small club of authors, and no one gets a free pass on inspection, and we also all have to deal with certain employees of Limetech doing another random inspection looking for other types of vulnerabilities. I'm more concerned about users installing a random container from a dockerHub search (not anything within CA itself) that might contain something unexpected (eg: mining software). The sweet thing about docker apps in particular is that they all only have access to files and folders that you've explicitly given them permission to have, so any malicious intent (eg: ransomware) is limited. Once again, this is about stuff that's on a dockerHub search, not CA itself. Both CA and FCP know what's going on with the apps installed, and if (big if) something ever malicious snuck through immediate steps are done to both alert the user and myself to what's happening.

Which is why every single plugin regardless of author undergoes a code inspection prior to inclusion in CA

If you can't see them now, they probably got lost somehow. Been too long since I upgraded to 6.9 to accurately remember. Shouldn't be too hard to set them back up again.

How were you doing that before?

LT Support should be able to answer on what key type you have

The USB Creator tool has some known issues. I would suggest you utilize the manual method. https://wiki.unraid.net/Manual/Changing_The_Flash_Device#Manual_Method

Try today's update

It appears that you have a BASIC key, but you have too many devices and need to upgrade to a Plus. You should contact support https://unraid.net/contact if this is incorrect.

I believe that 6.10 is making some changes to make this easier for the end user

No. Not because it's not an easy thing to do, but mainly because I don't want to deal with the inevitable support requests caused by that. Edit the "go" file (/config/go on the flash drive) to accomplish this

And you'll need to reboot to clear out /var/log

Apps - Previous Apps And no indication. Could be from unclean shutdowns. Hard to say definitively at this point. If this becomes a recurring issue then will jump off that bridge at that time.

Mar 6 16:10:05 tardis kernel: BTRFS error (device loop2): incorrect extent count for 7278166016; counted 259, expected 258 Mar 6 16:10:05 tardis kernel: BTRFS: error (device loop2) in convert_free_space_to_extents:454: errno=-5 IO failure Mar 6 16:10:05 tardis kernel: BTRFS info (device loop2): forced readonly The docker image is corrupt. Usual reason is that it filled up or unclean shutdowns. Delete and recreate (will be done before you can make yourself a coffee)

Not unless you gave them one via the template or docker run command

Without diagnostics, there's not much anyone can do to answer. If top / htop don't show the processes running using the CPU, then it's going to be an I/O Wait (which htop does show). The dashboard takes into consideration IO wait on its graphs. NetData app is also a great tool for diagnosing stuff

Is the server itself still responding? If it is, then its something in the container if there's no problems with the docker image (full, read-only etc)

Nope Post your diagnostics

the appdata share vs any other random share is simply a convention and nothing your particularly have to stick with Change the default appdata location in settings - docker. This will NOT however change anything already installed. The docker image does not exist on the flash drive, so if you boot with another flash and the image location etc is the same, then your apps will all show up (but won't be editable etc without the applicable files on the flash drive. This includes references to the icons (Admittedly, this is a scenario I never tested with the various changes to the way icons are handled). The docker image is very safe to delete (Settings - docker with the service disabled) and then recreate (via Apps - Previous Apps), assuming you did an actual backup of your original flash drive which had the templates stored on it.

What about Power Supply Typical Idle? (Set to "Typical") - And also look for BIOS updates