• Content Count

  • Joined

  1. Short update running 5.4.66-mvebu now, resulted in a system freeze in just a couple of minutes running raid check. I am officially out of ideas. The Helios4 was running fine for many years when I got it after the successful Kickstarter campaign. I can not really pin point when it started freezing (I think it started after October of 2019). I am also not sure if it is a hardware or a software problem.
  2. @gprovostThanks. Having a watchdog will restart the system in case it freezes, like it does for @Mangixand @fri.K I would be more interested in helping to fix the underlying problem. How can I help?
  3. @gprovost Not sure if this is expected or not, but since you asked before, this is running Armbian_20.08.13_Helios4_buster_current_5.8.16.img.xz without any changes. root@helios4:~# systemctl status watchdog.service Unit watchdog.service could not be found.
  4. It froze again during raid check I will try kernel 5.4.66-mvebu, like suggested by @fri.K After that I am really out of ideas
  5. Bought a new micro SD card and put on it. Booted, set up the root password and directly started a raid check (9.4% done so far). I am very excited to see what happens.
  6. I guess in your cases the system also freezes and the watchdog service is rebooting the system then. I am going to setup the system from scratch using tomorrow.
  7. I would see freeze, as the system is not usable anymore (not reachable via network nor serial). The logs also do not indicate a reboot. If it would be a reboot I would expect the system to be in an usable state afterwards.
  8. Hi Forgot to give an update. The system froze during raid check at 54.3% . The temperature was always between 54-57°C. @gprovost Any ideas what might be wrong? Regards -kratz00
  9. Hi gprovost Exactly. Not reachable over the network. Does not respond via serial console. Seems it is missing: kratz00@helios4:~$ systemctl status watchdog.service Unit watchdog.service could not be found. Raid check is nearly running for an hour, load is high and the temperature is stable around 55°C: root@helios4:~# uptime 06:53:44 up 21 min, 1 user, load average: 2.00, 1.92, 1.27 root@helios4:~# cat /dev/thermal-cpu/temp1_input 55122 Regards -kratz00
  10. Hello For quite some time I experienced system freezes. I already measured the voltage on the board 12V and 5V are okay on both connectors. Attached you will find the armbianmonitor -U output. I tried to capture kernel logs using information from some other thread. sudo dmesg -n 7 sudo dmesg -w But I could not capture anything useful. Today the system froze while checking the raid (filesystem was not mounted). [ 168.224361] md: data-check of RAID array md0 Is there anything else I can do to shed some light?
  11. In my case it would be a downgrade from linux-4.14.20-mvebu to linux-4.14.18-mvebu. I am not forcing or switching anything, I was just running 'sudo apt-get upgrade'. I do not know the inner workings of apt, but to me it is strange why it tries to install a package with the same exact version (5.41) again. What is also a little confusing is that there are different armbian version for the Helios4.
  12. Looks like the release on the kobol wiki ( was built against the armbian development version (!? The official armbian kernel for the Helios4 seems to be 5.41 seems to be the armbian version number, does this mean a newer kernel can only be released if the armbian version gets bumped?
  13. I have an odd situation which I can not explain. I installed the Debian 9 image (7/02/2018). I am now running Linux 4.14.20 as expected. After running apt-get update I see an update for the linux-image-next-mvebu package with the same package version (5.41) which would install Linux 4.14.18. Can somebody please explain what is going on? apt-cache show linux-image-next-mvebu Package: linux-image-next-mvebu Priority: optional Section: kernel Installed-Size: 34496 Maintainer: Igor Pecovnik <igor.pecovnik@****> Architecture: armhf Source: linux-4.14.18-mvebu Version: 5.41 Fi