trurl

You should start your own thread and post your diagnostics instead of hijacking this one.

Seems unlikely the application would have done that, but if it did then the application website might be a good place to ask. This is just the support thread for setting up the application in docker.

Do you have a backup of appdata?

Can you simplify by eliminating this from the setup?

If your appdata is going to live there why don't you have it set to automount?

We never got anything further from that user. Perhaps he didn't have his Unassigned Device mapped rw,slave. So, as you can see, not exactly the same. It is telling you the Unassigned Device you are using for your appdata is full.

You can have a maximum of 2 parity drives. Each parity disk must be at least as large as any single data disk.

Was this a "clean" install? No addons from V5 are compatible. There are some other things you might want to do now that you are on V6. Even without dockers and VMs there are definitely some plugins that you can run and are considered indispensable, Community Applications should be first, and then it will let you install others. Unassigned Devices is something you will probably want. If you want more advice go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

Why do you have SSD in the array? SSDs in the array are not recommended. They can't be trimmed, they can only be written as fast as parity, and there is some question whether some models may invalidate parity. Looks like you have your router as DNS. Are you sure it isn't a problem there? Did you try this?

2G RAM is pretty much the minimum now, and will only support basic NAS functionality. So can you access your data?

All of your data on disk1 to start is typical with the default High-water Allocation Method. Your docker mappings say you have all your downloads going to Unassigned, but I notice you also have a cache-only user share anonymized in the diagnostics as d-------s. Possibly this is where you were downloading before you switched them to Unassigned. That user share is cache-only, but all its files are on disk1. Mover ignores cache-no user shares. I am guessing you don't really want those moved to cache but you might reconsider the Use cache setting for that share since it doesn't make any sense as it is currently. Something that you should definitely reconsider is your system user share. That is where your docker image is, which contains the executable code for all your dockers. Your system share is cache-yes and all on the array. Ideally you want the system share to stay on cache so your docker performance won't be impacted by the slower array, and so they won't keep array disks spinning. That share is cache-prefer by default, but now that you have it on the array it will take a few steps to get it moved to cache where it belongs. Other than that I don't see anything. Disk1 will continue to be used until it gets to the High-water mark, half-full.

Usually caused by bad connections or cables. It basically means the data became corrupted between the disk and the rest of the system. New diagnostics might give some clue assuming you haven't rebooted.

The webUI, along with everything else in the OS, is in archives on the flash drive. There is no way to delete just part of that since it is not separate files. Have you tried putting your flash in your PC and letting it checkdisk? While in your PC, copy the config/go file and post it. Do you have a backup of flash or possibly a download of V5 yourself that you may have kept? Probably your data is safe, since each disk can be read individually on any Linux. How important is that data to you? Maybe moving forward to V6 will be the best thing, but it may take some effort and possibly expense if your current hardware isn't up to the task. How much RAM do you have?

And in fact, it isn't really possible for Unraid to guarantee a certain amount of unused space. It doesn't know in advance how large a file will become when it chooses a disk to write it to.

I have responded on that thread.

This makes no sense at all because of how Unraid actually uses the Minimum Free setting. It is all about allowing a disk to be chosen for writing a file, not about keeping a certain amount of space unused. itimpi already explained, but here is an example: Minimum Free is set to 10GB. A disk has 11GB free. That disk can be chosen for a new file because it has more than minimum. A 9GB file is written to the disk. Now it has only 2GB remaining, which is less than minimum, so the disk won't be chosen again. But note that the disk winds up having less free than the minimum. It has nothing to do with keeping some of the disk unused.

There is a docker for a lot of things. I don't even run any VMs because dockers do everything I want my server to do.

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

You can go directly to the correct support thread for any of your dockers by simply clicking on its icon and selecting Support. The original poster on this thread already found that support thread and posted on it here: https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=821007

No reason to do that. Everyone runs Plex as a docker on Unraid. If you haven't already, install Community Applications plugin: https://forums.unraid.net/topic/38582-plug-in-community-applications/ Then go to the Apps page to install other plugins and dockers. There are currently 772 dockers and plugins for Unraid listed there.

All you need is the config folder on a new install.

Was this a new install on your current flash?

Do you have an attached monitor and keyboard?