Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am also quite happy. Would you kindly tell us on what kernel you are currently on?
  2. What are you running the helios64 with? OMV? Did you do any manual changes within the system? I once had a faulty battery. Once I ripped that out everthing worked again... What does the log tell you once the machine goes down? I can feel the frustration but I believe if configured correctly the machine might run reasonably.
  3. Which kernel are you on? I am running my machine now for over 80 days without any issues whatsoever. See screenshot. I started from the last official image and then updated manually to the 5.15.93 kernel. Then rebooted and froze further kernel updates. Then I updated all the rest. Since then I have a solid machine and I won't go any further kernelwise.
  4. I usually do an update only via OMV. But no matter which way you use once the kernel is frozen it should only update the packages accordingly until that version. At least that's what it is in my case. In the past I just put in the terminal commands you mentioned. I believe the update process via armbian-config is identical (someone correct me pls if I am wrong) - and so is the OMV command, too.
  5. @TDCroPower as stated above. I use the old image and manually update the kernel until 5.15.93 and then freeze the kernel. Some reboots might be required anyway. Once it is up and running again I would then perform apt update && apt upgrade. Because of the frozen kernel the firmware should not update to any higher version same es the packages a higher kernel would require.
  6. That's kind of strange. I freeze the kernel via armbian-config as mentioned in previous posts and it holds it on my machine. Of course you can use the CLI as well. Then it should work with the apt-mark command. Are you running OMV on top of Armbian? Or are you using a different nas software?
  7. Could you try get the 5.10.63 image on sd-card and then go to kernel 5.15.93 via armbian-config and then apply apt update / apt upgrade? I somehow think that with updating to the latest kernel and then switch back to an older kernel the system already got corrupted.
  8. I usually run the machine between 400 and 1400 MHz ondemand governor. Yesterday it was set to full speed while performing a SnapRaid scrub... you may have to figure out what's best for your setup, but the mentioned range was the one I ran the helios64 for over 2 months without any issue whatsoever.
  9. Freezing the kernel is easy within armbian-config. Just go to System / Security and hit Disable Kernel updates (Freeze) Yes, I often started with a blank 5.10.63 system and then performed the updates to 5.15.93 accordingly. You can also set the kernel via armbian-config first, then let the machine do it's job and afterwards you freeze the kernel and do all the updates. Meanwhile I have a bunch of "old" images here of working SD-cards that I can always revert back to. That saved my ass also in the latest update trouble. For me 5.10.63 was not entirely stable but 5.15.93 is rock solid. So I would give it a go. Also: I will probably never update the kernel anytime soon and stick to my running system. I might compile it one day with a newer kernel but this is a bit farer away as I had no success with my first attempts and do not have the time to dig deeper into that.
  10. Just a quick one: Accidentally updated the machine three days ago and it got stuck in a boot loop. I forgot to freeze the kernel to 5.15.93 and that's what caused the issue. I reverted back to the old kernel, froze the kernel and then did the update via OMV and everything works as expected. I know, not a real solution to the problems (I did not hook the laptop in order to get the console working) but a workaround for those who have a running backup (here with SD cards)
  11. But it does reboot every 10 days by itself? Here I don't have any difficulties with the said settings. So maybe there is a different setting / hardware issue that causes the reboots. Mine has now been stable one month (touch wood). I will definitely use the machine as long as it runs... Harddisks: - SSD with media library and stores all docker containers - 4x 4TB HDDs (3 are merged with mergerfs and 1 hdd is solely the parity disk for snapraid) Not too many fancy things further on. Docker runs Jellyfin and Navidrome. VPN and mediastacks are only running when needed to. Otherwise I stop these containers.
  12. @mrjpaxton Well, at least once you set up the helios64 with the oldest official kernel you can indeed upgrade to Debian Bullseye (11) which gives you still a bit of time as long time support will be approx. until 2026. I am a bit at easy with the machine as it runs flawlessly. If I won't be able to build my own kernel until then I might just leave it as it is. Exposed only to the local network I don't see too much of a security risk either... but let's see how everything turns out. Maybe I will shift to a different NAS enclosure that "just runs" and has a decent support. On the other side I quite liked Kobol's approach with the Helios64.
  13. No scientific research, but as the A53 cortex only runs maxed out with 1400 MHz I thought that's the way to go... also in the past some users here on the board were posting more stable machines with max at 1400 MHz. But as I am no tester whatsoever I cannot measure actually the differences in case the system freezes and reboots but am somewhat happy that the actual system works as it should.
  14. Well, I was kind of busy travelling the last few weeks but my machine now has worked for 22 days without hicups and had to complete two snapraid syncs and scrubs in the meantime with some minor scheduled task additionally. I indeed did set the governor to 400 and 1400 MHz ondemand.
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines