barnumbirr

Good shout, my Helios64 is unfortunately in a location where I can't easily plug in another computer to get serial access. Might try to dig out an old RPi...

This is what my uptime looks like. OMV5, plex and r/rutorrent with 5 12TB WDC disks (LVM). None of these reboots were triggered by me... Wish I could find were the problem lies, can't read the logs for debugging as the reboot is so abrupt that nothing gets written to disk.

Nicely done. Corruption of the armbianEnv.txt file is one of the remaining nagging issues on the Helios64. I suspect it is linked to the system instability but I've not been able to pinpoint the exact issue so far.

Can you try to boot from the SD card again, mount the eMMC and edit the /boot/armbianEnv.txt to increase verbosity (defaults to 1 which means less verbose, maximum value is 7). Please then post the logs.

I've already asked the question on Twitter but I'll ask here as Twitter might not be everyone's cup of tea:

Try and restart your Helios64 while connected to it via serial, you should then see the boot logs. If you need to increase verbosity of said logs, edit your armbianEnv.txt to contain the following: armbianEnv.txt Report back with the logs. Hope this helps.

Try kernel 5.10.16, that seems to fix most of the stability issues for me compared to 5.10.12.

My system is on a microSD card as armbian-config never managed to configure the eMMC correctly (never took the time to debug the issue unfortunately). My system did crash at some point while I was at work today but no logs have a trace of the crash. System just froze, solid blue 'System' LED. I'll probably downgrade to an earlier kernel...

SOLVED!!! Of course this was due to armbianEnv.txt being corrupt. Restoring the file from backups allows the device to boot cleanly again.

Just applied the latest update to my Helios64, here is what apt reported: The following packages will be upgraded: armbian-config armbian-firmware base-files device-tree-compiler file iproute2 libcairo2 libgnutls30 libgnutls30:armhf libmagic-mgc libmagic1 libnss-myhostname libpam-systemd libsystemd0 libudev1 linux-buster-root-current-helios64 linux-dtb-current-rockchip64 linux-image-current-rockchip64 linux-u-boot-helios64-current systemd systemd-sysv udev unzip This went just fine until it tried to setup systemd, the Helios then lost all network connection: Tr

No, don't need to perform fix if you're only ever going to use the 1Gbps interface AFAIK.

I've been running into the same issue for about a week or two, haven't had the time to dig into it though. armbian-config says the "Boot from eMMC - System on eMMC" step went fine but device won't boot after that. Haven't hooked a serial cable to it to see where it fails.

From the wiki: Source: https://wiki.kobol.io/helios64/sata/#sata-controller-diagram

I think the idea is great, the implementation might be a challenge. I'd say: leave it to up to someone else as even if Armbian Staff isn't involved, potential issues might reflect bad on the Armbian project, especially coming from armbian.com. If the interest was really that high, there would already be a dedicated subreddit full of people selling SBCs. (/r/homelabsales might count)

From the wiki: Source: https://wiki.kobol.io/helios64/sata/#sata-controller-diagram