Search the Community

After installing armbian bookworm the fans are always at maximum. Here is how I solved. Trying to figure out what is not working I try to run the related service systemctl start fancontrol.service but it does not start. So I check the latest errors: systemctl status fancontrol.service I obtain Failed ...fancontrol.service: Failed to locate executable /usr/sbin/fancontrol so, fancontrol is simply not there and apt can't find it for installation. I took the old sd card and copied the fancontrol to /usr/sbin/ Than make it executable with: chmod +x /usr/sbin/fancontrol than systemctl start fancontrol.service systemctl enable fancontrol.service As soon as I started the service, voilà, the fan started to... blowing only when needed: problem solved! Attached you find the fancontrol file. fancontrol

Hello, I would like to sell my helios4 2gb ecc. It's served me well, I've outgrown it and is no longer required Posting on here incase anyone is interested Fyi, I'm UK based for postage

After upgrade to version 5.15.72, fancontrol service fails to start, due to missing /dev/fan-j17 There is some information in dmesg: pwm-fan j17-pwm: error -EBUSY: Could not get PWM

Hi my good old helios4 with OMV had been running for few years without big issue. but it suddenly lost all SATA HDD. OMV shown the 2 HDD are missing. i reboot it and during the boot i saw couple of error, failure... so decided to reinstall armbian by a new SD card. but tried 2 new cards with new images.. i got same error ... as attached log file. it seems during booting the kernel, not sure it is u-boot or kernel report it cannot find the root file system. i am not sure it is the SD card issue or it it the Helios4 board issue or any other issue. could anyone help? bootlog.txt

Hello all! After upgrading to OMV 7 and Debian 12 my OLED display remains dark. I am using Kobol Helios 4 NAS. Can anyone tell me where the problem is? When i try to execute git clone https://github.com/kobol-io/sys-oled.git cd sys-oled sudo ./install.sh I get the following error message via SSH. Installing luma.oled library error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install. If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed. If you wish to install a non-Debian packaged Python application, it may be easiest to use pipx install xyz, which will manage a virtual environment for you. Make sure you have pipx installed. See /usr/share/doc/python3.11/README.venv for more information. note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification. Installing sys-oled files 'etc/sys-oled.conf' -> '/etc/sys-oled.conf' 'bin/sys-oled' -> '/usr/local/bin/sys-oled' 'share/sys-oled/C&C Red Alert [INET].ttf' -> '/usr/local/share/sys-oled/C&C Red Alert [INET].ttf' 'share/sys-oled/helios4_logo.png' -> '/usr/local/share/sys-oled/helios4_logo.png' 'system/sys-oled.service' -> '/etc/systemd/system/sys-oled.service' Enabling sys-oled at startup Does anyone have an Idea what to do?

Support for bullseye dropped?

Hello everybody, I would like to sell my helios4 and helios64. They weren't in operation much and are like new. So they are perfect for spare parts or to use them as a complete replacement. I really like the products but I don't want the hustle of fiddling around with every new armbian release. So if anybody is interested you can contact me and/or write here a comment. Thank you very much!

... however Armbian_23.8.1_Helios4_bookworm_current_6.1.50.img.xz worked well and was then upgraded through apt to 24.2.1 / 6.6.16. I was then able to install OMV 7, Plex media server and Transmission on top. warning - the ethernet ports change, breaking scripts where they're hardcoded, e.g the wol service. changing the port in two places in the file and running systemctl daemon-reload ; systemctl restart helios4-wol seems to be running ok. This details the patch: diff --git a/lib/systemd/system/helios4-wol.service.orig b/lib/systemd/system/helios4-wol.service index 965eb74..451b857 100644 --- a/lib/systemd/system/helios4-wol.service.orig +++ b/lib/systemd/system/helios4-wol.service @@ -1,10 +1,10 @@ [Unit] -Description=Enable Wake-on-LAN for Helios4 eth0 +Description=Enable Wake-on-LAN for Helios4 end1 After=network-online.target Wants=network-online.target [Service] -ExecStart=/sbin/ethtool -s eth0 wol g +ExecStart=/sbin/ethtool -s end1 wol g Type=oneshot [Install] I have not been able to get the sys-oled to display however - it is detected ok but only shows gibberish. I tried all models to no avail. To get the code running, I had to install python3-luma.core and python3-luma.oled. Any ideas? Thanks

