it couldn’t be more worse as it already is 
Not persistently, but to debug the issue. By default there is nothing very important done via Cron, aside of the regular RAMlog clearing, in case it fills very quickly, so it’s not a big issue when it is disabled temporarily, especially when the system is unstable anyway.
I now attached a screen to view additional error messages after the crash.
This is what I got.
This looks different to the error messages in the log files.
Do you have any ideas, what could be the reason for the crash?
This is a kernel panic. Could be data corruption. MichaIng what do you think?
This is with cron still disabled? A fsck would not hurt at least, and upgrading/reinstalling the kernel afterwards:
> forcefsck
reboot
# after reboot
journalctl -t systemd-fsck
apt update
apt full-upgrade
Thanks - I will try this.
fsck did find some errors - let’s see if this helps.
Cron jobs were enabled during the last crash. I checked before to disable cron, but it did not change anything.
this seens to work - so it was due to a file system problem.
Thanks a lot
I’m glad it worked .