Squid

You should probably post in the rclone thread, as in and by itself the OS isn't responsible for that. Not to say that a change in the OS isn't a contributing factor.

The first dropdown *should* work with the pre-populated items The second one (after the "or") has to be entered in manually due to security changes in 6.10

The only part you needed to remove was the vfio-pic.ids=.... You still need to keep the pcie_acs.... And additionally, you would have to go to tools - system devices to then stub the hardware properly

When clicking on the View Next Unread Report when in a defect report, the current report simply reloads instead of going to the next report

Fatal: Plugin URL on xml template does not match PluginURL in .plg (https://raw.githubusercontent.com/docgyver/unraid-v6-plugins/master/ssh.plg vs ) You problem is that on the .plg you've got an unescaped ampersand on line 74 dd if=/boot/bzroot bs=512 skip=$(cpio -ivt -H newc < /boot/bzroot 2>&1 > /dev/null | awk '{print $1}') | xzcat | (cd /boot/config/plugin/ssh/baseline ; cpio -i -d -H newc --no-absolute-filenames etc/ssh/sshd_config ) and unescaped ampersands aren't allowed in XML. Either escape it (&amp;) or ideally put the entire FILE code within a CDATA tag IE: the .plg file is invalid and will not load even if simply pasting it into Install Plugin

And, "Stock" speed in RAM actually tends to be an overclock since every motherboard manufacturer seems to think that enabling the overclock on RAM (ie: XMP / AMP) is the correct thing to do by default.

I don't know what happened, but your recovery is Apps, Previous apps and check off what you had installed then hit install

Exactly. Seemed to me to be completely pointless to have a GUI when no matter what you had to go to dockerhub to find out everything you needed to add in anyways. So I forced you to do that. Unfortunately, most people don't understand that change and thought I was taking something away from them. Which I'm not. But, I have given in to pressure and it will get re-added on the next release.

Ignore it. Depending upon what you read online, it's either a badly worded message that doesn't mean what it says or it's just not working. Either way, harmless

That is the right way You should post your diagnostics

Nov 1 18:58:31 DAGON kernel: BTRFS error (device nvme0n1p1): incorrect extent count for 3243245568; counted 1366, expected 1338 What you might consider doing is redoing the cache drive as XFS. BTRFS works fine for most people, but the most stable by far is using XFS, especially if you have no immediate plans to install a redundant cache pool in the near future. If the "docker image" keeps doing this for no real reason (ie: you've never filled it up), then something else that might help is switching to using a docker folder instead of a docker image.

Yes. Personally, I never bother with a preclear, as a rebuild onto them followed by a parity check is the same rough thing as a pre-clear.

Why do you need them in .yaml file? Any system supporting docker compose also supports docker itself, and you can get the applicable commands by editing what you have and make a change, revert the change then apply and the applicable command will appear to run on the other system after adjusting for paths

Are you sure? Drives will work, but unless I'm mistaken they'll only be detected as max 2.2TB

it should be /var/local/emhttp/var.ini

No matter what, it would be the usual suspects always showing up. Netdata has an update issued to the container multiple times a day 365 days a year Most of the common containers would also be "permanently" stuck in updated apps simply because of how and when updates get issued to them.

What are you talking about "automatically" updating? Only time they'll update is if you hit Update or if you have the auto update plugin installed (and via it you can cherry pick what to update)

Very unlikely, since that was largely meaningless (except for plugins) as in this day and age with containers that automatically get built as new app versions come available, or rain or shine every Friday it was extremely rare for any template to ever get updated by the maintainer that the container was updated.

Oct 30 02:23:33 Tower kernel: mce: [Hardware Error]: Machine check events logged Oct 30 02:23:33 Tower kernel: mce: Uncorrected memory error in page 0x0 ignored Oct 30 02:23:33 Tower kernel: Rebuild kernel with CONFIG_MEMORY_FAILURE=y for smarter handling Oct 30 02:23:33 Tower kernel: [Hardware Error]: Deferred error, no action required. Oct 30 02:23:33 Tower kernel: [Hardware Error]: CPU:1 (19:21:0) MC22_STATUS[Over|-|-|AddrV|-|-|UECC|Deferred|-|-]: 0xd589f68949fd8949 Oct 30 02:23:33 Tower kernel: [Hardware Error]: Error Addr: 0x0000000000000000 Oct 30 02:23:33 Tower kernel: [Hardware Error]: IPID: 0x0000000000000000 Oct 30 02:23:33 Tower kernel: [Hardware Error]: Northbridge IO Unit Ext. Error Code: 61 Oct 30 02:23:33 Tower kernel: [Hardware Error]: cache level: L1, tx: GEN I *think* its a typical ryzen problem that appears on all platforms and can be safely ignored

Soon

I have a "normal" daily driver with a decent video card, so I run Plex on it to avoid any of the complications with GPU passthrough to a container.

And make sure you include a trailing slash

Usual reason for the image getting corrupted is the image filling up. Setting it as a folder allows it to expand up to the entire size of the drive its on without actually reserving any space in advance for it. From what I'm seeing in the logs though there's no obvious reason for what's going on (hence the memtest). So, my next shot is try a folder

Start with recreating the docker.img file https://forums.unraid.net/topic/57181-docker-faq/?tab=comments#comment-564309

There's two smart files smart-one and smart-all try deleting them both