bunducafe

I had a similar issue with random reboots. Did DM @axelroy directly and also "tweaked" the system. I am running the helios now for almost 2 weeks without issues with the following settings: Min CPU speed = 400 MHz Max CPU speed = 1400 MHz CPU governor = on demand So it seems that the helios was rebooting when having to deal with intensive tasks - in my case: performing a SnapRAID scrub. Anyhow: Now I am at maximum speed of 1400MHz whereas the helios could perform even on 1800MHz. The question is if this is a problem by design? Or is there a way to fix it

I was just wondering, which would be the most elegant way to get the system backed up if everything resides within the eMMC. If I would not have moved the eMMC route and still use the SD card as my OS I would just clone the SD card. Hence this is not possible is there any tutorial to get a bootable clone of the eMMC?

After fiddeling aroud I finally have the helios64 also running solid. I never had any freezes before just some problems with getting the system to boot from the emmc device and, see other thread, with setting up OMV - LUKS - Snapraid - UnionFS I am currently under: Linux helios64 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 GNU/Linux OMV Version 5.6.2-1 (Usul) So I would say that OMV is not the culprit out of the box. The system works fine but it always depends on what kind of plugins you are using etc. So far I have no docker install

Hi folks, just a heads up in this thread (maybe related to others experiencing boot issues with Helios64 and OMV5): If you use the setup: OMV5, Multiple Hdds, LUKS encryption + UnionFS then it is very likely that the machine does not come up instead is booting into revocery mode. That's because it cannot find any mountpoints because of LUKS. In order to get the helios booting again you have to add a "nofail" into the mergerfs option. Unfortunately the merferfs pool does not getting mounted automatically once you decrypted the hdds within LUKS Plu

At least I could get it booted again. I did a clean install onto a fresh SD card with the latest Armbian-Image kernel 5.10. It did boot up but of course I am losing all my configs with OpenMediavault etc. That's the output of the dmesg, there seems something wrong with both mmc and sd. How can I solve that issue in order to get a system that works and where I can then do all the config with OMV and after that reboot / shutdown and boot again...?!

Unfortunately I cannot get the console working with neither MacBook nor iMac. It's really frustrating. Beyond that: I shortened the P10 jumper in order to boot from SD card, yet, it does not boot. No flashing light, just the steady blue one, no heartbeat. So, what else am I supposed to try to get the Helios64 boot again from SD card? Funnily I did not change anything from the last time, I just switched the Helios off while I was away...

After I could not boot at all tonight, I am somewhat puzzled what I should do. There is a possibility that the SDcard just went dead but neither could I boot from the eMMC. After several reboots with a freshly installed SD the helios is booting up again but of course all the setup is lost. Bottom line: Is there a way to easily delete the emmc partition and tell the helios64 to boot from SD card immediately? And if so: How ;) I cannot get it done via the armbian-config unfortunately.

Hm, I guess I have to go the same route as I am unable to boot again with emmc. Also in the boot settings I only have two points left I can chose. So will have to contact the support team directly I suppose.

Hm, is there a possibilty that the old bootloader name is again the used in the newer kernels? I can get it working with the workaround in the troubleshooting section: Then the machine boots without any issues. Here I am unsure what I have to do? Excersise the same procedure again - e.g. in armbian-config: Select Boot from eMMC - system on eMMC ? Then I do fear that it won't boot as expected as I have done this several times now...

I received the Helios64 last week and wanted to set it up right now. Ran into the exact same issue. As I had no luck with connecting my MacBook Air via Serial Console, I did it headless with the SD Card. After copying the boot partition from SD to the eMMC, it booted once without an issue. After trying to install OMV via softy it just does not boot anymore. I will be back on the SD Card and unwilling to touch that procedure again if it is not flawless.

Thanks for the info. I’d rather use the case with fans. I won’t use it as DAS and it will be in the hallway under the router and stuff. I am now tempted to use the stock fans and see how it goes instead of change everything in the first place... if the fans are too noisy in the end then I will change them for some Noctuas

Thank you for the insight. So I might opt in for the Noctua directly and play with the config afterwards anyway. Helios case is arriving tomorrow and shipment was way faster than expected, so I will be able to set it up later next week.

Hi folks, I am fairly new here, reading, trying to understand but do have some knowledge with Unix and some SBC. Now the Helios64 is on arrival and I would like to know if I should change the fans immediately in order to get a quieter case. Is the NF-A8-PWM significantly less noisy than the stock ones? Or is there maybe a different route to go?!