shares gone after adding cache drive

[James_Darkness]

my dockers don't work and my shares are gone all i did was add a cache drive

[itimpi]

1 hour ago, James_Darkness said:

my dockers don't work and my shares are gone all i did was add a cache drive

You are likely to get better informed feedback if you post your system’s diagnostics zip file. 

[James_Darkness]

56 minutes ago, itimpi said:

You are likely to get better informed feedback if you post your system’s diagnostics zip file. 

thank you, after a reboot i got my shares back but my docker wont start. i did edit the docker.img settings and nothing

unraidnas-diagnostics-20220406-2340.zip

Edited April 7, 2022 by James_Darkness

[ChatNoir]

1 hour ago, James_Darkness said:

my docker wont start. i did edit the docker.img settings and nothing

Looks like your docker image is corrupted.

Apr  6 23:31:32 UnRaidNAS root: mount: /var/lib/docker: wrong fs type, bad option, bad superblock on /dev/loop3, missing codepage or helper program, or other error.

 

You will need to delete and recreate it, then reinstall your containers from Apps, previous apps.

[ChatNoir]

You should also move your appdata, systems and domains shares to your cache. Files are all over the place.

Ideally before step 5 of the FAQ above.

[itimpi]

I also note that that the docker.img file is explicitly set to be on disk1.   Normally you want it to be on the cache to get better performance from your docker containers.  
 

It is also set to be 100GB which seems excessive.   The default of 20GB is enough for most people unless you have a lot of docker containers.  Is there a reason you have such a large size?   If you find you are filling that up when docker containers are running you may have a docker container mis-configured to write into the docker.img file when it should be mapped to use Unraid storage external to the containers.

[ChatNoir]

1 hour ago, itimpi said:

If you find you are filling that up when docker containers are running you may have a docker container mis-configured to write into the docker.img file when it should be mapped to use Unraid storage external to the containers.

If that's the case : https://www.youtube.com/watch?v=9DxPEfbAJJ0

[James_Darkness]

On 4/7/2022 at 1:24 AM, itimpi said:

I also note that that the docker.img file is explicitly set to be on disk1.   Normally you want it to be on the cache to get better performance from your docker containers.  
 

It is also set to be 100GB which seems excessive.   The default of 20GB is enough for most people unless you have a lot of docker containers.  Is there a reason you have such a large size?   If you find you are filling that up when docker containers are running you may have a docker container mis-configured to write into the docker.img file when it should be mapped to use Unraid storage external to the containers.

thank you after deleting the img file from inside the docker setting docker is working and I'm redownloading everything now. i also changed the size to 20gb

 

one more thing my server is running very slow and buggy so i looked at my logs and its filled with this 

Edited April 12, 2022 by James_Darkness