Hi,

 

I'm in a bit of a pickle that I don't know how to get out of. Kinda wish I could go back to initial default docker config or perhaps do clean install of Unraid and restart from scratch. Not sure if that's an option at this point.

 

I don't even know how to explain my problem...

 

Some years ago I had an issue with permissions in the appdata folder which I "solved" by not using the default path /mnt/user/appdata (maybe because of the cache) but instead used the direct path to my nvme drive (/disks/Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M532569N/Docker/appdata), wich probably was a stupid fix but it worked at the time.

Now, as I am spring cleaning on the server, I would like to migrate everything to the correct location, but I am getting confused by the multiple appdata folders that exists on the system now for some reason. Some are probably links, virtual or direct paths?

 

Anyway, as I did a migration today, to what I though was the correct folder (/mnt/user/appdata), got everything up and running and then ran the common errors scan and got this:

- Default docker appdata location is not a cache-only share

- Invalid folder appdata contained within /mnt

 

As I check the shares it seems the appdata is now spread across multiple drives in the array instead.

I have a cache drive designated (a 256gb sata ssd), but I don't really want to use it for docker purposes as I feel it adds a layer of complexity and confusion that I don't need.

I am not sure why docker started using the cache as it was not setup to use it from the beginning. It was only supposed to be used as a cache for the array at the initial copy from the older server over the network.

 

So, what I would like to do is,

1. I would like all "Appdata" to run directly from my nvme (the samsung above) where my docker.img is located, and the mount point /mnt/user/appdata to be pointing towards that folder and not the cache as it seems to be doing now, since the cache drive is considerably slower and less reliable.

2. I would like to remove the cache from the system completely, as I don't really need it, and it just adds confusion for me in the folder structure.

 

The folders I have now is

"/mnt/appdata" <-- shows everything that I copied to /mnt/user/appdata but is now spread all across the array. I have no memory of ever creating this folder.

 

"/mnt/user/appdata" <- Where I copied everything to from the bellow folder, hoping everthing would be ok, which spread everything across the array, probably because the cache settings were set to "array". So this folder seems to be on the cache drive somehow?

 

"/mnt/user/appdata/appdata" <- link to "/disks/Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M532569N/Docker/appdata" which I have been using as the "fix" and my default docker template appdata install directory.

 

I don't even know where to start to fix this.

What I am thinking of doing right now is either,

- Copy everything to "/disks/Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M532569N/Docker/appdata" and then somehow go from there to restore the link "/mnt/user/appdata" to that folder.

Or

- Copy all appdata to an external drive, deleting all appdata folders and redoing the whole docker config again somehow.

 

Also want to make sure the cache is not invovled ever again.

Not sure if any of the above are the correct approaches and how not to get the cache mixed up in this all over again.

 

Any idea's are welcome.

Thanks.

are you trying to recover or start over?

Please post a diagonistic file. this wil contain most data I'm looking for...

 

I only know of a few way to get the /mnt/appdata

What I really need is some answers or a picture of your main, a picture of your shares, a picture of the settings for appdata and a picture of your docker advance default appdata path...

as example. I run zfs. My Main is this collection of disk...

If I called the zfs pool appdata I would have a pool disk mount located at /mnt
 

 

Default unraid setups a appdata share.

 

as by default unraid ships with a cache pool for a single disk and this is setup to be the location for the appdata folder.

 

as you can see I also have a made a docker share. 

 

with the share settings I'm more looking at the Primary storage and secondary storage.

 

As this will dictate how new files when created are placed on xyz disk. It should be set to one location so mover doesn't separate files.

 

and under Settings > docker

I'm looking for your Default appdata storage location.

 

BUT In truth it doesn't matter as long as you tell the docker the folder paths...

 

example plex:

in the docker template at the top right:

 

there will be a show more settings. as some docker need settings but usually they are not touched. Most docker ship with a config folder of some sort. this is usually mapped to the unraid appdata folder location.

 

the will be named appdata but you can set the docekr path to any location on unraid.

 

 

 

So to fix you first need to stop all dockers.

Review all dockers appdata location.

 

Double check folder file location and set a folder you want to use and tell unraid primary storage to be that one location.

 

Otherwise you have some weird hardlink / symlink -ing going on...

 

 

I also recommend making a flash backup as We can go over a way to clear the unraid flash drive and start fresh...

(though depending on how and what we delete you may need to do some disk restructuring and may lose data on disk)

 

I would also advise looking into the appdata backup plugin to run a black to save and attempt to backup your current dockers and configurations.

Thanks @bmartino1. I think I managed to solve it eventually.

 

What I did was:

1. Disable/remove my empty cache sata ssd

2. Populate the other M.2 slot with another 1TB Nvme

3. Make a pool of the new drive.

4. Configure Default appdata path in docker settings

5. Move Plex, Docker image, appdata, VM folder to new pool drive

6. Clear old Nvme and add it to the pool in a Raid 1 config

7. Setting all Docker/VM shares to default appdata path and pool as primary storage

8. Unbalance Gather everything into /mnt/user/appdata on pool

9. Removed link /mnt/user/appdata/appdata as it was pointing to the old nvme that is now in the pool.

10. Prayed...

 

Still testing, but it seems to work as intended now.