JMacGill

Thank you all for the help. IDK how to mark this as solved but I'm all good now. Thanks again.

Thanks for all the help so far. One last thing. How do I get the drive back online if it is ok? It still shows a red X next to it.

It took many hours but I did a SMART test. Here is my new diagnostics. unraid-diagnostics-20211205-2244.zip

Here is my diagnosticsunraid-diagnostics-20211204-2021.zip unraid-diagnostics-20211204-2021.zip

I was swaping out an 8TB drive for a 10TB one after I had just spent 4 days upgrading my two parity drives (from 10TB to 18TB). Within the first hour of the rebuild, drive 5 was taken offline and emulated while the rebuild continued. I decided to just cross my fingers and let the rebuild finish and hope that nothing else went wrong. Because I have two parity drives and two drives were being emulated at the same time, am I safe to assume that the rebuilt data should still be good? I'll include my log file if it helps. unraid-syslog-20211204-2240.zip

Thanks. I didn't know about this. I was wondering what was up.

What version of PlexPass Server is your docker currently on? Mine has been on Version 0.9.17.0 and it still says it's up to date when I check for docker updates. same with all your other dockers I use. I haven't had any updates listed for about two months now.

Version 0.9.16.3.1840-cece46d was released two days ago on Mar 21, 2016. Any word on when the update will be available for your Docker container? edit: It's been a week now and Docker is not showing an update available but Plex web has been telling me about the update for days. Is my Docker not working or is the update still not available for your container?

Are you running the 6.1.9 version of unraid, if not upgrade the plugin as mine did this before I was already running 6.1.9 but I got it to come back by just re-adding the container back from the '"My containers" section. All the settings were still there and Plex works.

I just upgrade to the latest version today and after the upgrade the server disappeared from Docker and is no longer there.

This would be achieved using a specific tag for the version of deluge you want to use, unfortunately i dont have tags that go that far back so for now i can only offer you deluge 1.3.12, im assuming then they only support deluge 1.3.11 or earlier? Correct, they list 1.3.1, 1.3.5, 1.3.6, and 1.3.11 as supported, but not 1.3.12

Is there any way to specify which version of Deluge is installed with this Docker container? I have an IPTorrents account which I currently can't use with Sonarr because of their strict rules on what torrent clients can be used with their tracker and I can't figure out how to install older versions of programs when using their Docker versions.

Hello, this is my first post. I just bought unRAID exactly two weeks ago on the 14th and finally finished setting up my server hardware. I ran into a few problems and learned a few things but I was able to figure them out by using Google. My current problem is not unsolvable. I already found the topic covering it here http://lime-technology.com/forum/index.php?topic=38323.0. What I would like to know is why this happened. I just bought, installed, and setup unRAID and in that time there was one update the very day after I bought my key. I never ever installed a BETA version of unRAID yet I'm getting this error at the top of my docker page: Your existing Docker image file needs to be recreated due to an issue from an earlier beta of unRAID 6. Failure to do so may result in your docker image suffering corruption at a later time. Please do this NOW! Why am I getting an error from a BETA that I never had? From some early Googling it looks like the error comes from moving the Docker image between the cache to the array, which I did do while upgrading my cache disks to larger sized SSDs. I turned off all my Docker containers before doing the move and restored the image to the cache before turning the containers back on but I see now that I did forget to turn off Docker before moving the image file. Would that have prevented this problem? Also, if this was a problem in an earlier BETA version wouldn't it have been fixed before releasing a final version of the OS to the public. And if not then wouldn't this issue not be from an earlier BETA but from the very version of unRAID that I have installed?