Jump to content

bunducafe

Members
  • Posts

    64
  • Joined

  • Last visited

Everything posted by bunducafe

  1. And sold, that was a quick one 😉
  2. Hi folks, I upgraded my server towards a bigger machine and unfortunately neither my parents nor brothers need a reliable fileserver. So this little machine goes on sale. - Helios64 with all trays + 2 SSD inserts - Fully assembled - Original packaging - Changed the two fans for Noctuas in order to get an even more silent server What's missing is the Battery for UPS. Mine was faulty and caused me some random reboots. Condition is mint / very good. System is stable with 5.15.93 running OMV6. If you would like pictures of the machine itself please drop me a note.
  3. I am also quite happy. Would you kindly tell us on what kernel you are currently on?
  4. 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.
  5. 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.
  6. 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.
  7. @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.
  8. 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?
  9. 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.
  10. 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.
  11. 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.
  12. 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)
  13. 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.
  14. @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.
  15. 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.
  16. 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.
  17. As I would love to suspend my disks anyway after 5h without accessing the NAS I am kind of reluctant to try the suspend workaround. But what could be interesting is changing the HDDs to one more SSD. Or make 3 (bigger) HDDs out of the 4 in my system in order to avoid the hiccups.
  18. That’s interesting. I have 5 bays equipped, 1x SSD as media drive, 3x WD Reds 5400rpm as mergerfs pool and 1x Toshiba N drive with 7200rpm… actually I was sometimes assuming that it might has to do with waking up drives and that the PSU does not generate enough power to do so… I might have a try with the upscale the voltage workaround you posted as it seems plausible. I also was considering to get a new PSU and see if the shipped one is a bit faulty…
  19. I am on OMV6 with the latest kernel 5.19.93 and I was fiddeling around a lot to get a stable setup. I did a clean install recently and everything works what I need it for. Unfortunately it does random reboots - so I get around 15 to 20 days and then the helios64 reboots and I have not found out what triggers that behavior. I did run it with ondemand governor at full cpu range. Maybe I will try it to throttle it once I am back on the machine. And I might give it a go with an older kernel. Some recommended the 5.19.63 build. I once tried to build my own kernels but did not have enough time to do it properly. Maybe I will jump back at this waggon because at the end I would love to have the machine work the way I want it to. I keep you posted but it will take a while with further experience. trial and error.
  20. How did you set hold? Only via armbian-config? I ran into a same issue on my helios64. I have frozen firmware and kernel immediately after first install, executed the omv installation script and then did a update and upgrade via cli which resulted in an upgrade to the latest kernel which was not intended. When doing a showhold it shows the "frozen items" correctly but apparently they were not taken into account when updating the machine...
  21. Short shout out: running stable on the latest 5.19.x kernel. But with cpu frequency throttled to 400 - 1600 ondemand governor. Means that it runs slightly below maximum power. Does anyone know if there is a workaround to correct this issue and use it with full cpu power and not creating any kernel panic?
  22. Thanks for the heads up. At the end it is really nice to see that there is still some activity in that lovely machine. I tried to compile now my own image through a VM on my Mac, but the actual VM is somewhat unstable with OS Ventura on the ARM chip but at least I know now how to do it and then my wife's machine has to do it (on Intel). Meanwhile I went down with my CPU frequencies on the latest 5.19.x kernel as I encountered various reboots (even when not really using the helios64). Therefore I will experiment the next weeks with older kernels in order to find one that runs stable within my environment. I had one with an uptime more than 60 days but I cannot recall which one it has been :)
  23. Just out of curiosity: If upstream only makes the OS more likely to be fragile what is the use case then for community builds that can be downloaded every now and then? Totally agree. It's a pity that people are not willing to support open source projects like this one. I actually started now to set up a virtual machine in order to be able to compile myself. Still at the beginning but meanwhile I am thinking of freezing an old kernel that works well with my setup. Maybe the best way to go in the end because the helping hands will keep on vanishing day by day.
  24. Is the first LED still blinking regularly? Or frozen? I think it's rather a kernel panic than a problem with hibernation.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines