March 3, 20233 yr My system reboots in 6 hours, sometimes in 2 days. I have not seen it last longer than two days, so what I have done. swapped out Ram (its been lasting longer but still happens) enable syslog (I could not find anything within the reboot window) enable "Save CA debugging information" (waiting for a reboot) Downloaded "diagnostics" (I don't know what I am looking for) and looks like it clears out after reboot I plan to wait until the next reboot and upload diagnostics and Syslog. But is there anything else I should do? Edited March 3, 20233 yr by beringbullet
March 3, 20233 yr Author Here are the Diagnostics, Crash was 10h:21m ago from this pull, I did not have CA debugging at this time. tower-diagnostics-20230303-1252.zip
March 4, 20233 yr Author Here are the syslog (with CA debugging information: on) and diagnostics crash was 4h:44m ago. syslog-192.168.88.12.log tower-diagnostics-20230304-0931.zip I found this from seeing this in the syslog, but I can ping all my name servers, and I see it all over the logs even when there is no crash from syslog - ntpd[1162]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Edited March 4, 20233 yr by beringbullet
March 5, 20233 yr Author Well that was not it, it happen again 2 hours ago, and the syslog shows nothing
March 11, 20233 yr Community Expert Unfortunately there's nothing relevant logged, this usually suggests a hardware problem, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.