Search the Community

I’m helping my friend set up Helios64 with OpenMediaVault as a media server. We’d manage to set it up as per your documentation mentioned on your wiki page but are stuck on SD-Card to eMMC migration. As after migrating with no error so far we’re still unable to boot the system without the SD-Card in Helios64. We still couldn’t figure out what could be the problem? Can you guys help?

Hi, I want to ask, if there's a way how to turn off Helios64 without the 100% fan spin. It only takes 1 second but it's very annoying when I want to turn it off during the night. Looking https://github.com/armbian/build/blob/master/packages/bsp/helios64/fancontrol.conf and https://wiki.kobol.io/helios64/pwm/ No luck :Z

Hi, For some reason my Helios64 took a nose dive today, so I hit the reset button and it wouldn't boot up. Plugged in to the serial console and this came out: I'm guessing the relevant lines are libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ... ERROR: Did not find a cmdline Flattened Device Tree Loading Ramdisk to f4f09000, end f5ee4ba4 ... OK FDT and ATAGS support not compiled in - hanging Any ideas on what to do from here please? I'm booting from an SD card which I have checked that it's OK by plugging it into my stationary computer and checking the fs. Crossing my fingers that there's just some command I need to run to generate some file and it'll just work again...

Dear H64-Friends, I've got the Armbian Debian installed with Linux Kernel 5.10 and Open Media Vault (OMV). I just use the basic functions for backing up files, nothing extraordinary. I am wondering what's the best strategy to update the Helios64 system concerning stability and getting no errors for backing up files (automatic USB-Backups). Keep it always up to date if there's an update available in OMV? Or just wait some weeks?

When there is a kernel panic the fans stop which causes the HDD and CPU temperatures to rise unchecked. I've just come back to find my board has crashed again and the HDD temperatures had risen above 60c which is not good. Is there a watchdog or boot setting to automatically reset the processor after a kernel panic ?

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: Tried rebooting, no luck. Can't get a serial console up and running as it won't go past 'Starting kernel...' The blue 'System' LED is on but doesn't blink. What can I do to help debug/fix this?

That newsletter indicated that USB-C to HDMI cables promised were still delayed. Is there an update on that? Thanks!

Hello together, i experienced network problems with Helios64 and latest Debian Buster Image. I cannot setup a static ip address after installation of OMV5, moreover it crashes on install. I double checked it on a fresh image without any changes and an immediate installation of OMV over softy. The result is the same. After the crash OMV is in fact available, but the network configuration is broken and a static setup doesnt work over the OMV UI, nor armbian-config, also the boot takes about 2-5 minutes due to whatever reason. armbianmonitor http://ix.io/2PPJ

I have installed Armbian 21.02 Ubuntu 20.04 Focal with Linux kernel 5.10.16 and OpenZFS 2.0.1-1 on my Helios64. Created a three-disk encrypted RAIDZ pool with the following command: sudo zpool create -f -o ashift=12 -O compression=lz4 -O atime=off -O acltype=posixacl -O xattr=sa -O encryption=aes-256-gcm -O keylocation=prompt -O keyformat=passphrase tank raidz1 /dev/disk/by-id/foobar1 /dev/disk/by-id/foobar2 /dev/disk/by-id/foobar3 Then I did a single sequential read benchmark with fio on /tank: cd /tank sudo fio --name=single-sequential-read --ioengine=posixaio --rw=read --bs=1m --size=16g --numjobs=1 --iodepth=1 --runtime=60 --time_based --end_fsync=1 This results in a speed of 62 MB/s, much lower than I would expect. I created exactly the same pool with three disks of the exact model (same batch) on Ubuntu 20.04 with Linux kernel 5.4.0 and OpenZFS 0.8.3 on a HPE ProLiant MicroServer Gen10, and the performance of the same benchmark is 232 MB/s. Does anyone have the same experience of this low encrypted ZFS performance on the Helios64? Is this because of the encryption? Looking at the output of top during the benchmark, the CPU seems to be taxed much, while on the HPE machine CPU usage is much less.

Hello, my nas is too noisy, do you know if it's possibile to change the fans with others that is silent? Regards.

