I am running a daily backup followed by a sync, all set up via dietpi menu.
The backup always runs through, but the sync to my second HDD fails regularly, up to every 2nd day.
I recently activated a hardware watchdog and this restarts my pi3b+ whilst the sync should be running indicating something made the sync fail or putting too much strain on my PI3b+ whilst syncing.
If the sync succeeds, it takes around 2 hours.
Although only a handful of files actually change from day to day. Shouldn’t the sync be much fast then?
My pi is up 6 days now and there was not a single crash after I enabled logging as per above (and uninstalling ram log)
Everything else (backup/sync) is as before.
I will continue observing to see if that is a coincidence or not.
@MichaIng any ideas why journalctl are not surviving the reboot? On my test system, logs did not keep most of the time. On some reboots, they survive. But not that often.
No idea. Works reliable on dietpi.com and my home server. With the applied settings there should be always two files in /var/log/journal/*/, one active system.journal and one with a timestamp of up to 7 days age. /run/log/journal/ on the other hand should be empty.