trurl

Changed Status to Closed

Did you create the network?

I always say it's just one day older than yesterday.

I remember turning 50. It was relatively painless.

It is unmountable. Use the -L switch.

No. Please read that wiki again. You must repair the md device for a disk in the parity array, or you will invalidate parity.

Do you know how your cache pool was configured?

yes, but

no Were you following these instructions? https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui You should capture the output from filesystem repair so you can post it if you have questions.

New Config will only (optionally) rebuild parity. If you think parity is already valid then you can check a box when you go to start the array telling it parity is valid and it won't even rebuild parity. No other disk will be changed in any case. The reason for the warning is because if someone has a data disk that needs to be rebuilt, then doing New Config makes it forget that data disk needs to be rebuilt. The main danger from New Config is accidentally assigning a data disk to the parity slot, thus overwriting that data with parity.

You have 2 very different sized disks in cache pool. The default btrfs raid1 will give you a mirror, but with total capacity only equal to the smaller of the 2 disks, so you only have 250G capacity in cache the way it is currently configured. Cache pool does appear to be mostly empty now. Before going much further with setting things up again, you might want to reconsider your cache pool configuration and how you would like it to work. See the Cache Pool section of the FAQ for more: https://forums.unraid.net/forums/topic/46802-faq-for-unraid-v6/?page=2&tab=comments#comment-554741

Can you elaborate?

In Settings - Docker, Advanced View. Do you have Preserve user defined networks turned on?

Have you read any of the Docker FAQ? What Network Type are you setting for the dockers? Host Network Type will not work if you need to map the container port to a different host port. Lots of people are doing this successfully.

If you pass the entire drive through, I think you would have to see if you can map it as a network share in Unassigned Devices, since Unraid can't use the drive if you give it to a VM. Are you sure you even need a VM? There are a lot of dockers that people use for downloading.

I actually asked for the docker run for plex. But I can see from the one you posted that you must not be doing anything right. It is even telling you what the problem is. Remove all your dockers. After you remove all your dockers, go read all of the Getting Started section of the Docker FAQ: https://forums.unraid.net/topic/57181-docker-faq/ After you have finished studying that, let us know and we will work on a single docker and see if you can get it setup correctly.

For starters, the usual Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

I don't actually use any VMs, but are you sure you can even do it that way? Don't you at least have to specify a partition?

That is not enough information for us to guess whether or not those are the same thing.

I don't use qbittorrentvpn myself, being already familiar with transmission. One thing I notice in your screenshots though, is that your plex doesn't have any mapping for any of your media. That shouldn't really cause the connection refused, but it does mean plex wouldn't be able to access anything on your server even if it was running. Maybe we can try to work through setting up your plex docker correctly and go from there. Post your docker run command for plex as explained in this very first link in the Docker FAQ:

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

Mover is really intended for idle time. There is simply no way to move from cache to the slower array as fast as you can write to cache. Doesn't matter how often you schedule mover, and if mover is trying to run at the same time as things are writing to your server, it is just going to be competing for those resources. Our hardware is very fast these days, but our data is also very large, so things seem to take as long as they always did.

There is obviously a disconnect somewhere. If it isn't on the Unassigned Device, then your VM must not be looking at the Unassigned Device.