Hi, everyone. The Kobo site is kind of difficult to navigate if you're looking for relevant information, but I came to the conclusion that this is the right place for support. Forgive me if I'm mistaken. I was wondering if someone could help me interpret these bootlogs from serial term when trying to boot my Helios64 from the EMMC. Following the instructions on Kobol's site, I flashed their u-boot image to an sd card, booted the Helios64 off of said sd, fetched the latest image of Armbian, unpacked that image, and flashed it from my laptop to the Helios64 via usbc to what I presume is the correct interface. Could it be that I messed up? Here's a quick example of the weird behaviour when I take the sd card out and turn on the machine: Basicall, it keeps repeating this dialogue but with different files. So, for the one above, it says "Retrieving file: pxelinux.cfg/01-64-62-66-d0-03-42", but then it'll go on and say "Retrieving file: pxelinux.cfg/C0A8018", and so on. It'll keep doing that for a bunch of files, after which there's no boot screen or login prompt or anything. I haven't managed to ssh into it, either, but it may be my mistake that I can't figure out how to do so. If I unplug the ethernet, it looks like this: I'm really dreading the idea that I have to take apart the chassis and jump the board so that I can boot from the sd card. I don't understand why the sd card wouldn't be before the emmc in Helios64's boot order. That seems absurd to me. Anyway, here's at least part of the log. I didn't feel like sitting around to let it go through all the files:

Hey, I think a dedicated topic for ZFS on Helios 64 is needed. Many people want to have it As we know, and many of us playing with dev builds for helios ,it is no easy to work with ZFS I wrote few scripts maybe someone of You it can help in someway. Thanks @jbergler and @ShadowDance , I used your idea for complete it. The problem is with playing with OMV and ZFS plugin. then dependencies remove our latest version of ZFS. I tested. everything survived but ZFS is downgraded to latest version from repo for example: root@helios64:~# zfs --version zfs-0.8.4-2~bpo10+1 zfs-kmod-2.0.0-rc6 root@helios64:~# uname -a Linux helios64 5.9.11-rockchip64 #trunk.1 SMP PREEMPT Thu Nov 26 01:32:45 CET 2020 aarch64 GNU/Linux root@helios64:~# I tested it with kernel 5.9.10 and with today clean install with 5.9.11 First we need to have docker installed ( armbian-config -> software -> softy -> docker ) Create dedicated directory with Dockerfile ( we will customize ubuntu:bionic image with required libraries and gcc 10 . in next builds we can skip this step and just customize and run build-zfs.sh script) mkdir zfs-builder cd zfs-builder vi Dockerfile FROM ubuntu:bionic RUN apt update; apt install build-essential autoconf automake bison flex libtool gawk alien fakeroot dkms libblkid-dev uuid-dev libudev-dev libssl-dev zlib1g-dev libaio-dev libattr1-dev libelf-dev python3 python3-dev python3-setuptools python3-cffi libffi-dev -y; apt install software-properties-common -y; add-apt-repository ppa:ubuntu-toolchain-r/test; apt install gcc-10 g++-10 -y; update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-10 10; update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-10 10 Build docker image for building purposes. docker build --tag zfs-build-ubuntu-bionic:0.1 . Create script for ZFS build vi build-zfs.sh #!/bin/bash #define zfs version zfsver="zfs-2.0.0-rc6" #creating building directory mkdir /tmp/zfs-builds && cd "$_" rm -rf /tmp/zfs-builds/inside_zfs.sh apt-get download linux-headers-current-rockchip64 git clone -b $zfsver https://github.com/openzfs/zfs.git $zfsver-$(uname -r) #create file to execute inside container echo "creating file to execute it inside container" cat > /tmp/zfs-builds/inside_zfs.sh <<EOF #!/bin/bash cd scratch/ dpkg -i linux-headers-current-*.deb zfsver="zfs-2.0.0-rc6" cd "/scratch/$zfsver-$(uname -r)" sh autogen.sh ./configure make -s -j$(nproc) make deb mkdir "/scratch/deb-$zfsver-$(uname -r)" cp *.deb "/scratch/deb-$zfsver-$(uname -r)" rm -rf "/scratch/$zfsver-$(uname -r)" exit EOF chmod +x /tmp/zfs-builds/inside_zfs.sh echo "" echo "####################" echo "starting container.." echo "####################" echo "" docker run --rm -it -v /tmp/zfs-builds:/scratch zfs-build-ubuntu-bionic:0.1 /bin/bash /scratch/inside_zfs.sh # Cleanup packages (if installed). modprobe -r zfs zunicode zzstd zlua zcommon znvpair zavl icp spl apt remove --yes zfsutils-linux zfs-zed zfs-initramfs apt autoremove --yes dpkg -i "/tmp/zfs-builds/deb-$zfsver-$(uname -r)"/kmod-zfs-$(uname -r)*.deb dpkg -i "/tmp/zfs-builds/deb-$zfsver-$(uname -r)"/{libnvpair1,libuutil1,libzfs2,libzpool2,python3-pyzfs,zfs}_*.deb echo "" echo "###################" echo "building complete" echo "###################" echo "" chmod +x build-zfs.sh screen -L -Logfile buildlog.txt ./build-zfs-final.sh

