trurl

You can get to the correct support thread for any docker by clicking on its icon in the webUI and selecting Support.

Probably not directly related to your problem, but the Use cache setting for some of your shares may not be what you intend. You have some shares set to cache-no but still have files on cache. Mover only moves cache-yes shares from cache to array. It ignores cache-no and cache-only shares. And you have some shares besides the usual (appdata, system, domains) set to cache-prefer. Mover moves cache-prefer shares from array to cache. People are often confused by these settings so just thought I would mention it.

https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

You may have issues that go beyond the purpose of this thread. I will split it out if appropriate. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

Post your diagnostics.

V6.5.3 is still available, but I think it is more likely a coincidence that you began having problems when you upgraded. Lots of people successfully using Plex with the latest versions of Unraid.

What plugin is that? There was a plugin way back in Unraid V5 by that name, and it had a similar purpose to Unassigned Devices. Surely that isn't the plugin you mean is it? You shouldn't be using any plugins that aren't available on the Apps page. Perhaps this was a typo. There is a SNMP plugin. Is that what you were referring to?

Easy enough to test. Downgrade Unraid.

When you edit a docker it reinstalls it. Only its appdata persists. There is a separate handbrake docker.

This has nothing at all to do with Unassigned Devices. I recommend you set this back to Auto. You can get yourself in trouble working directly with the assigned disks.

I have merged your threads. Crossposting has been considered a bad thing on message boards since long before the world wide web. How are we supposed to coordinate our responses when you do this?

Yes the reported size is wrong and a known issue. You don't mention how you have cache pool configured, so I don't know if the answer you gave here is right either. The default configuration of raid1 would only give 512GB for those 2 disks. raid0 would give that answer of 1TB. But there is a way to get the 1.5TB total capacity of the disks if that's what you want. See the Cache Drive/Pool section of the FAQ: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?page=2&tab=comments#comment-554741

yes

It's a dropdown because it's a choice you can make. The plugin actually installs a customized version of Unraid, whichever version you choose from the dropdown. It is simply the Unraid version you choose with support for NVidia added to it.

rar and unrar are in the Nerd Pack.

That would be a first step. I've not used that software myself. I don't know if it writes to the disk or if it tries to extract the data to some other location. If it alters the disk contents in any way then you won't be able to put it back in your server without rebuilding parity. Do you have backups of anything important and irreplaceable? Many of us don't have the capacity anywhere to try to backup our whole server, but you should have another copy of anything important and irreplaceable. You get to decide what qualifies. Parity is no substitute for backups, as you have seen.

You don't. You would have to use it in another system. Have you been to their website to see about that software?

Parity has no data. It only allows data to be reconstructed from the parity calculation using the bits on parity together with all the bits on all the other disks.

Starting dockers from a script isn't the way it's usually done in Unraid. We have a user interface that allows you to fill in all the parts of the docker run command using a web form. In addition to making it easy to run the docker, that same web form saves the entries to make it very easy to start the docker again, reinstall the docker, or even edit the entries to change the docker run command. You can even specify an icon and other things for the container so it all integrates very well into the Unraid webUI.

Format is a write operation. It writes an empty filesystem to the disk. When you perform any write operation in the parity array, Unraid updates parity at the same time. So after a format of a disk in the parity array, parity agrees that the disk has an empty filesystem. So no, there is not. There are prominent warnings in the webUI to try to prevent you from making this mistake. We would have given you different advice about how to repair an unmountable disk if you had asked us before doing anything. If the data was very important, you might be able to recover some of it with some third party software, such as UFS Explorer. Obviously you should not write anything to the disk if you want to have any chance. If you want additional advice about how to proceed with your existing setup, let us know what you want to do, and go to Tools - Diagnostics so you can include the complete diagnostics zip file attached to your next post.

I do use Unassigned Devices but don't understand what your question has to do with that statement it is in reply to. Just to break it down a bit. A cache-no share means a User Share that is set to Use cache disk: No. User Shares do not and cannot use Unassigned Devices. A User Share with only one included disk means its Include setting only allows one specific array disk to be used.

Why have you replied to that nearly 2 year old post? That user hasn't even visited the forum in nearly that long. The main reason I ask is because I had to approve your account. Making random replies to very old posts is an odd way to begin your life on the forum. We get a lot of spammers but so far you seem legit. Welcome!

Not only is it easier, but it also makes it possible to easily reinstall it with the same settings. Or are you actually trying to use this docker in some environment other than Unraid? Now that I look more closely at your volume mappings, I assume that must be the case.

Might be something about how you have this docker setup, or it might be something about how you have your user shares setup. Or both. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

Another thing to consider in the case of torrents. If they are on the array, parity is only involved when you are leeching (written). Parity does not get involved when you are seeding (reading). I have mine on a cache-no share with only one included disk. Since I am not that concerned with how fast they are written I don't care about how parity affects their downloading speed (it probably doesn't). They are protected by parity and can stay there seeding as long as I want. If you have torrents seeding from cache, mover may not be able to move them to the array since it can't move open files.