trurl

Something is filling rootfs, probably the cause of your upgrade problem also. What dockers do you have?

I'll let someone else comment on WOL plugin, but what do you mean by the above? Do you mean that you have installed every single one of the packages in Nerdpack? It is probably a bad idea to randomly install a lot of things that you don't know what they are and aren't going to use. I recommend only installing packages that you know what they are and that you actually intend to use.

Possibly the rebuild will be bad anyway even if you let it complete, due to read errors on the other disk. Probably was a bad idea to try to rebuild a disk with another known bad disk in the array. We really need the diagnostics, or at least the SMART for all disks and syslog. Diagnostics is the simple way to get those but if you can't get diagnostics then try to get syslog and SMART for each disk.

New Config will be the way forward but just to make sure we aren't missing something, Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post

Is it available inside your network?

Your appdata and system shares have files on the array, and they are set to cache-yes. The correct setting for these is cache-prefer, or even better, cache-only. You don't want your apps on the array. Their performance will be degraded by the slower parity writes, and they will keep array disks spinning. Also, many people have reported SQL corruption with various dockers on your version of Unraid. This appears to be fixed on the current release candidate. Something that appears to help with the version of Unraid you have is to specify the disk path for appdata, instead of the user share. So, /mnt/cache/appdata instead of /mnt/user/appdata. Whichever version you decide to try, you should set system and appdata to cache-only. Then disable the docker service (Settings - Docker), delete the docker image, and recreate it so it will be on cache where it belongs. Also delete your appdata so it can be recreated on cache where it belongs. Since you have such a small cache drive, I recommend moving all your other user shares from cache to the array, then setting them to cache-no, and reserve your cache strictly for the system (docker image) and appdata shares. Do you have any VMs? Possibly you have allowed your libvirt image to get onto the array as well since it is also in the system share. You should also fix that.

Also, in future please attach to your posts instead of linking to external sites.

If you did in fact start from scratch by deleting plex appdata, then possibly you have other things wrong with your system. Or possibly you are just getting new corruptions on a new database. Either way we need more information. Post your docker run command as explained here: https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345 and post your diagnostics. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

If you deleted the plex appdata then the database would be gone. Did you? That is normally what would be meant by "starting from scratch".

I see you have a sig left over from before. You may not be seeing it because unfortunately the default in this forum software is to not display sigs. You can enable viewing of sigs by clicking on the dropdown next to your user name in the upper right, and selecting Account Settings. You can also update your sig there, looks like it probably needs updating since it says you are on V6.2. If that really is the version you are using then you need to update your server.

According to your profile, you joined 3 years ago. That would have been before our current forum software. Not sure when we began requiring approval of first posts to keep out the spammers but it may have been around then. If you never posted then you weren't approved for posting. I don't see any other posts from this account. Were you using another when you posted a week ago? Do you mean you see later posts from another account you used, or do you just mean later posts by other users? We are a very active forum and probably have 100 or more new posts every day.

Until I approved your new account, you were only allowed one post per day.

And the 1 parity check (in step 4) is actually optional. It is very different from what you posted. If you aren't sure you understand please ask more questions. Or if you have any problems while following itimpi instructions, please come back for further advice. DO NOT FORMAT any disk in the parity array.

No that won't work. Is there data on the current cache that you want to keep?

Is this supposed to be an answer to my question? It often helps if you quote the person you are responding to, or at least mention their name. OP usually means the Original Poster. If that is what you mean by "op" then your question is even more confusing.

Who is this question directed to?

You are using 21G of 30G in your docker image. I always recommend only allocating 20G for docker image. Have you been having problems filling it up? Making it larger will not fix that problem, it will only make it take longer to fill.

Doesn't help at all. Still need Diagnostics and run command. That is not the run command. See the very first link in the Docker FAQ for instructions on getting the run command.

Cache- yes is not cache only. There are 4 possible settings for Use cache. Since you have been using the wrong setting, it will likely require a few steps to get your set up working more efficiently. Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post.

I think that mistake is caused more by people not understanding the word "format", a word that everyone seems to think they understand, but really have no idea of what happens specifically. "Format" doesn't mean "get this disk ready to use (again)", whatever that might mean exactly. Format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used. Unraid treats that write operation just as it does any other, by updating parity. So after formatting a disk in the parity array, parity agrees the disk has an empty filesystem, and rebuilding a formatted disk from parity will result in an empty filesystem.

Post diagnostics and docker run command.

In future, please ask on the forum before attempting to make any changes of any kind (add, remove, replace) in your disk assignments. If you understand how parity works, and if you understand what format does, then you can figure these things out for yourself. But it seems most people don't even know what format does, much less how parity works.

Give us a screenshot of what it shows when you click MORE>