trurl

Your use of the device identifiers sdd,sde is not generally useful, since these are not necessarily the same from one boot to the next. Unraid identifies disks by their serial number, Is one of the Unassigned Devices your former cache disk? Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

And you would set it to be larger than the largest file you ever expect to write to cache, similarly to what you would set it to for a user share. It is perhaps even more important that you don't allow your cache to fill as that may corrupt docker image, appdata, or anything else you have that lives on cache. Min Free on cache will only have an effect on cache-yes or cache-prefer user shares, where it will cause additional files to overflow to the array.

You have to create a mapping for your media. See the Getting Started section of the Docker FAQ: https://forums.unraid.net/topic/57181-real-docker-faq/

The Add Container page seems to be what you are talking about. After you select a docker from the Apps page you are taken to the Add Container page and are no longer in CA. The Add Container page is builtin and not part of the Community Applications plugin.

Only Administrators work for Limetech (Unraid). Everyone else you encounter on this forum are just other users like yourself, some of whom dedicate some of their free time to helping others, including creating addons for Unraid. Often they don't get the appreciation they deserve.

If you get that problem on a clean install, then that suggests you have a problem with plex, not a problem with reusing a previous library. I don't see how that could be a problem. It would just mean that plex.tv wouldn't know about that server. I don't think it should be a problem creating a new server at plex.tv I don't specifically remember removing any, but I probably have, since I have had plex server on a number of different platforms over the years, and the only plex server I currently have is the one on my Unraid (and it was originally a needo docker as you know). If you are still in doubt, you might see if anyone has anything to say about removing a server over at the plex forums.

But as long as you're keeping an eye on it that's fine. Some people "set it and forget it" and never know they have a problem until they get multiple problems and then come here hoping we can save their data.

You can configure which notifications you get, and even configure each disk separately for what gets monitored.

And speaking of recovering disks, you have a couple that should be showing you SMART warnings on the Dashboard. Do you have Notifications setup to alert you immediately by email or other agent when Unraid detects a problem?

Since you have unresolved and recurring hardware issues, I have to ask: Do you have another copy of anything important and irreplaceable? Parity is not a substitute for backups, and invalid parity as you seem to often have is definitely going to be a problem if you do need to recover a disk.

Also, on the Settings - Docker page, turn on log rotation.

Delete docker image, recreate it at 20G, and reinstall your dockers using the Previous Apps feature on the Apps page. They will be exactly as before. But exactly as before may be wrong in some way. The way you fill docker image is by having one or more applications writing to a path that is not in mapped storage. Common mistakes are using the wrong upper/lower case and using a relative instead of an absolute path (beginning with / ).

Also, your docker image is 40G and already 22G is used. If you have your docker applications configured correctly it is extremely unlikely you would ever get close to using even 20G, and I always recommend people only have 20G for docker image just so it will fill up sooner and they will know they have something misconfigured. Since you are trying to transcode to a folder mapped to /tmp, possibly that is where you are going wrong. Have you actually set Plex to transcode to /transcoding_directory?

Have only looked at syslog so far, but do you have an explanation for all the parity errors you are getting with the parity check?

Unlikely that faulty memory would be the cause, but can't hurt to check. Reboot and select memtest from the boot menu and let it run for at least one full pass. Then reboot in SAFE mode, disable Docker and VM Services, and try parity check again.

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post. Also post your docker run command as explained here: https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

Ultimately, the Unraid webUI is just executing docker commands. You can get help with the docker commands at the command line with docker --help. I think you just need to remove the docker and run it again using the correct repository and mappings etc.

At the bottom of the Add Container page. Click on the "+Add another..."

What happens if you do a parity check with no dockers running?

Post diagnostics. If the webUI won't let you get them you can try to get the from the command line as explained here: https://forums.unraid.net/topic/37579-need-help-read-me-first/

You need to make sure it only has one partition but the /dev/sdx designation has nothing to do with it. Are you having a problem, or were you just trying to add to the discussion?

We don't get any training😄 Merge seems to work exactly backwards to what you would expect. I usually use Split instead to select specific posts and split them into a new thread or into another thread. But in this case, I wanted to take the whole thread and merge it here. I started from the thread the other user created, selected Merge, and gave it the URL for your support thread. You would think that would mean merge that thread into yours, but apparently not. I think this may be exactly how we lost the Docker FAQ back in the early days of this forum software. I later found it in some other thread that was several pages down into the forum. Ironically, I had replied to that other user telling them how to get to the correct support thread for their Docker.

Have you tried this:

If it seems to be going wrong try to get another diagnostic. If you look at Main - Array Devices, it should have a lot of writes to parity, a lot of reads of all other disks, and zero errors on all disks.