bunducafe

Thanks @SIGSEGV for your post. I do very much appreciate it because at the end it comes down to exactly that: There are a few very keen developers and a bunch of users who like to use the software with their units - in that case the Helios64. But in return are not really willing to contribute. To be a bit more subjectively: I would love to contribute and I do so once in a while if I stumble upon some problems I could solve myself. Mostly related to a running system with OMV and Armbian If it comes to testing kernels and debug I am out of the game because I did not even manage to get the console working. That's mainly because I am with MACs here at the office and I simply could not get the console running on none of my machines. So on this side I would consider myself a complete noob which makes debugging kind of impossible to me. I might get a separate laptop with a non-mac unix system in the future just for this purpose. Meanwhile I am a bit far off in giving support on that kind of level unfotunately. That's also a reason why I am rather reading through the forum and usually not be one of the complainers as I know how much work the devs put in here and how good it usually works. A hickup from time to time is totally fine with me.

If you do fiddle around keep us posted, would be great to know if it works... I am somehow reluctant to try it at the moment as I need a running system. Because the mentioned workaround (updating bootloader) does not make the emmc fully writeable I would rather stick to the sd card at the moment.

Is there any need to format the emmc and do a rsync? I mean, if I roll back and the i/o errors on the emmc are gone shouldn't it boot flawlessly again and preserves the exact same state as before the update?

Thanks. As the sd card is working flawlessly I am not in need to do so right now. And with the emmc issue I cannot write on that thing anyway. But just in case: It's done with "dpkg -i" I suppose. No specific order, right?

Uh, I should have followed this thread a little bit earlier as I ran into the emmc issue (no write permission) and the system does not come up and I cannot manipulate anything. For now I am back with sd cards and will probably stick to it as I can make clones from the sdcard a bit easier with my setup here. Is there an easy way to roll back the actual kernel?

I am with Buster, but regarding the ondemand governor: I have set them from the very beginning from 400 and 1400 and the system has been running rocksolid after this.

Yes, just received that email, too. What a pity. I am quite satisfied with my Helios64 and I do hope it will last quite a bit... in the meantime I do hope that this forum remains the best source for trouble shooting. Thank you guys for your beautiful machines. Maybe it's there is a way to revive everything in the (not too far) future. Would be great!

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 in order to let the machine run full CPU speed and performance governor? I am happy with the machine, no doubt, at the end this is rather a question of how I can achieve the maximum speed if needed.

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 installed here but I certainly will do that again. I do recommend the OMV Backup Plugin so I can boot from the latest stable release via SDcard if I mess up with something. That's also nice.

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 Plugin. That's a bit of a nuisance but it is bearable if you do not boot your machine every day. In my case I had to remove the nofail, the mergerfs did mount immediately and then I did put the nofail in again. There might be a more elegant possibility but at least it is a remedy to get the helios working again. Jump over to the OMV-forums and do a search for LUKS + UnionFS + nofail and you find several threads about that issue. I have no idea if it is better to swith to the merferfsfolder plugin because I have no knowledge so far if I just can change the plugins without any errors.

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.