Hello everyone.

 

I've upgraded my Cubietruck from Xenial to Noble Ubuntu using supplied image on https://www.armbian.com/cubietruck/ . Thank you by the way for uncomplicated installation, worked just fine. Now to the problem: Cubietruck continues to hang (or shut down, I don't know exactly on the same time in a few days turn.

 

Here are the last lines of syslog when it happens:

 

2025-03-03T23:34:59.245531+01:00 Artisan anacron[8415]: Anacron 2.3 started on 2025-03-03
2025-03-03T23:34:59.249722+01:00 Artisan anacron[8415]: Normal exit (0 jobs run)
2025-03-03T23:34:59.253667+01:00 Artisan systemd[1]: anacron.service: Deactivated successfully.
2025-03-03T23:45:02.005984+01:00 Artisan CRON[8426]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
2025-03-04T00:00:01.113480+01:00 Artisan CRON[8446]: (root) CMD (/usr/lib/armbian/armbian-apt-updates)
2025-03-04T00:00:01.118626+01:00 Artisan CRON[8445]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
2025-03-04T00:00:16.107103+01:00 Artisan systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
2025-03-04T00:00:16.146682+01:00 Artisan systemd[1]: Starting fake-hwclock-save.service - Save the current clock...
2025-03-04T00:00:16.202733+01:00 Artisan systemd[1]: Starting logrotate.service - Rotate log files...
2025-03-04T00:00:16.259038+01:00 Artisan systemd[1]: fake-hwclock-save.service: Deactivated successfully.
2025-03-04T00:00:16.260455+01:00 Artisan systemd[1]: Finished fake-hwclock-save.service - Save the current clock.
2025-03-04T00:00:16.326193+01:00 Artisan systemd[1]: dpkg-db-backup.service: Deactivated successfully.
2025-03-04T00:00:16.328508+01:00 Artisan systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
2025-03-04T00:00:16.457562+01:00 Artisan armbian-ramlog[8515]: Tue Mar  4 12:00:16 AM CET 2025: Syncing logs to storage
2025-03-04T00:00:16.564333+01:00 Artisan armbian-ramlog[8518]: sending incremental file list
2025-03-04T00:00:16.565404+01:00 Artisan armbian-ramlog[8518]: auth.log
2025-03-04T00:00:16.565867+01:00 Artisan armbian-ramlog[8518]: kern.log
2025-03-05T18:34:44.202645+01:00 Artisan systemd-random-seed[268]: Kernel entropy pool is not initialized yet, waiting until it is. 

Noticed on 05.03.25 and rebooted at 18:34 manually

-------------------------

2025-03-06T23:33:48.656870+01:00 Artisan systemd[1]: Started anacron.service - Run anacron jobs.
2025-03-06T23:33:48.659661+01:00 Artisan anacron[6409]: Anacron 2.3 started on 2025-03-06
2025-03-06T23:33:48.666596+01:00 Artisan anacron[6409]: Normal exit (0 jobs run)
2025-03-06T23:33:48.672146+01:00 Artisan systemd[1]: anacron.service: Deactivated successfully.
2025-03-06T23:45:01.444161+01:00 Artisan CRON[6419]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
2025-03-07T00:00:01.621123+01:00 Artisan CRON[6439]: (root) CMD (/usr/lib/armbian/armbian-apt-updates)
2025-03-07T00:00:01.627275+01:00 Artisan CRON[6441]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs)
2025-03-07T00:00:01.657120+01:00 Artisan systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service...
2025-03-07T00:00:01.661516+01:00 Artisan systemd[1]: Starting fake-hwclock-save.service - Save the current clock...
2025-03-07T00:00:01.800805+01:00 Artisan systemd[1]: Starting logrotate.service - Rotate log files...
2025-03-07T00:00:01.945811+01:00 Artisan systemd[1]: fake-hwclock-save.service: Deactivated successfully.
2025-03-07T00:00:01.966228+01:00 Artisan systemd[1]: Finished fake-hwclock-save.service - Save the current clock.
2025-03-07T00:00:01.998597+01:00 Artisan systemd[1]: dpkg-db-backup.service: Deactivated successfully.
2025-03-07T00:00:02.004085+01:00 Artisan systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service.
2025-03-07T00:00:02.179015+01:00 Artisan armbian-ramlog[6468]: Fri Mar  7 12:00:02 AM CET 2025: Syncing logs to storage
2025-03-07T00:00:02.242697+01:00 Artisan armbian-ramlog[6471]: sending incremental file list
2025-03-07T00:00:02.268700+01:00 Artisan armbian-ramlog[6471]: ./
2025-03-07T00:00:02.269353+01:00 Artisan armbian-ramlog[6471]: auth.log
2025-03-07T00:00:02.276689+01:00 Artisan armbian-ramlog[6471]: boot.log
2025-03-07T00:00:02.278456+01:00 Artisan armbian-ramlog[6471]: lastlog
2025-03-08T09:58:11.992041+01:00 Artisan kernel: Booting Linux on physical CPU 0x0

Noticed on 08.03.25 and rebooted at 9:58 manually

 

I've tried to search the forum for the same problem and got only like "stable shouldn't be crashing - problem either with unstable power supply or overheat. My Cubietruck ist plugged into small UPS, overheat shouldn't be a problem - maximal CPU temp was like 43°C . Also it's strange the problem occurs at midnight. I'm using Ubuntu Noble 6.6.75-current-sunxi. Cubietruck is doing nothing more as Samba / minidlna. An external SSD Drive 5 TB is plugged in both USB ports (one isn't enough for power supply). Here's needed to say, that the same problem I got on Debian 12 Bookworm (switched to Ubuntu with hope to eliminate the problem).  I've disconnected the external SSD USB Drive to see if problem was within. Any suggestions and help would be appreciated.

 

PS: is Ubuntu image now gone from https://www.armbian.com/cubietruck/ ?

I'm not sure there is a problem.  It looks like this may be expected behavior.  I think your board is a community supported device which means that by default it will be on the beta apt repository.  There are new packages deployed to the beta apt repository daily.

So depending on the settings you have for your apt updates if you have automatic updates enabled and reboot on kernel updates you will get a daily reboot.

Some of this functionality for auto updates in armbian-config was just recently introduced.

Hi. Thank you for reply. It wouldn't be indeed a problem if it would restart once a night or something. The problem it just stops responding - no samba shares, no ssh access. I guess it literally hangs. It could working for a few days and someday just stops responding, as I check syslog - always the same: end of the log at the midnight.

Same issue with disabling ram logging as solution (worked for me):