trurl

That looks much like what you had before. All OK except system share still has files on disk1. From the command line, what do you get with these? ls -lah /mnt/cache/system ls -lah /mnt/disk1/system

If you are interested in learning a bit more about what is going on under the hood, open your diagnostics. It is all text files (except one). There are logs, there are SMART reports from all attached disks, there are the results from numerous commands that give some details about your hardware, and there are .cfg files that are your settings from the webUI. Those .cfg files are taken from your flash drive.

From Unraid, your flash drive is at /boot. If you have your flash drive shared on the network, you will see it as flash

On the flash drive, in the config/shares folder, are .cfg files named for your user shares. Each of these contains the settings for that specific user share. You have a lot of those .cfg files that no longer correspond to any of your user shares. If I open each of those in the diagnostics it will tell me whether or not it has any files, but that is a lot of trouble when you have so many of them. It makes it very difficult to get any idea what user shares you actually have.

It isn't stuck there. You can reconfigure things so it gets moved, but why do you want to? appdata, domains, and system shares are better left on cache so your dockers and VMs performance will not be affected by the slower parity writes, and so your dockers and VMs will not keep array disks spinning. Since it sounds like you have made some changes since those diagnostics you posted earlier, post new diagnostics so we can see what your current situation is.

You should post your diagnostics. You may have some configuration issues that is causing these problems and they will return. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

Dual parity makes more sense after your drive count has increased to quite a bit more than just 2 data drives.

Do you have Notifications setup to alert you immediately by email or other agent as soon as a problem is detected?

The first one is telling you exactly what to do. Here is a FAQ with more details: The second one is the problem we supposedly already fixed in this thread just a few posts above. Post new diagnostics so we can get a better idea what you might have done. The third one is telling you exactly what to do. No idea about the fourth one. Maybe with diagnostics someone else will have an idea. The fifth one is telling you exactly what to do.

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

Are all your plugins up to date?

I have deleted all of those files you went to all that trouble to attach. It would have been even more tedious for those of us who might help you to download them all separately and open them. The Diagnostics you get from the webUI is a single zip file. You should attach that single zip file unaltered. If you think it gave you a lot of separate folders and files, it is because your PC and its browser is configured to automatically open zip files. Find the single zip file you downloaded in the usual place for your downloads, and attach that to your NEXT post. Help us help you.

Yes. Just compare the names with your current share names. If you have some with the same names but different upper/lower case, put those names in a post and I will take a closer look. Even if you accidentally delete a .cfg file for a share you already have, the share will still exist because its folder exists at the top level of one or more disks. But if it doesn't have a .cfg file it will have default settings until you change them, and changing the settings for a share will create or modify the .cfg file.

USB connections aren't reliable enough for dedicated use in the parity array or cache pool.

You still have a lot of unused config/shares .cfg files that makes it difficult to see which shares you still have. Maybe a screenshot of the User Shares page for future reference as you progress?

Docker image doesn't look full in those diagnostics now, but are you sure you didn't fill it? Since the appdata for a container contains the settings for that application, such as paths, it is certainly possible that the appdata contained incorrect settings, or maybe was missing some settings, that would cause you to fill docker image. Did you check the settings for the applications before you used them again?

If by device ID you mean sdg sdh that is not guaranteed to stay the same after reboot. In fact, with removable drives it is very likely to change when you plug them in again.

It is, as is the new thread you started in General Support. But I replied to that thread with advice on how to find the correct thread.

You can go directly to the correct support thread for any of your dockers by simply clicking on its icon and selectint Support.

👍

Is it exactly the same problem with the same messages filling your log? Or do you just mean your log space is filling up? Start your own thread with your diagnostics if you want us to take a look.

Among the services it is starting are the SMB protocol, which is what allows your Windows computer to see files on the server. Normal.

I assume you mean you did all this after you posted the diagnostics. And probably you mean you have set all of the other shares to cache-no. Mover won't move cache-no shares, and as explained, you don't want those moved. Set appdata, domains, and system back to cache-prefer or even cache-only.

Your appdata, domains, and system shares are supposed to be on cache, and they are on cache (except some of system is on the array as noted). Those are set to stay on cache, they are supposed to stay on cache as explained, and you don't want them moved from cache. These are the only shares still on cache. Your "M---" share is set to cache-yes, and it has all been moved to the array. Sorry if I have mostly just repeated what was already said, but this is the way you have it set up, this is the right way to have it set up, and it is working as intended. Except you need to get rid of the duplicate system files on disk1. You can see how much of each disk each user share is using by going to Shares - User Shares and clicking Compute... or use the Compute All button.

Video doesn't seem to work. But from your description it sounds normal. You start the array and it takes a short time before it is completely finished starting. Or, at least, there are some "services" that also have to start after the array is started, such as SMB which is the protocol you are probably using to access your shares over the network.