Lindworm

Here is the way I fixed my problem. The broken backups are just backups. No worries there, can be restarted after fix. Deleted those folders. Some stuff was misconfigured. For whatever reason all Array only folders had Cache as main storage configured and the mover action to move from Array to Cache. ¯\_(ツ)_/¯ I turned that around, hit the mover, to start moving. Now everything is slowly moving to the array. When done, I disable the mover behavior in the share. Then new files only drop in the array. I tested the behavior with some test data, and all looks well as it should. This must got broken with the last update. I don't know how, buut the tools you get to fix that are decent. Thanks.

But thanks for the link, while checking and reading, I realized that a bunch of settings are wrong now and differ from my last personal documentation. I think I can fix that now on my own.

I am using unraid now since version 4 and this is an ever growing setup. The mover was never on. And yes something changed. The tick box "use cache" is gone on the share config page, for example, instead I can only tell if I prefer Array or Cache. Totaly different behavior. (Might be changed a couple of versions ago, i do usualy not babysit unraid) Now the mover is set to hourly and directories gets moved to /mnt/cache that in the last 6 years never popped up on it and were only visible and accessible in /mnt/cache. I have never ever experienced a back copy from HDD to NVME cache before. Now when I drop a test folder in /mnt/user, wait an houre, unmount everything and only mount the cache drive, I see all the data which should be in /mnt/user and not on the cache.

I just lost a big bunch of data, because something about the cache system changed? I miss now a setting in each share. If it should use the cache or not. Lots of my shares were set to NOT use the cache at all. These folder all of a sudden popped up on the cache drive. Now there is only a setting what is prefered. Array or Cache. That lead to unraid copying all the content it could to the cache drive. For example my backup folder which is 6 times the size of the cache drive, mounted what was left. No realizing this because ¯\_(ツ)_/¯ you rarely check for such things, borg was sending backups and now all my borg archives are broken beyond repair. I need to be super super sure that stuff in /mnt/user is not in /mnt/cache, gets not moved and so on. I will manage that myself. The upper was true for me, until a short time ago. no clue when it changed. How can I do that?

I now stated over with a new configuration and copy the files. But I know now for the future.

Hi, when I restarted the server today suddenly one of the drives told me "Unmountable: Volume not encrypted" but the info of the drive told me it is xfs-encrypted So I tried to mount the drive manually mkdir /mnt/disks/sda1 cryptsetup luksOpen /dev/sda1 sda1 --key-file /path/to/keyfile mount /dev/mapper/sda1 /mnt/disks/sda1 and there are my files, the disk opens fine and I seem to see all data on it. I know I now could insert a new drive and copy the data over after adding the drive to the array, but I wonder now how I can repair the automount of unraid on bootup, so I can have a full array again without days of copy jobs?

Hi, daily I have to restart the server because docker crashes and I am greeted with Warning: mkdir(): Input/output error in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 349 in /var/log/docker.log I find time="2022-07-10T17:56:36+02:00" level=warning msg="deprecated version : `1`, please switch to version `2`" containerd: creating temp mount location: mkdir /var/lib/docker/containerd/daemon/tmpmounts: input/output error I checked all filesystems now 3 times. It's not the filesystem. That started with 9.10.3. Prior everything worked fine. But I am lost how the docker install in unraid works, as I can write into /var/lib/docker/containerd/daemon/tmpmounts without any problem. Does anyone have an Idea please how to fix that? Best regards and thanks for your help.

That way worked for me and manual setup of usb worked either. I had the same issues with the mac version of usb creator