Seeing the SOC go upto 80-90C, is there any fan mod or way to reduce temps? for now, added a external fan, removed the case, temps are around 50 Running OMV6 on bullseye

Hi All, I'm a happy user of a Helios4, and have been for several years now. However, at some point it will be challenging to continue to support it, and I'd rather be proactive about maintaining access to my data than scrambling around. Do people here have recommendations on current hardware that can replace the Helios4? It would need to meet the baseline hardware requirements of the existing hardware. Bonus points if one can re-use the laser-cut case Thanks!

Hi all, just a quick note here that I am running 23.05 Bookworm successfully on Helios4 with ZFS. I did a clean install with a self-built image. Why the self-build? For two reasons: I wanted to have working fancontrol and that required the recent patch of @Heisath - https://github.com/armbian/build/pull/5392 I ran into an issue with not being able to install kernel headers (see below) so I needed to build an image with kernel headers built-in Build steps I wanted the release version so I did this in a clean build environment (WSL2 Ubuntu): git clone --depth=1 --branch=v23.05.2 https://github.com/armbian/build And then manually place this file in your local tree https://github.com/armbian/build/blob/main/patch/kernel/archive/mvebu-6.1/92-mvebu-gpio-remove-hardcoded-timer-assignment.patch. You need to touch .ignore_changes. Then run compile.sh INSTALL_HEADERS=yes. Testing After booting the image, I only did the following steps: systemctl disable helios4-wol # not sure why this service is failing but I do not use this anyway apt update apt upgrade reboot apt install zfs-dkms apt install zfsutils-linux Kernel header issue This is after apt update / apt upgrade / reboot. The repo seems to be out of sync. Also armbian-config fails altogether with a grep error (something with maximum count). root@helios4:~# apt search linux-headers|grep mvebu WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-headers-current-mvebu/bookworm 23.02.2 armhf Linux kernel headers for 5.15.93-mvebu on armhf current linux-headers-edge-mvebu/bookworm 23.02.2 armhf Linux kernel headers for 6.1.11-mvebu on armhf edge root@helios4:~# uname -a Linux helios4 6.1.36-mvebu #2 SMP Wed Jun 28 11:12:41 CEST 2023 armv7l GNU/Linux root@helios4:~# cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=helios4 BOARD_NAME="Helios4" BOARDFAMILY=mvebu BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=961a103 VERSION=23.05.1 LINUXFAMILY=mvebu ARCH=arm IMAGE_TYPE=user-built BOARD_TYPE=conf INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage FORCE_BOOTSCRIPT_UPDATE=yes VENDOR=Armbian REVISION=23.05.1 BOOTSCRIPT_FORCE_UPDATE="yes" BOOTSCRIPT_DST="boot.cmd" root@helios4:~#

I'm using Armbian 23.02.2 Bullseye with Linux 5.15.93-mvebu and OMV6. I want to upgrade to Armbian 23.5.1 Bookworm with Linux 6.1.30. Up to now no upgrade is offered. If the answer to the thread title is "yes" I need help how to do the upgrade. If the answer is "no" I kindly ask for information about the reason not to be able to upgrade. By the way: Helios4 is a maintained platform, maintainer is @Heisath

I'm using Armbian 21.08.8 (Bullseye). I want to upgrade to Armbian 22.02.1 but "apt-get update" doesn't offer anything. Reason seems to be that <mirror>/apt/dists is from Feb 1st 2022. OTOH <mirror>/dl contains the new release but "starting from scratch" (download image, write SDcard) implies that I have to rebuild my OMV6 on top of Armbian. Question: When can I expect that <mirror>/apt/dists will be refreshed? Or is there any other way to upgrade my installation?

Helios4 can boot directly from the sata disk nr 1, without the need to switch from the SD or the eMMC. I personally tried setting SW1 to 11100 and using u-boot-sata for Clearfog, which shares the same uSOM and the system booted regularly, obviously the system didn't recognize many devices being u-boot for another board. I tried to compile a version of u-boot for sata trying to integrate the changes present in https://solidrun.atlassian.net/wiki/spaces/developer/pages/287212134/A38X+U-Boot in the U-boot build instruction and sources for Helios4 present in the Kobol Wiki but my skills are not sufficient for such a job. In the binaries available for Helios4 at https://imola.armbian.com/beta/pool/main/l/linux-u-boot-helios4-current/ there are only u-boots for uart, flash and mmc. Would it be possible to have the sata version in future releases? Thanks in advance and for all the work done.

