Hello! Sorry for my English. Over the past few days I have been trying to optimize my system. Because I'm new to this business, I configured the Share incorrectly from the very beginning. As a result, these Share ended up on different disks. I tried to move the files and share from one drive to another. That is, I made a lot of mistakes, as I found out later that you can not copy from Share to disk and vice versa. I used the cp and mv commands to make it all work. For example, the Media folder had multiple copies on disks 2 and 3 (because disk 2 ran out of space). I moved both folders (which are Share) to 1 disk. Please see pictures. And so I did for all Share. Now it is not clear yet whether I have lost the information or not, but I cannot enter any container: a connection error. So my question is how to re-install system to fix all my possible troubles which I will know and will not know and of course save data. Please step by step if possible.

 

P.S.: What are the user and user0 folders in the lowest picture? They have the same content.

Edited April 22, 20224 yr by bombs1ght

Attach Diagnostics to your NEXT post in this thread 

18 hours ago, trurl said:

Attach Diagnostics to your NEXT post in this thread 

Please see attached file

tower-diagnostics-20220423-1947.zip

It isn't necessarily important which disks are used by each user share, since you shouldn't be accessing the disks anyway and only accessing the user shares.

 

The main thing I see is you have no fast pool (cache). Even if you don't intend to cache user share writes, your Dockers/VMs will perform better if on fast pool, and won't keep array disks spinning since they always have open files.

10 hours ago, trurl said:

It isn't necessarily important which disks are used by each user share, since you shouldn't be accessing the disks anyway and only accessing the user shares.

 

The main thing I see is you have no fast pool (cache). Even if you don't intend to cache user share writes, your Dockers/VMs will perform better if on fast pool, and won't keep array disks spinning since they always have open files.

I see. Thanks you! Only one more question please. I would like to merge the system, appdata, isos, domain folder into one Share to have fewer directories in the Share tab. Is it possible to do so? In addition to the fact that I automatically get the same Share settings for all these folders, which is acceptable for me, can there be any other nuances?

Edited April 25, 20224 yr by bombs1ght

Looking at my simple Unraid setup, I can see one problem.  In the Docker configurations, the path to   appdata    is hard coded as    /mnt/user/appdata/binhex-krusader

 

If you move this directory, you will have to edit any and all of these hard coded links.  I suspect that many of the other directories, that you want to move into System, will have the same issue.  This should be a fixable problem but be aware of it before you start.

5 hours ago, bombs1ght said:

merge the system, appdata, isos, domain folder into one Share

I think it makes sense to have these separate for a few reasons.

• You will want to backup appdata separately. libvirt.img in system should also be backed up. CA Backup plugin will take care of these. But there is no point in backing up docker.img, and if something goes wrong, often we will recommend deleting and recreating it by reinstalling your containers using Previous Apps.
• isos doesn't necessarily need to be on fast pool since these files may not need to be open after they are used for VM install.
• domains may not fit on fast pool depending on how you use vdisks in your VMs, but note that VMs can access your Unraid shares so it often isn't necessary to have large vdisks. You will also want a backup strategy for your VMs separately from the CA Backup plugin.

It would be possible to put all of these under one share, but you need to be aware of all the paths that reference these shares and update them wherever they exist. In addition to what Frank1940 said, each of these shares were created due to the Settings you have in Docker and VM Manager.

 

Since you don't often need to access these shares, no need to share them on the network. I share them private so only I can access them, and hidden so nobody sees them, I have to enter their share path to access them on the network. I do the same with the flash (boot) share.

 

 

Thanks you for your answers guys!