chiel315

Hi all, My dockers worked fine, with the following settings (I use directories instead of an image): dockersettings.png My system share was set to use NO cache, and all files were on a single disk of the array. The goal was to move the docker files to cache, so I followed the following steps: 1. (probably unnecessary, but did it anyways): in docker tab: stop all dockers 2. in settings -> docker: enable docker to No 3. in share settings for system share, user cache pool: Prefer; select cache pool: Cache. 4. from main: start mover 5. wait for mover to finish 6. settings -> docker: enable docker to Yes, not touching any other settings. 7. All dockers dissapeared. If I browse the docker directory, i see my containers still listed properly. I am aware that I could just re-add the dockers from templates, but I would like to find out why this happened, in order to prevent this in the future. And possibly restore the dockers which are right there in the share: systemshare.png, the containers are there: containers.png, and they have their config: containerconfig.png. I don't understand what changed: the location of the files is still the same, and the docker settings are pointing to the right path (it also hasn't changed, but I verified anyways) and all data seems to be there.

You are correct! It's actually your answer which i linked above 🙈. Thanks!

I am an idiot. Duplicate: Solved.

Hi. I have user share 'appdata' which is prefer cache (pool: "ssd"). I have a different user share 'backup' which is on the array only. When I run the following cron job, I expect the pi-hole file in the backup user share to be on any disk in the array, but instead I find it to be on the ssd cache pool (but still in the correct user share). # make backup docker exec pihole bash -c "cd /etc/backups; pihole -a -t" #note: this mounts to volume /mnt/user/appdata/pihole/backups # move backup to share mv /mnt/user/appdata/pihole/backups/pi-hole-*-teleporter_*.tar.gz /mnt/user/backups/cron/pihole/ # remove backups older than 7 days find /mnt/user/backups/cron/pihole/ -type f -name 'pi-hole-*-teleporter_*.tar.gz' -mtime +7 -delete My question is: How do I make the mv command actually move the file from the ssd cache to the disks assigned to the backup share. Thanks for your time!

Small update: It has been getting worse: it now resets the routing table multiple times a day. I'm realy at a loss here.

Hi guys, I'm running into the issue that my custom entries in the routing table in the network settings keep disappearing. I haven't been able to pinpoint a cause (or a regular interval). I set the routing table up properly so everything works as intended, and then after a few weeks stuff stops working, and when I go see why, it turns out all my custom entries are removed from the routing table. I have not been able to find a correlation between any event (like a reboot, parity check, new docker/vm, array up/down etc.) and the tables resetting, it just kinda happends. I'm not sure what logs would be usefull here, so I have included the default anonymized diagnostic export. If you think the problem might be shown in different logs, please let me know. Thanks a lot for your help! tower-diagnostics-20220505-1207.zip