MichaIng
could you have a look pls
hi,
I have the same issue. Tried to:
systemctl unmask systemd-timesyncd.service
systemctl enable systemd-timesyncd.service
systemctl start systemd-timesyncd.service
not working for me. also tried :
apt install --reinstall systemd
additional info:
Operating System: Raspbian GNU/Linux 11 (bullseye)
Kernel: Linux 5.10.63-v7+
Architecture: arm
Well you would need to check for root cause first before going into error fixing. 5 minutes after reboot do following and post the results
systemctl status systemd-timesyncd.service
journalctl -u systemd-timesyncd.service
I’ll try the Armbian based N2 image creation tomorrow, will upload an image then as well. It should be “Bullseye” btw, not “Buster”.
Is there any news?
Sorry for missing to reply here. The new image is up for a while. Sadly old systems cannot be upgraded since a different partitioning is required, so the new image needs to be flashed freshly.
Hello, I’ve been using the latest version (flashed the eMMC) for some time now but unfortunately I still have crashes.
The blue LED stops flashing and the system is dead. But it does not get warm/hot.
Slowly I’m really getting desperate. I have also run memtester, but no problems were found.
Nasty, my N2+ runs rock solid 
. Probably enabling persistent system logs provides some info about what happens:
dietpi-software uninstall 103
mkdir /var/log/journal
reboot
To revert:
systemctl stop systemd-journald
rm -R /var/log/journal
systemctl start systemd-journald
dietpi-software install 103
My odroid crashed…
How can I see the logs?
Which logs are important?
All logs dated from 1 hour before the crash, given by journalctl.
The log says absolutely nothing…
And before 01:55:22 there are only Home Assistant related things.
May 15 01:55:22 DietPi 86cdbd335317[2001]:
May 15 02:00:22 DietPi 86cdbd335317[2001]:
May 15 02:05:23 DietPi 86cdbd335317[2001]:
May 15 02:10:23 DietPi 86cdbd335317[2001]:
May 15 02:15:23 DietPi 86cdbd335317[2001]:
May 15 02:17:01 DietPi CRON[21585]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 15 02:17:01 DietPi CRON[21586]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 15 02:17:01 DietPi CRON[21585]: pam_unix(cron:session): session closed for user root
-- Boot a5db5145b65e4b2fbb3c8c97876436c2 -- (new boot)
May 15 19:08:46 DietPi systemd-timesyncd[1696]: Initial synchronization to time server [2a01:4f8:160:43aa::2]:123 (2.debian.pool.ntp.org).
If you don’t have an RTC attached, note that the logs of the last boot session are mixed with those of the next boot session until time sync has finished. Probably you see some more – Boot lines above the ones you posted? However it indeed looks like the hourly cron job is the last entry from before the crash. It seems to have been quite a sudden full crash then 
. What about RAM usage and what other hourly cron jobs are done?
ls -l /etc/cron.hourly
I have activated the RTC and I have added a battery.
ls -l /etc/cron.hourly
total 4
-rwxr-xr-x 1 root root 1311 May 2 16:16 dietpi
ls -l /etc/cron.hourly/dietpi
-rwxr-xr-x 1 root root 1311 May 2 16:16 /etc/cron.hourly/dietpi
But the dietpi folder is empty.
Today I had another crash…
But this Time Home Assistant was the last thing.
May 18 01:25:37 DietPi b75d9a29f859[2004]: 22-05-18 01:25:37 CRITICAL (MainThread) [supervisor.jobs] The following job conditions are ignored and will make the system unstable when they occur: {<JobCondition.HEALTHY: 'healthy'>}
May 18 01:25:37 DietPi b75d9a29f859[2004]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not running - CoreState.SETUP
May 18 01:25:37 DietPi hassio-supervisor[3601]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.jobs] 'ResolutionFixup.run_autofix' blocked from execution, system is not running - CoreState.SETUP
May 18 01:25:37 DietPi hassio-supervisor[3601]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
May 18 01:25:37 DietPi b75d9a29f859[2004]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
May 18 01:25:37 DietPi hassio-supervisor[3601]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
May 18 01:25:37 DietPi hassio-supervisor[3601]: 22-05-18 01:25:37 INFO (MainThread) [__main__] Running Supervisor
May 18 01:25:37 DietPi b75d9a29f859[2004]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
May 18 01:25:37 DietPi b75d9a29f859[2004]: 22-05-18 01:25:37 INFO (MainThread) [__main__] Running Supervisor
May 18 01:25:37 DietPi b75d9a29f859[2004]: 22-05-18 01:25:37 WARNING (MainThread) [supervisor.core] System running in a unsupported environment!
May 18 01:25:37 DietPi hassio-supervisor[3601]: 22-05-18 01:25:37 WARNING (MainThread) [supervisor.core] System running in a unsupported environment!
May 18 01:25:37 DietPi b75d9a29f859[2004]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.jobs] 'OSManager.mark_healthy' blocked from execution, no Home Assistant OS available
May 18 01:25:37 DietPi hassio-supervisor[3601]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.jobs] 'OSManager.mark_healthy' blocked from execution, no Home Assistant OS available
May 18 01:25:37 DietPi b75d9a29f859[2004]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons
May 18 01:25:37 DietPi hassio-supervisor[3601]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons
May 18 01:25:37 DietPi b75d9a29f859[2004]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' starting 2 add-ons
May 18 01:25:37 DietPi hassio-supervisor[3601]: 22-05-18 01:25:37 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' starting 2 add-ons
But I see everytime pulseaudio in red… I haven`t installed it.
pulsaudio2.txt (63.4 KB)
pulsaudio1.txt (82.1 KB)
I guess PulseAudio runs on the container? It seems to have issues to find the audio devices. I wonder what for HA requires audio?
All that messages with “will make your system unstable” and “unsupported environment” don’t look good. How did you install that HA supervised?
I think it’s the usb interface stuff.
I tried to sync a crypto wallet = crash
I synced photoprism with my nas = crash.
That sounds like some hardware difficulties
What do you mean by that?
I guess there are disks attached to USB and probably high I/O is causing system crashes?? Just guessing.
Yes…
I tried another HDD but same problem.
But I have zero problems with my Pi.