And no, don't be worried. The message is more about if you have multiple .key files (for different servers) all stored on the same usb stick (previously a very common occurrence for people with multiple servers)
Install the auto update plugin (whether enabled or not) will patch the OS to fix this caused by a change at dockerHub Sent from my NSA monitored device
If the LSI bios doesnt see the drives then you're probably using the wrong cables (reverse breakout) you want forward breakout Sent from my NSA monitored device
Not that I'm the one to help, unless the problem is obvious, but at the very least, you're going to have to post the docker run command, and a screen shot of whatever the error is...
Oct 14 15:45:23 Tower root: plugin: installing: /boot/config/plugins/dynamix.s3.sleep.plg
Uninstall the plugin if you don't want it to sleep...
BTW, always post diagnostics instead of just a syslog. Makes life easier for us
Do you have a cache drive? This implies that you've set your appdata to be cache-only (which is possible if due to a misconfiguration of an app it created a cache folder), but you don't actually have one. Post your diagnostics.
You can't tell from the diagnostics, but if you a schedule set for unRaid to check for plugin updates, then it also checks every time you hit the Plugins tab. If you disable the schedule, then the plugins tab will have a manual Check For Updates button
Ok. Probably because the tag that sets the minimum version required by the plugin wasn't present in 6.3.5
But, I can guarantee that a scan will not work from its UI background scans probably will.
The changelog in the plugin is the censored version. The commit history on Github for all my plugins tend to have more swearing in them 😉