trurl

You could say that Tom IS Unraid.

Do you have any other browsers (including tabs on the same browser, or mobile apps such as ControlR) open to your server?

Check the filesystem on that disk.

I see someone has already volunteered to help you free of charge in PM, but I just thought I would comment on this remark. All of these dockers are provided free of charge. Not every docker is going to have a video created for it. Sometimes you just have to take the trouble to read some things, including that Docker FAQ thread I linked. The Docker FAQ has a lot of general information to try to help you understand how to set up dockers in general. If you understand a few things about docker setup it goes a long way to help you figure out how to use any particular docker. Also, this thread (and all docker support threads) has links in the very first post with more information. You should take the trouble to consult these when you are trying to set up a particular docker. Nobody here is getting paid to help you, nobody here is getting paid to provide these docker applications, and nobody here is getting paid to create videos for you.

Why didn't you say so to begin with. In other words, you are asking a question about Fix Common Problems instead of a question about this docker. Maybe you are on the wrong thread.

If you are absolutely sure you know which drives are parity then you can avoid rebuilding as I mentioned, but the order of parity IS important if you aren't going to rebuild.

If you want to skip the parity rebuild, don't assign any parity until you start the array. Then stop it, Tools-New Config to assign parity, and check the parity valid box before you start again.

One of the things in your old config that you don't want to bring forward is the disk assignments if they have changed since that backup of config was taken. More than one user has started up with an old backup only to find that they have made that critical mistake I mentioned, assigned a data (former parity) disk to a parity slot. Your disk assignments are in config/super.dat, and if you delete that from config before booting it will make you assign your disks. Whether the rest of that old config will be exactly what you need is another question, but you should be able to work through that from the webUI without any data loss. Just one more thing. If for some reason Unraid offers to FORMAT anything, DON'T DO IT! Come back here for further advice.

You could start by telling us which docker you are even talking about, since more than one is supported in this thread.

The very most important mistake you must avoid is accidentally assigning any disk that contains data on it to a parity slot. As long as you don't do that we can work through everything else.

Where is your download folder?

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

I wasn't suggesting that as a fix to be coded, just a work-around using what it currently gives me to work with.

Did you click on that link? Let me give it to you as just a link instead of that embedded snapshot: https://forums.unraid.net/topic/57181-real-docker-faq/?tab=comments#comment-564345 That is the same link, and while it does take you to a post in a long thread, the specific post is telling you exactly how to get us some information that might get us started on trying to help you. The post you gave asking for help doesn't really tell us anything, but if you follow the directions in that post I linked then maybe we can get started. Also, that long thread is a good resource for you even if you don't try to swallow it all in one gulp. A lot of effort has gone into putting a lot of answers in one place there.

That link is broken since the domain here has changed. Here is the correct link: https://wiki.unraid.net/UnRAID_6/Getting_Started

Well, making the empty slots black is closer since the text can't be seen on that color.

Maybe the word "hide" is where the problem lies. I don't mean hide it so that it doesn't take up any space in the layout. I want it to take up space in the layout. I just don't want the border around the rectangle or any contents in it. These are not "Available disk slots" inside my case. I don't see any way to make the override get me where I want to go.

If you have opened ports to your server then you are probably already getting hack attempts from all the bots out there.

This is coming along nicely. One thing I would like is the ability to hide empty slots. In order to match my case layout, I have 7 rows x 3 columns, but there aren't really any bays to fill in many of these locations. Also, I have an SSD as an Auto-Mounted Unassigned Device that doesn't show up for some reason. My 2 cache-pool SSDs are displayed fine. That Unassigned Device is on a USB port if that matters. And I just plugged in another Unassigned Disk to an eSATA and it does show up. So I guess USB isn't supported?

Probably a good idea to always refresh when you switch tabs if you are going to work with multiple pages open to the same server. It is certainly possible this could cause unexpected behavior besides just this incident.

The very first link in the Docker FAQ:

His sig has not been updated, probably since we moved to the new forum software. He probably isn't even aware we have sigs here since you have to enable them in order to see them. Looking at the most recent diagnostics he posted on another thread he is on 6.6.6

See you already got your answer on the CA thread. Everybody can just skip this.

Putting multiple SSD in cache pool is the best way. It is simpler to setup, easier to maintain, and gives redundancy since it will be raid1.

Most people configure things so their dockers and VMs are on cache or unassigned device and not on any array drive. They shouldn't affect parity if you are doing it that way. Do you know which disk your system and appdata shares are on? Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.