BRiT

I am using the dark theme if it matters.

The recent change of styles for the forum makes it incredibly difficult to be able to tell the difference between Unread and Read threads. Previously the unread threads had thicker font style, perhaps even used bold. Now the text style is barely different from already read threads. Is there any chance you can reapply the styling or do something to show more of a difference between the two? Thank you

Be sure to see if you are using any plugins that are not 6.11 compatible. First up is NerdPack (provides ability to install more smaller things), if so transition to NerdTools (similiar to NP but 6.11 compatible) or plan to after the upgrade. I think the approach I used was to write down what I actually used from NP, uninstalled it, upgraded OS, installed NT, then installed what I used from my list. Next up is NUT which is an alternative Battery UPS plugin. Most simply use the normal APCUPSD instead. There is a newer version of this being maintained by an active community developer. You should switch over to their version, if you need it. This may only be required if you plan on going to 6.12.x series once it releases. Those were my two largest updates that I needed when upgrading. Oh, I did have to upgrade my version of PUTTY on all my other windows systems so I could SSH into unraid. Something about newer cipher algorithms or certs being used and removing compromised older ones. Without this client software update it couldn't negotiate a connection. At the same time I also switched my dockers from macvlan to ipvlan. That was painless for me, but I did need to adjust the docker config to remove the old params and use the newer params in order for them to start. For my VMs, I pulled down newest vm tools and made sure to update them inside the VM after the unraid update. I may have been lucky, but going from 6.9 to 6.11 was uneventful for me.

For completeness here are the previous posts documenting this regression and misbehavior compared to older versions of "newperms" which worked fine with "." as current directory:

I reported this exact behavior for "newperms" before but was told it was working as expected. It has a bad effect on the UI and a lot of other things. The quickest way to undo the damage it did is to reboot.

Is there a solution to this current thread? Or will it remain unsolved? 😋

That's just the way they were implemented. 🤷‍♂️

All expected parts of the system to support the functionality of docker and vms.

In the meantime maybe you could try from here -- https://slackware.pkgs.org/15.0/slackware-x86_64/expect-5.45.4-x86_64-4.txz.html / https://slackware.uk/slackware/slackware64-15.0/slackware64/tcl/expect-5.45.4-x86_64-4.txz

Is preallocation for full size of download enabled in your torrent software?

AFAIK, Nginx is what the base web ui uses.

Recycle Bin is the best you're going to be able to deal with, but that is restricted to SMB activity.

You need to restore from backup your "appdata" share. You said in the first line of your original post that it was wiped out from the crash. That is where all the data is really stored for these dockers. That is your issue.

You need to restore from backup your "appdata" as well. That is where all these dockers store their actual configuration files and databases and other required information. The "previous apps" is very limited information like the parameters and configuration of the docker run command.

You could easily install your own webserver docker and serve up the files that way.

I don't know if those drive are supported by WDidle3 or if they have their own program to adjust their behaviors, so do your due diligence to know if that is needed or even supported. But in the past many have had to use that program on WD drives to get their load cycle counts under control.

Have you tried adjusting their settings using WDIDLE3?

XMP is overclocking memory. I would avoid all overlooking on a system that stores my data. It doesnt matter if it's cpu or memory, you don't want to run out of spec.

You probably need to ask the actual Plex developers what their application does when "optimizing the DB" and what additional directories you may have to map so it doesn't write inside the Docker image.

Out of curiosity, does your patched versions work on older 6.10.3 systems? I am wondering if I can switch over before hand, so when I do opt to move to 6.12 it eill be a couple less steps to do at that time. Thanks for the updates.

You're running Dynamix File Integrity / Bunker / Sha256 on a lot of your files.

If I recall correctly, and I may be off the mark... The top tier allows for unlimited number of drives to be connected but has a limit of 30 devices PER POOL. So if you want to use more than 30 drives, say 60 drives then you would define 2 different POOLS.

I'm sorry you screwed up and don't view a helpful post showing one how to directly contact the company as being helpful. Maybe your view will change after you resolve your issue and are not feeling frustrated from your mistake. Have a wonderful weekend.

You should directly contact the company if it's Urgent. https://unraid.net/contact

Still seems a bit daft to not have any recovery code options.