I have run into this issue multiple times and the process flow is this: Flash image "Armbian_20.11.6_Helios64_buster_current_5.9.14.img" to a micro SD card. Run through the config (installing OMV with SAMBA) Kick over to the OMV to configure the share / media so its available on my network Runs for some time (this last install was running for maybe a few weeks before it triggered a Kernel panic) Power off. Power on. Board boots, hangs on "Starting Kernel..." Is there some trick I am missing to get this thing to actually boot / reboot correctly? Troubleshooting info: No jumpers are shorted. I had a similar issue with a previous img as well.

Hello everybody, im experiencing a similar problem. Sometimes my WD RED 12 TB HDD is not recognized in that slot its in, when i change it to any other it works again. Nevertheless it seems this problem doesnt only apply to one specific slot, but is changing from time to time. EDIT: The LED of that slot doesnt turn on, yet the drive starts and runs Do anybody experience the same problem, or know any help? Thank you in advance. Best Regards.

Had anyone tested DAS mode performance with Capture One? Or could someone explain to me how it works? Also, would C1 show the DAS mode and NAS mode as seperate volumes or is it smart enough to show up as the same one? Background: Capture One doesn't work well with network drives. Editing images, moving raw files, even saving catalog backups is dramatically slower on a NAS than a DAS or internal drive. It doesn't matter how fast the drive or network is. Its a long standing bug they're always quick to say they aren't prioritizing fixing. I've looked at other NAS's that do a DAS mode by running a 10GBE connection over thunderbolt and that's a great solution in every situation except for working with C1. Has anyone tried this?

Hello, I've bought 3 new identical drives and put 2 of them in the Helios64 and 1 onto my desktop. I ran smartctl longtest+shortest on both drives simultanously but all of them were aborted/interupted by host. `# /usr/sbin/smartctl -a /dev/sda` Output: http://ix.io/2OLt On my desktop the longtest from smartctl succeeds without error and all 3 drives received the same care, I just bough them and installed them, so unlikely the drives are physically damaged. The complete diagnostic log: http://ix.io/2OBr So anyone got an idea why are my SMART extended tests being canceled? Note: I've tried even the trick with running background task to prevent drives from some vendor sleep `while true; do dd if=/dev/sda of=/dev/null count=1; sleep 60; done`

Hi everyone, I have installed openmediavault and zfs. Since yesterday I have this error: Failed to execute command 'export PATH = / bin: / sbin: / usr / bin: / usr / sbin: / usr / local / bin: / usr / local / sbin; export LANG = C.UTF-8; zfs list -H -t snapshot -o name, used, refer 2> & 1 'with exit code' 1 ': The ZFS modules are not loaded. Try running '/ sbin / modprobe zfs' as root to load them. Click "show details" Error # 0: OMV \ ExecException: Failed to execute command 'export PATH = / bin: / sbin: / usr / bin: / usr / sbin: / usr / local / bin: / usr / local / sbin; export LANG = C.UTF-8; zfs list -H -t snapshot -o name, used, refer 2> & 1 'with exit code' 1 ': The ZFS modules are not loaded. Try running '/ sbin / modprobe zfs' as root to load them. in /usr/share/php/openmediavault/system/process.inc:182 Stack trace: # 0 /usr/share/omvzfs/Utils.php(438): OMV \ System \ Process-> execute (Array, 1) # 1 /usr/share/omvzfs/Utils.php(394): OMVModuleZFSUtil :: exec ('zfs list -H -t ...', Array, 1) # 2 /usr/share/openmediavault/engined/rpc/zfs.inc(194): OMVModuleZFSUtil :: getAllSnapshots () # 3 [internal function]: OMVRpcServiceZFS-> getAllSnapshots (Array, Array) # 4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array (Array, Array) # 5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV \ Rpc \ ServiceAbstract-> callMethod ('getAllSnapshots', Array, Array) # 6 / usr / sbin / omv-engined (537): OMV \ Rpc \ Rpc :: call ('ZFS', 'getAllSnapshots', Array, Array, 1) # 7 {main} Also I can no longer access the folders on the disks. Can someone help me?

