trurl

Yes. What you had was creating a folder in RAM named /cache, which of course would not survive a reboot. All of unRAID is in RAM except the mounts.

Not without further information from you. Tools - Diagnostics, post complete zip. Also post your docker run command as seen here: https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

Post your docker run command as seen here: https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

I haven't looked at the diagnostics. You say you checked the permissions, but it is unclear how you checked them. Did you go into console inside the container?

These are hardware errors. Spinning down drives shouldn't cause hardware errors.

Have you tried reseating the controller?

You have a lot more disks than I am inclined to wade through SMART at this point. Maybe you could tell us which 9. What exactly do you mean by "your disks are old as dirt" ERRORS? You do know that reliable reconstruction of a disk requires reliably reading every bit of every disk ( - # of parity)? Are all these problem disks on the same controller? How is your power supply?

Did you look at the github documentation linked in the first post of this thread? It mentions the watch volume. Your docker run command includes a watch volume, with nothing mapped to it. That docker run command is the result of filling in the template when you try to install the docker. And the template includes a watch volume, so you need to map it. Have you seen the Docker FAQ? https://forums.unraid.net/topic/57181-real-docker-faq/

It is basically right there in the error message you're getting. You haven't specified a mapping for the watch folder. Do you know how to use docker?

Possibly an issue with the plugin not supporting your old version of unRAID, I don't know. Also, calling me "Constructor" is like calling you "Newbie". In other words, you aren't addressing my username, just my title.

Which version unRAID? Which browser? Is your server whitelisted?

I apologize if I was a little terse. If you didn't rebuild the disabled disk don't be surprised if you have some parity sync errors.

Not that this helps with your problem, but I thought I would explain a little about the 2 keys. You have 2 keys because there is a separate key file for plus and pro. When you upgraded to pro the plus key wasn't deleted, and that is probably a good thing. Why delete something without warning and take the risk that something didn't go quite right. And FCP warns when you have multiple keys because if you ever need to get a new key for a new flash, it could happen that the wrong key gets replaced. Not sure whether that could really happen with different levels of keys (plus,pro), but probably that hasn't been tested. You can delete the unneeded key yourself. It is on the flash drive in the config folder. Extremely unlikely any of this has anything at all to do with your plex issue. The docker and plex don't know anything about the keys.

+1

Sounds like some sort of hardware issue where something isn't getting re-initialized on a warm start but does on a cold start.

Do you have any adblockers? You should whitelist your server.

Not sure I understand. Of course your server has an OS, unRAID is the OS. And if you boot in GUI mode it even has a browser. But you don't need a browser on the server, you just use another computer's browser to access any app's web interface.

I don't think UD supports encrypted disks that weren't created on unRAID since it has no method to get any key. From the 1st post in this thread:

You should post your docker run command as explained in the very first link in the Docker FAQ: https://forums.unraid.net/topic/57181-real-docker-faq/

Do you have any scripts scheduled with the plugin?

Is it possible you have an adblocker or similar in your browser, and it is just getting tripped up with the new release? You should whitelist your server if you haven't. Also might be worth clearing browser cache since it sounds like this might just be a problem with the UI on your system. Have you tried another browser?

That looks fine, but I don't think anyone suggested that was your problem.

Both of those locations are the same location. cache is part of the user shares.

Your screenshot of volume mappings also says that you haven't mapped any of your media, so even if you get it running it won't be able to access any of your files. Have you read the Docker FAQ?

Why is your docker image 50G? That often indicates a user has been running out of space in docker image due to misconfigured dockers, so they try to fix it by increasing space. Most people never use anywhere near 20G if they have things configured correctly. You also have a surprisingly large number of share .cfg files. Maybe some of these are no longer in use, or maybe you just have a lot more shares than you intended. This can also be a sign of misconfigured dockers.