I've been having issues with my Helios4 becoming unresponsive when it's been up for a while. I decided to do some more thorough investigating and found that it was having problems writing to the sdcard. That led to the following entries in syslog: Dec 20 21:36:43 helios-backup kernel: [318645.034243] mmc0: Timeout waiting for hardware interrupt. Dec 20 21:36:43 helios-backup kernel: [318645.034254] mmc0: sdhci: ============ SDHCI REGISTER DUMP =========== Dec 20 21:36:43 helios-backup kernel: [318645.034258] mmc0: sdhci: Sys addr: 0x00000008 | Version: 0x00000202 Dec 20 21:36:43 helios-backup kernel: [318645.034263] mmc0: sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000001 Dec 20 21:36:43 helios-backup kernel: [318645.034267] mmc0: sdhci: Argument: 0x0084a0d0 | Trn mode: 0x0000002b Dec 20 21:36:43 helios-backup kernel: [318645.034271] mmc0: sdhci: Present: 0x01e60006 | Host ctl: 0x00000017 Dec 20 21:36:43 helios-backup kernel: [318645.034274] mmc0: sdhci: Power: 0x0000000f | Blk gap: 0x00000000 Dec 20 21:36:43 helios-backup kernel: [318645.034278] mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x00000207 Dec 20 21:36:43 helios-backup kernel: [318645.034282] mmc0: sdhci: Timeout: 0x0000000e | Int stat: 0x00000000 Dec 20 21:36:43 helios-backup kernel: [318645.034285] mmc0: sdhci: Int enab: 0x03ff000b | Sig enab: 0x03ff000b Dec 20 21:36:43 helios-backup kernel: [318645.034289] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000 Dec 20 21:36:43 helios-backup kernel: [318645.034292] mmc0: sdhci: Caps: 0x25fcc8b2 | Caps_1: 0x00002f77 Dec 20 21:36:43 helios-backup kernel: [318645.034296] mmc0: sdhci: Cmd: 0x0000193a | Max curr: 0x00000000 Dec 20 21:36:43 helios-backup kernel: [318645.034299] mmc0: sdhci: Resp[0]: 0x00000900 | Resp[1]: 0x00000000 Dec 20 21:36:43 helios-backup kernel: [318645.034303] mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000900 Dec 20 21:36:43 helios-backup kernel: [318645.034306] mmc0: sdhci: Host ctl2: 0x00000000 Dec 20 21:36:43 helios-backup kernel: [318645.034309] mmc0: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x78275208 Dec 20 21:36:43 helios-backup kernel: [318645.034313] mmc0: sdhci: ============================================ Dec 20 21:36:46 helios-backup kernel: [318648.042018] mmc0: Card stuck being busy! __mmc_poll_for_busy Dec 20 21:36:48 helios-backup kernel: [318649.277911] mmc0: card never left busy state Dec 20 21:36:48 helios-backup kernel: [318649.277918] mmc0: tried to HW reset card, got error -110 Dec 20 21:36:48 helios-backup kernel: [318649.277923] mmcblk0: recovery failed! Dec 20 21:36:48 helios-backup kernel: [318649.277947] blk_update_request: I/O error, dev mmcblk0, sector 8691920 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Dec 20 21:36:48 helios-backup kernel: [318649.277958] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:348: I/O error 10 writing to inode 382819 starting block 1086491) Is it possible this is due to the power supply starting to go bad? I haven't yet tried using different sdcards, but that would be my next step. Has anyone else seen this?

Hello everyone! After my Helios4 had been laying in a cardboard box for a long time after moving houses, I decided it was time to once again set it up as an NAS. I was previously running Open Media Vault (OMV) with 4 disks in xfs and using MergerFS for unionizing three of them at a single mount point and then using Snapraid for the fourth disk. OMV worked pretty well for me but I go somewhat irritated from time to times because how it decides to thing in it's own way. But now I when I re-installed it (after getting a new PSU) I went with Armbian instead to keep it closer to "standard" linux. I think I will still go with MerverFS and Snapraid this time also but I also wonder what you guys and gals are using! For example: - What filesystem are you using? xfs, btrfs or maybe zfs? - Are you running raid, mergerfs or something else? - How are making the storage avalible to other hosts? NFS, SSHFS? - Are you running some kind of admin UI to manage your Helios?

