I recently upgraded my Unraid box and while using unBALANCE I noticed that my docker.img is living in two different locations.

 

One of the docker.img files is on disk13, the other is in my NVMe cache.

 

Disk13:

 

NVMe cache:

 

Both of the Docker vDisk files are 53.7GB despite Docker settings being configured for a max of 50GB. The docker image file location is set to:

/mnt/user/system/docker/docker.img

 

 

I am in the process of upgrading 2 disks in my array and so the shares that are on that array are marked as "unprotected" while the array rebuilds.

 

I note that even though /system/ is set to prefer NVMe cache, and even though docker.img is on my NVMe cache, Unraid thinks that it's unprotected because the img file is supposedly existing in 2 locations at once.

 

 

How do i correct this issue? Do i just modify the vDisk location and manually point it to /mnt/nvme-cache/system/docker/docker.img then delete the other file on Disk13?

 

Thanks.

 

7 minutes ago, LumpyCustard said:

How do i correct this issue?

Looking at timestamps, the one one nvme looks more recent. I would simply delete (or move elsewhere as backup while you figure this out) the system share from disk13 if everything it has exists on nvme cache. /mnt/user/system should then pick whatever is up on nvme

This is assuming system share uses the nvme cache

 

10 minutes ago, LumpyCustard said:

Unraid thinks that it's unprotected

If your nvme cache is protected by raid, ideally it should not complain. If the cache is single disk, then of course it is unprotected once the files are on cache 

14 minutes ago, LumpyCustard said:

Both of the Docker vDisk files are 53.7GB despite Docker settings being configured for a max of 50GB

This is normal

Thanks, i'll give it a try. And yes the NVMe cache is a 4 disk array so it's "protected", hence why i noticed the difference between the shares that live on my array and the shares that are using Prefer Cache.

 

I'll wait for the rebuild to finish in 12 hours and give it a try.

 

Thanks again.

 

Edited February 27, 20233 yr by LumpyCustard

15 minutes ago, LumpyCustard said:

/mnt/nvme-cache/system/docker/docker.img

Normally you should not do this, as this can conflict with any mover activity and bypass shfs which unifies the file systems across cache pools and array

If you directly addressed pool or drives like this before, it might explain how you ended up with 2 copies

6 minutes ago, apandey said:

Normally you should not do this, as this can conflict with any mover activity and bypass shfs which unifies the file systems across cache pools and array

If you directly addressed pool or drives like this before, it might explain how you ended up with 2 copies

 

I've never directly accessed the pool (by pointing it at the actual directory on the invidual disk) or modified my docker image location since building this server so i'm not entirely sure what happened.

 

I've been having issues with unBLANACE reporting issues with file permissions with containers such as krusader, nginx, and others, despite running new permissions to fix the issue unBALANCE continues to complain about permission issues.

 

Most recently when my cache failed (due to to running in RAID0 mode), i used unBALANCE to completely empty my cache after getting the SSD professionally repaired. After moving all the files and creating a 4 disk cache in mirror mode with new NVMe drives i noted that mover was refusing to move some files back into the NVMe cache, again -- mover left some /appdata/ files for krusader, nginx and some others in the disk array rather than moving them to the nvme cache.

 

I've run and re-run new permissions multiple times and it just doesn't want to fix the issue so i'm at a loss. I ended up manually moving the files myself using the unraid file browser plugin.

Edited February 27, 20233 yr by LumpyCustard