Squid

Just on the off chance, did you try simply loading the UI in another tab? Does anything happen / appear if you hit the log button?

Looks like the docker.img is corrupted. Easiest to delete it and recreate it then re-add your apps via the apps tab, previous apps. Other problems. Disk 1 has a ton of read errors Personally, I'd replace it with 32 reallocated sectors, and 8 more waiting currently to be reallocated.

correct To run a script before the array is started, (ie: very early in the boot up sequence), you manually edit the "go" file /boot/config/go and add your own script / commands in there. Doing that via the plugin is not something I'm interested in doing / supporting

Because of this, I'm going to mark this plugin as being incompatible with 6.4+ within Community Applications. Should someone else take up the mantle, let me know.

And as an aside, I do believe that with any test in FCP I am more than fair. While ultimately every single test boils down to my opinion on the matter, someone has to make the determination. And my track record with FCP does show that when I am in error about such and such test I do adjust accordingly.

I'm talking about statistics sender which is part of preclear, not Dynamix Stats which has nothing to do with it. And FCP is checking for statistics sender, not dynamix stats installed without preclear. I guess that I can make the wording clearer, but in the installed Plugins section, it is named "Statistics" My point is that stats sender installed without preclear installed is 100% pointless and while at best may be benign and cause no trouble, and at worst its another plugin installed which may under certain circumstances cause issues. Either way, having a completely unused plugin installed (if preclear is not installed, which is the only way the warning trips) doesn't make any sense.

Do the update, once the too many files open appears, post your diagnostics

Scripts are executed as part of the array initialization process, and until the script is finished, the whole boot process is paused. Unless you fork a new process into the background.

6.3 was limited to a Max width of 1280px which in this day and age is tiny Sent from my SM-T560NU using Tapatalk

If you have dynamix (Settings - Notification Settings) set to check for updates on a schedule, then the button is not there. The system will automatically check for updates whenever you enter the tab. If dynamix checking for updates is disabled (ie: you're relying upon CA AutoUpdate to automatically check and install updates), then the button will be there.

Exact same issue? The usual reason for blacklisted flash drive is the simple one -> it is blacklisted (IE: if you transfer the registration on your purchased .key file to a new flash drive, the original flash gets blacklisted on the next release of unRaid to prevent you from pirating the software and running it on multiple servers while only purchasing it once)

Relatively painless. How I would program it would be as something like "Try It Now". Stop all running containers Start all unRaid managed containers Execute the script to start with the delays, etc. In my mind, you've got to stop everything and then run through the actual startup order for everything to see how it all supposedly works.

The Black / White themes automatically adjust the banner to a maximum width of 1920. The Azure / Gray themes automatically adjust the banner width to your window width. All themes automatically adjust the "main viewing area" to a maximum window with of 1920.

Look up a couple of posts

ok This is now fixed on today's update. It will now find the proper share and check it. Also fixed a couple of other similar edge cases if storing appdata on a UD mounted device.

I'll test CA with that format and update if necessary. EDIT: Tested with plugin Manager and CA autoupdate, and there's no problems with that.

Have you clicked the whale?

Hopefully a real stupid question, but is docker enabled? Even with docker hub searches on, CA won't search docker hub without docker being enabled. This is a search for darco/mfi-controller

docker files from github have to be manually built. But, CA will pull and convert your first one if you search for darco/mfi-controller

In retrospect, I thought that pluginman (at least on 6.3.5) used str_compare. We've had so many discussions on this @bonienl that I can't remember. But you've also got to remember here that we're trying to switch from a version 4.x.x to 2018.x.x version_compare should figure that out (2018 > 4), but str_compare will fail (4 > 2) Net result either way is that only using Check For Updates from plugins works fine either way. Its CA Auto Update that can't make head or tails of a version called 4.x.x because it's extracting a date from the version so that it can automatically delay installing updates for so many days (using date_diff)

Something we didn't consider. 4.x.x is greater than 2018. Plugin manager does a simple string comparision. Guess you'll have to go back to the way things were.

Not quite sure. I just tried it and it worked for me. Try setting static DNS addresses of 8.8.8.8 and 8.8.4.4 in settings - network settings

Well, you did at some point (and recently or added the subfolder to the docker config recently) /boot/config/shares/appdata.cfg exists and is set as use cache no. Nevertheless, the issue is in FCP, and will probably get fixed tomorrow. That test hasn't changed at all in probably over a year.

ok. I see the problem. FCP has been assuming that the default location refers directly to a share, and not to a folder within a share. In this case, it appears that you've also got an appdata share which is set as use cache "no", and since your subfolder off of the Docker share also happens to be the same name as a share it's getting looking at the share settings for appdata, and not Docker. You must've just recently made some changes that triggered this, but I'll update FCP to account for it as there is nothing wrong with your docker settings.