Squid

You should post your diagnostics to put everything into context

You should post your diagnostics

You should post your diagnostics, but probably you're going to have to https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309

Disable any RAID mode you've got setup in the BIOS 00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management Device NVMe RAID Controller

VT-d is under Advanced, System Agent in your BIOS Does the system show that HVM is enabled? That's done via Advanced, CPU Configuration And also, what is your CPU

You enabled Virtualization and VT-d / IOMMU in the BIOS? There's 2 separate options to enable, and the latter is usually buried in a submenu

Active Streams plugin / Open Files plugin.

If you simply want to basically start over, then just delete the contents of /config on the flash drive (but do not delete the .key file) and reboot Your containers will all be still be there but you can simply delete the docker.img file (https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309) (This does leave all of your data intact but you will have to re-assign your drives)

It's either still backing up or verifying

That *appears* at first glance to be some corruption on the flash drive. Diagnostics (in a new General Support thread) might help pinpoint what's going on

Your best solution is upgrading to 6.10 and switching from macvlan to ipvlan instead

https://unraid.net/contact

I took a wild guess at the name of the container.

Possible corruption on flash drive Fix common problems tests the integrity of your flash drive by ensuring that certain required and guaranteed to exist files can be correctly read. You will see this error if these files are missing and/or cannot be properly read. Reasons for a corrupt flash drive could be: Unclean shutdown caused by power failure, crashes etc when the server is possibly updating information on the flash drive Defective flash drive (replace it) It would probably be best to create a post in General Support and include your diagnostics for further investigation NOTE: This is a relatively new test and there may be some false positives due to various configurations, plugins installed etc. If a false positive is found, then the next release of Fix Common Problems will "whitelist" the configuration file. If you have any questions, post the full FCP warning and your diagnostics (from Tools -> Diagnostics) to this thread https://forums.unraid.net/topic/47266-plugin-ca-fix-common-problems

You should post in the mover tuning plugin's support thread. Otherwise, uninstall the plugin, reboot and try it again based upon the stock mover script

Not in my mind. But, you can have the Apps tab show those results by enabling Show Incompatible Apps in it's settings. You will also have to understand that no provisions are ever going to be made by CA in keeping the entire system running (appfeed etc) under that OS version (or more to the point, CA versions less than the current version, and you're stuck at that rather old version of CA now)

userscripts, gpustat, intel-gpu-top, nvidia-driver

It's already marked as being only compatible to 6.9.2, but if you're removing it very shortly, then I'm going to pre-emptively blacklist it. What about the companion plugin?

You really need to do https://unraid.net/contact to let Limetech do the proper investigation and supply all the details.

Can you retry all this stuff without running what appears to be folding at home? In your diagnostics it's taking at the time the ps was run 850%, and at the time top was run 1076%

Use the unassigned devices plugin (you may also need to install Unassigned Devices Plus to support ext2)

So I started thinking about this today and ran into an immediate problem Let's take netdata as an example. It's updated pretty much every day. So, since any delay period causes the update "days" counter to restart again this would never actually get updated. How would you handle this?

Yes, but if they're both saying the same thing "Can't create directory" it implies the problem is not with either of them.

I would look at youtube, SpaceInvader One's channel. Tons of videos which will give you a good run down of things.