kilonde

The server goes completely unresponsive for no reason or user action. It can come back alive after several hours, sometimes not.

Am I impacted by this issue as well? Anyone can shed some light?

Thanks for your thoughts, as far as I can tell there is no pattern to it, and most of the time the server locks when I am not actively doing anything with it. I just think that CPU spikes and it feels like an out of memory issue, so something is starting to take up memory. The docker containers are restarting on purpose, to actually stop memory leaks, because the change detection container used to use a lot of RAM but with hourly restarts I don't observe that behaviour.

After upgrading to version 7, I am experiencing very frequent server locks. One even lasted longer than a week, and then the server came back online. Sometimes, Docker containers continue to run, but the web GUI is not available. Sometimes, everything is unreachable. Most of the time, SSH is not available. Tailscale is showing as online but unreachable. I have not made any configuration changes from version 6, which ran for months without any issues. I have tried open-source Nvidia drivers instead of the default ones. I believe I am on IPvlan and have the latest patches. The behaviour was the same during 7 betas and RC. Earlier today I had a hard lock which eventually resolved, and just now I had one that was semi hard, meaning that i could see open dashboard, but other pages would not load. I could access SSH, however: Prior to killing docker (semi hard lock I describe above): After reboot: CPU usage looks quite high with no VM or docker running. Any ideas where to look? tower-diagnostics-20250211-1554.zip

I get the following error when I run the script: [appdata] Does not contain "read list"! SMB config has not changed root@Tower:~# cat /etc/samba/smb-shares.conf [appdata] path = /mnt/user/appdata comment = application data browseable = yes # Secure public = yes writeable = no write list = kilonde case sensitive = auto preserve case = yes short preserve case = yes I suspect I need to make some changes to the smb-shares.conf? Thank you!

Thanks for your help, this has worked!

I am confused how to update my repo path in the configuration to avoid this error: Remote repository paths without ssh:// syntax are deprecated. My repo configuration is like this: [email protected]:/mnt/disk/borg_backup/repo and the ssh command looks like this: ssh_command: ssh -i /root/.ssh/Pi Also, is it advised to keep the same version of borg on client and the server?

Thanks again, that makes sense, the tunables tab is showing good for all parameters. Yet my Idle stats dont look promising: And it looks like only two frequencies - 800MHz or 3.6 GHz Can I make some further changes? All C states are enabled in bios, no VMs.

Thanks, based on that output, the auto tune does not run, or am I wrong? Google does not help much unfortunately.

I get the same error, have you managed to get it working? I'm using 10th gen Intel.

Thanks, I replaced it with 20 4 * * 1,4,6,0 and it appears to have worked! 7 is not Sunday

Post here if you find something, I am also on 10100 and was freaking out that after changing bios settings my output looks like this:

I have tried to set this up but it does not seem to work: 20 4 * * 1,4,6,7 PATH=$PATH:/usr/bin /usr/bin/borgmatic prune create -v 1 --files --stats > /mnt/logs/backup-"`date +"%a-%H"`".log 20 4 * * 3 PATH=$PATH:/usr/bin /usr/bin/borgmatic check -v 1 2>&1 First added the statement with notepad but read elsewhere that it might be causing issues so recreated the file in VSC, the issue persists. Logs are created but with a strange name: Docker log is full of cron errors as well Any idea what is going wrong?

Thanks for bringing borgmatic to unraid, I have managed to get it working with unassigned drive. The ultimate goal is to have a Raspberry Pi hosted remotely for backups - I have managed to do a test backup, but it looks like the encryption was done on the Pi? My plan is to set a wireguard connection schedule to connect the Pi to my unraid, run borgmatic backup and then disconnect the pi from my unraid. What is the best way to: Make sure the encryption is done on the more powerful unraid server Connect and disconnect the Raspberry Pi Wireguard connection from the unraid server. Furthermore, my healthchecks only show this in notification emails: Is there a way to have more detailed --stats output? I have followed sdub's guide on creating persistent logs in appdata and can see the output. According to borgmatic documentation the notification should already contain some log up to 10kb? https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#healthchecks-hook

Is there any chance you could share your backup "pruning" script?