Thule Posted January 17, 2021 Share Posted January 17, 2021 Armbianmonitor: http://ix.io/2Mk4 I can't pinpoint the cause of the freeze exactly, but it shows as follows in syslog: At midnight, logrotate was started but never successfully concluded. At the time, I was also recording a stream via smb to the hdd. (Not a very demanding activity) When I tried to access the SBC via network share or ssh this morning, neither would show as available. The SBC was running but "dead". When I rebooted it by re-plugging power, instead of showing ~9:00 o'clock, the SBCs internal clock showed 02:17. Here are the last messages of the syslog before the SBC locked up: Quote Jan 17 00:00:00 droid systemd[1]: Starting Rotate log files... Jan 17 00:00:01 droid armbian-ramlog[390]: Sun 17 Jan 2021 12:00:01 AM CET: Syncing logs to storage Jan 17 00:00:01 droid armbian-ramlog[390]: sending incremental file list Jan 17 00:00:01 droid armbian-ramlog[390]: auth.log Jan 17 00:00:01 droid armbian-ramlog[390]: daemon.log Jan 17 02:17:10 droid systemd-udevd[370]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Jan 17 02:17:10 droid systemd-udevd[365]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. I should note that the SBC has been running 24/7 stable for weeks. There have been more hardware demanding tasks running without issue. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.