After upgrading to the 5.15 kernel, I noticed that the fan control is only able to control one of the fans, while the other spins at full speed. Experimentally I found out that the PWM control for the second fan is ineffective: helios4# uname -r 5.15.86-mvebu helios4# echo 0 > /dev/fan-j10/pwm1 # works, fan is off helios4# echo 255 > /dev/fan-j10/pwm1 # works, fan at full speed helios4# echo 0 > /dev/fan-j17/pwm1 # does nothing, full speed helios4# echo 255 > /dev/fan-j17/pwm1 # does nothing, full speed Some digging around I found that 92-mvebu-gpio-remove-hardcoded-timer-assignment.patch has been ported to 5.15, but it doesn't seem to work for me.

Straightforward! See signature. Thanks to the team.

For marvell-mvebu build DRBD is not supported, the module is missing in either current and edge config a grep of CONFIG_BLK_DEV_DRBD in build/config/kernel from the git build repo shows that most boards have DRBD compiled as module except some few exceptions. One of these few exception is mvebu (ClearFog Base/Pro, ESPRESSObin, Helios 4). I don't understand why. DRBD is a very nice and secure block device which provides network block replication (raid over network), and it is widely used. DRDB compile and work flawlessly on helios4 with the mvebu kernel. But we are obliged to compile the kernel or only the module, which is somewhat painful. As I have an helios4 which provides a DRBD node, I first compiles three years ago the module using the current kernel headers,. Then I refrained from updating since I was needing this DRDB node. But now I need to update to buster, so I updated to the current branch. Of course I lost my DRBD device, and so I compiled a home made kernel. This is now technically very easy with the new build environment and docker. compile.sh and the associated set of bash scripts are very handy and well conceived. Thank you for the developers who did this work. But with my servers t has been nevertheless very long and painful. I have only low power servers, and my gateway upper download rate is 300KB. So when I tried the script it could not download anything, I found that it gives to aria2c a lowest speed limit of 500K, so no hope to download something on my network. I tried to change this limit. I tried many value, usually I could down load at 220K, but it seems that the speed can slow down during short period of time, so my downloads aborted. I had to reduce this minimal speed to 70KB to be able to download the software. Then I compiled the kernel 14h of compilation on my machine! Next time I will try either to launch a temporary instance on a VPS with better bandwidth, and/or install DISTCC, but I have never tried discc in docker, and I have to learn. Now running current-mvebu_22.11.0-trunk with kernel 5.15.76, drbd works flawlessly on helios4. But for next release I strongly wish that it would be incorporated in the distribution. I think it could be useful for people looking fr a server to support a drbd node. But how to request it, posting in the github issues? doing a PR seems quite overkill to just replace 'n' by 'm' in CONFIG_BLK_DEV_DRBD.

System successfully upgraded. No problems detected (so far). Thanks to the team.

Hey, the last time my Helios4's PSU blew I suspect was due to a power overload, with the PSU not being able to deal with all 4 HDDs doing active work (this also killed one of the HDDs in my array). Based on the system log, it looked like the system was doing a regular integrity checks on all 4 HDDs at once (!). I would like to either disable the integrity check altogether, or more ideally, spread it out. I have two RAID-1 arrays, and there is no reason for all four drives to be checked simultaneously. For example, I can check one of the arrays (two HDDs) and then once that is done, the second array (the other two HDDs) after. Does anyone know where the code/script for the integrity check lives? The closest I found was /etc/cron.daily/mdadm which runs mdadm --monitor --scan --oneshot but from the manpage description it is unclear to me whether that is superficial check or that may actually invoke a deep and lengthy integrity check.

This is with armbian 22.02 bullseye. phross@helios4:~$ uname -a Linux helios4 5.15.26-mvebu #trunk.0002 SMP Thu Mar 3 10:15:53 UTC 2022 armv7l GNU/Linux phross@helios4:~$ cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 0.00 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 0.00 ms. I remember reading discussions about issues with cpufreq patches causing issues on armada-38x socs. Is the cpufreq driver for armada-388 still not working?

Hi, I have a Armbian 22.02.1 with Linux 5.10.60-mvebu with buster debian packages. Its possible to update bullseye a not lost my storage raids?

Hello, I know that Kobol is out of Business.. But I am thinking...what if my helios4 motherboard die...? To mitigate that, I want to acquire new motherboard. Does any one knows how I could get one? Thanks in Advance