Squid

Doesn't that mean that you've got two appdata shares and therefore a ton of duplicated files? Not the ideal thing to do -> if you reference within the container's template /mnt/user/appdata/... then which pool is it reading from? There are rules dictating what it does for duplicates, but been forever since I've tested that and can't remember OTOH

Glad its working, but that doesn't make a whole lot of sense to me with regards to CA -> especially if you were already on 2025.01.15+

Do you have multiple tabs / browsers / devices sitting on the dashboard by chance?

Thanks for your investigation. The fix we put in for memory issues on 7.0.0 obviously didn't cover everything. This gives us a good data point on solving this issue.

We recommend that everyone running 6.10.0+ install the plugin - This includes 6.12.15 and 7.0.0

Or if within the GUI for the plugin (Tools - Unraid Patch) you hit "Install" Uninstalling the plugin alone (and rebooting) will set you back in the "unpatched" (not-recommended) OS

As previously mentioned, updates to the plugin will be coming

Sorry for the delay. I missed this. Can you reply back with your Diagnostics.

Additionally, if when upgrading the OS and patches are available that aren't in the new OS version they are also automatically downloaded and installed when you reboot for the upgrade.

Try the other ethernet port? It's an Intel E1000 which is the gold-standard for ports

Patches are installed after you're notified about them (or manually check for them) When you reboot your server If in the GUI you manually install them.

Rolling back (in the very unlikely event of an issue) is uninstalling the plugin and rebooting. The plugin automatically checks for any new patches once a week. If a new patch becomes available, then you are notified about it via your notification settings. The new patch itself however won't be automatically installed until you either do it or you reboot your server. Due to the need to create the plugin, and test every single release of the OS with the patches installed to confirm no issues were caused, the system is setup to "auto install". As the scope of the patch plugin evolved and it was going to be potentially utilized for ongoing patches going forward, then the auto install and some other considerations did come up. But at that point revamping everything would have incurred a significant delay in publishing the patches. This plugin will be updated over time.

Try 7.0.0

Not without manually looking at them. Provisions used to be present in the OS to update the templates but it caused a whack of issues and wasn’t worth it due to how rarely templates get updated

Docker Tab, click the icon and select "Edit". There you can modify any variables you set originally or change them etc.

Not sure. It works for me -> with it simply installed, and accessing the server via TS on another device. Best bet would be to ask in the TS support thread

Reboot into safemode Starten Sie im abgesicherten Modus neu

Want me to test @dlandon? Tell me what you need

If after upgrading to 7.0.0 and closing out all the other browsers, tabs, devices open to the webUI, then try it all again. If problems still exist, let me know what computer you're using, browser, how long it took for the problem to manifest itself when sitting on the dashboard, and include your diagnostics

Jan 6 01:03:31 Cubus kernel: ffmpeg[22669]: segfault at 14ba0c15aee8 ip 000014ba146921eb sp 00007fffd76914b0 error 4 in libavformat.so.60.16.100[14ba1460f000+1ce000] likely on CPU 7 (core 7, socket 0) I'd start with running a memtest from the boot menu for at least a couple of passes. Quite often (not always) segfaults can be caused by memory issues. The mce has nothing to do with this initially, and is listed as a "corrected" error, but again may also be memory related

You've got a docker container referencing on one of its paths /mnt/cache/... and you do not have a pool named "cache" - only a pool named "cache_nvme". Edit each container and update the path appropriately (Because of this, you may also be having issues with containers where they lose their configuration etc after stopping / starting / rebooting the array)

Wouldn't have been this. The plugins which are integrated will not install. EG: SSD trim, Unlimited Width etc will not install themselves when booting 7.x

Not quite sure what you guys want from me here. If @NetAlertX wants to create a new support thread here (instead of GitHub) with the relevant information, then either @FlippinTurt or myself could update the xml to point to the new thread. Alternatively @NetAlertX, (this is the ideal thing) if you want to create a new GH repository with the xml then I'd use yours and get rid of FlippinTurt's. (Please use a new GH repo, not an existing repo for NetAlertX)

The mce while it exists, doesn't show any details. Look in your system event log and it'll probably say whats going on (I'd surmise memory)

close all browser sessions open to the UI on all devices Then log out, wait a couple minutes and try again