Perfect, that looks fine. Still wondering about the fsck issue on reboot, but nothing to worry about then. When you unexpected powercycles again, we should investigate those separately. One step to keep system logs from before the crash/reboot is to enable persistent logging:
No it's not (yet) the same. "Full" means that rsyslog and logrotate is installed, which is basically an unnecessary overhead to the system logging as systemd-journald is running anyway, but additionally forwards system logs to rsyslog which stores them in plain text to /var/www. So you have doubled system logging then. Of course when one needs or wants plain text log files, it's the way to go, but journalctl is actually quite nice, can filter and sort all system logs combined.
An outstanding task to make that "Full" logging choice a "Persistent syslog" choice, which enables the persistent journal by creating that directory for it.
battling with a new Odroid N2+, which is constantly rebooting in the middle of dietpi-backup/sync to an external usb-ssd I question myself if the filesystem is not in risk of being corrupted.
If it is, is there a warning somewhere? And how can I check/fix it. I mean the main OS drive.
battling with a new Odroid N2+, which is constantly rebooting in the middle of dietpi-backup/sync to an external usb-ssd I question myself if the filesystem is not in risk of being corrupted.
If it is, is there a warning somewhere? And how can I check/fix it. I mean the main OS drive.
Thx in advance
How was the issue resolved?
Stopped using the N2+. There is no stable dietpi for this avaliable at the moment.