Hello, I installed OMV on my Helios64 and created a share. The device stays online and works well for hours and then at some point eth0 goes offline and no longer communicates. The only way to restore connectivity is with a reboot. I looked at the logs and dont see anything jumping out at me as to why this happens but I could very easily be missing something or the log didnt capture the event. I have not yet tried to console in through the USBc port when this occurs but will try next time. Has anyone else seen this issue or fixed it?

CURRENT branch (Linux Kernel 5.10) Feature Support Status Remarks Shutdown OK Reboot OK Suspend to RAM Not Supported USB host controller refuses to enter suspend mode 2.5G Ethernet (2.5G speed) OK TX offload disabled by default, can be enabled for better performance 2.5G Ethernet (1G speed) Performance issue Requires hardware fix. Main Power/UPS status OK Status can be read from sysfs Battery Charging OK Status can be read from sysfs UPS configuration OK Auto shutdown after 10 min of power loss. USB Type C - Host OK use dwc3-0-host overlay. Enable P13 jumper to be able to use USB 2.0 device. USB Type C - Gadget OK use overlay to enable USB device mode. refer to this link USB Type C - DisplayPort OK eMMC Boot OK SPI Boot Not Supported Recovery Button OK To use maskrom, jumper P13 must be enabled. USB LED Not Supported usbport led trigger does not support activity and only works with USB 2.0 device LAN LED OK default to eth0 activity Wake On LAN Not Supported Suspend still have issue Armbian 21.02

Hi guys, My Helios64 keeps going offline, it has this red light come on the front panel but i am not sure what it means exactly. This happens once every few weeks, the system is fine after a reboot. What does this red light mean exactly? Is there anything i can do to prevent these breakdowns? Cheers,

Had my Helios up and running for a few months now running off SD card, but there was a message (can't remember where) to not make the install you 'final' setup as things were still in development. I've been keeping track of the 'what works and doesn't' , but as there are no updates in 6 weeks, is the general consensus that we've reached stability and its time to transfer to the eMMC?

Hi. My helios64 always crashes with this method : [environment] 1TB m.2 sata ssd for system 16TB seagate exos on data drive 18TB WD Ultrastar DC550 on data drive Linux helios64 5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 aarch64 aarch64 GNU/Linux about 620,000 files on data drive. [method1] #sync #sysctl -w vm.drop.caches = 3 #ls -CFR [datadir] > [tmp dir] #ls -1lFR [datadir] > [tmp dir] #zip -j [tmpdir] filelist.zip #sync >>>>>>> Crash (blinking Red LED) [method2] (First step) via samba , on Windows , see property of all 620,000 files. (Second step) on SSH "sysctl -w vm.drop_caches = 3" >>>>>> Crash(blinking Red LED)

Has anybody got DAS mode working using USB-C ? Using: Armbian 20.08.21 Buster with Linux 5.8.17-rockchip64 I was not certain, I thought I read it was supported. I was hoping to use Windows 10 via USB 3.1 --> Helios64 USB-C to copy large video library. Note; using UART via COM3 is working as expected. Note; in windows I do remember seeing some USB error loading some USB driver; would it be related to some missing driver?int Any successful implementation of USB DAS interface; I would be happy to hear from you.

Hello everybody, Is it possible to use the box with another card (odroid n2 for example)? Thanks a lot

Trying to understand this issue. If I ONLY need the 1Gbs (LAN1) ethernet connection and DO NOT need the 2.5Gbs (LAN2) connection, do I need to perform the "Fix" for this issue? I'll be using Armbian Buster for this device.