19 19

About This Club

Dedicated section for talk & support for the Helios4 and Helios64 open source NAS. Lead and moderated by the Kobol Team.
  1. What's new in this club
  2. Some Helios64 had issues with CPU freezes or other instabilities. If you buy one you should make sure that you can give it back if it is one of those. Cheers ebin-dev
  3. Hello! I have connected the WD 10TB RED HDD via external USB 3.0 enclosure to one of the USB 3.0 Ports on the HELIOS4. Unfortunately the speeds don't exceed 45 MB/s. when running RSYNC jobs. On the PC I can completely use the speed of the GBit Port.. When connected to the USB Ports of HELIOS4 the speeds are low. Can somebody help? The external enclosure is from UGREEN. HDD is NTFS formatted. Any advice will be gratefully appreciated.
  4. I will sell my helios64. never got a chance to use it as i went with a pc for server.
  5. Hi, I'm selling my Helios64. It's just too much work for me to keep the system stable. Moreover, I'm moving to a bigger x86 system. Here is the link from German ebay-Kleinanzeigen: https://www.ebay-kleinanzeigen.de/s-anzeige/kobol-helios64-open-source-nas/1948286131-225-990?utm_source=mail&utm_medium=social&utm_campaign=socialbuttons&utm_content=desktop I'm happy to send it abroad, however, you have to cover the shipping cost. Cheers, Julius
  6. Go ahead, OMV6 works fairly well with the Helios64... there are some bits and pieces that are not completely ported (plugins for example) and some need a bit of adjustment whatsoever. But all in all it is okay. I am running OMV6 together with SnapRaid. MergerFS and Luks I am running outside of OMV as I do find it easier to customize for my needs.
  7. Hello, I have a Helio64 not yet configured and I would like to be able to install the latest image available on https://armbian.hosthatch.com/dl/helios64/archive/ and especially to install the latest OpenMediaVault 6 version. Do you think this is possible ? Or will OpenMediaVault 6 not be available from armbian-config? As I write this post, the latest image available for Helios64 is Armbian_21.05.9_Helios64_bullseye_current_5.10.63.img.xz I thank you for your help Flolm
  8. Wanted to share my unfortunate experience today of trying to do a fresh install of a newer armbian version in order to accommodate OMV 5 on my Helios4. Was doing everything as usual and after the first boot from the new SD card tried to run armbian-config while still attached to the serial console. That proved to be a mistake as it started some auto install script type of thing and wiped one of my hard drives. Also the GUI wasn't showing properly. The exact same thing happened when I tried to reproduce the same steps. Should have been wiser and connected via SSH after inital boot to go from there. No such thing happened when running armbian-config via SSH for the first time. I am running Mac OS Big Sur and have the 1.4.7 FTDI VCP beta driver installed. The command I was running to connect was screen /dev/tty.usbserial-X 115200 -L. Fortunately the drive that was wiped was a redundancy drive.
  9. Exactly the same happened to me a few weeks ago. Replaced the PSU. Also ordered some new capacitors for the old PSU.
  10. Never mind ... it was the PSU! I took it apart and there was that magic smoke smell ... all the three output capacitors where popped and dried. I've replaced them and now the Helios4 is booting up again. She's alive!
  11. Similar issue here. Suddenly no connection, I took all apart. I connected the board to the power with no fan and no HD: - the Power indicator green led (LED 8) and - the ethernet port yellow led are blinking, - with a clicking sound. All of them at a same time, a little bit more than 1 Hz. No serial connection. Molex has no 12V and 5V is floating between 0 and 2V. I already tried pushing and holding the reset button with power stable and power rising, nothing. Fun thing when I disconnect the power the clicking and blinking will slowly fade away. I think she's gone.
  12. @RockBian it wasn’t my intention to color the issue black and white. My statement was based on that most user accounts have been from users of WD REDs. I personally believe this issue is far more prevalent than made out in this thread. It’s simply that triggering the issue may require time and the right kind of workload. So either people don’t trigger the issue or they may not even notice it unless they’re checking system logs. I hope your new disks work out for you. Either way, I never tried any other disks in my Helios and probably never will considering there’s no further development and Armbian used to break seemingly every other day (a while back).
  13. As you can read earlier in this thread I had a Toshiba which after half a year acted up in a Helios, while it run fine in another NAS, It's exchanged by a WD Red which is going strong since then. (But it didn't last six months, so far).
  14. @flowerThe 2.5G interface (eth1) indeed operates absolutely reliable if connected to a 2.5G switch - even without the hardware mod and using current Armbian Bullseye (kernel downgraded to 5.10.43). My interfaces are managed by systemd-networkd - the config files for the bridged setup are attached below. With this configuration the interfaces receive ipv4 and link local ipv6 addresses. Net transfer rates are around 255 MBytes/s (a nice alternative to bonding two 1Gig Ethernet interfaces). Armbian 21.08.6 Bullseye with Linux 5.10.43-rockchip64 # cd /etc/systemd/network/ # ls -la total 20 drwxr-xr-x 2 root root 4096 Nov 16 14:42 . drwxr-xr-x 6 root root 4096 Nov 26 07:00 .. -rw-r--r-- 1 root root 30 Nov 26 2020 br0.netdev -rw-r--r-- 1 root root 233 Oct 10 19:27 br0.network -rw-r--r-- 1 root root 40 Nov 16 14:42 eth0.network # cat br0.netdev [NetDev] Name=br0 Kind=bridge # cat br0.network [Match] Name=br0 [Network] IPForward=yes DHCP=no Address=192.168.xxx.xxx/24 Gateway=192.168.xxx.xxx DNS=192.168.xxx.xxx # cat eth0.network [Match] Name=eth1 [Network] Bridge=br0 # networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 ether off unmanaged 3 br0 bridge routable configured 4 eth1 ether enslaved configured 5 lxcbr0 bridge no-carrier unmanaged 6 vethpivccu ether degraded unmanaged 6 links listed.
  15. I have been trying for a while now the edge kernels and I have found that after the HW-mod (above) the network bonding has started to work... not consistently but once setup, the next reboot will actually enable the full network bonding. Currently I'm running 5.15.4, had to rebuild ZFS but that was it. Packages I've upgraded: - linux-dtb-edge-rockchip64/focal 21.11.0-trunk.65 arm64 - linux-headers-edge-rockchip64/focal 21.11.0-trunk.65 arm64 - linux-image-edge-rockchip64/focal 21.11.0-trunk.65 arm64 - Package: zfs-dkms - Version: 2.1.1-0york0~20.04 - Priority: optional - Section: kernel - Source: zfs-linux $ cat /proc/net/bonding/nm-bond0 Ethernet Channel Bonding Driver: v5.15.4-rockchip64 Bonding Mode: transmit load balancing Primary Slave: None Currently Active Slave: eth1 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 Slave Interface: eth1 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 64:62:66:xx:xx:xx Slave queue ID: 0 Slave Interface: eth0 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 64:62:66:xx:xx:xx Slave queue ID: 0
  16. I want to buy a HELIOS64 NAS, is there any more for sale, please contact me at fengjiannan2010@163.com
  17. @meymarce it’s most likely related, and not due to bad disks. All my disks have received a bunch of UDMA_CRC_Error_Count due to the Helios. I’ve since completely stopped using the Helios and put the same disks inside an ASUSTOR. Zero issues. Basically don’t put WD REDs in a Helios, or be prepared to have a bad time, heh.
  18. @BipBip1981 how is that related to the original problem? Looks to me like you get SMART warnings cause the disk is failing.
  19. Hi, I have same problem with WD Red 8to (WDC WD80EFBX-68AZZN0). In slot 3 Depend of drive, some are more or less sensible Best configuration without or (with less) error (i test again...) is: slot 1: WDC WD80EFAX-68KNBN0 slot 2: WDC WD80EFAX-68KNBN0 slot 3: TS256GSSD370S slot 4: WDC WD80EFBX-68AZZN0 slot 5: WDC WD80EFBX-68AZZN0 harddrive in slot 5 was in slot 3 before and i had: 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 11 in: Error 11 occurred at disk power-on lifetime: 46 hours (1 days + 22 hours) Bye.
  20. Hi, I thought this forum did support on the Helios{4,64} regardless of the OS since Kobol is now closed. More, the issues I encounter testing the Armbian patches can be helpful for the future Armbian releases (I had the eMMC issues long time before many Armbian users were impacted with the Buster update). I did tried to apply the Armbian patches for kernel 5.15, but they fail because Helios4 and 64 are now mainlined. But not problem, I will try to fix it by myself, and report back the solution here. I have the skills to do it. BTW I have the same issue with vanilla kernel 5.15 and Helios4. I will test it first on the helios4 because it's not used anymore. Kind regards, Xavier Miller
  21. The power cable you bought probably will not work. Check the pinout and connections + voltages. Compare with Helios64 here: https://wiki.kobol.io/helios64/sata/#hdd-power https://wiki.kobol.io/helios64/sata/#j8-pinout https://wiki.kobol.io/helios64/sata/#hddssd-harness
  22. If you are not using Armbian kernel why do you ask here? Anyway try Armbian kernel and check if the necessary sys nodes are there.
  23. Hello, So, I sold by Helios64. This is the end of the game for me, somehow unfortunately. I loved the design of the device, its robust case and so good build. What a great NAS device, really! I will anyway keep an eye on this forum. Cheers
  24. Hi! I am trying the vanilla 5.15 kernel which has support for helios64. The system is booting, disks, MMC and network are working. But fancontrol fails. It seems the /sys entries have changed and the udev rules are not working. I've tried to understand the wiki page in order to adapt the udev rules and fancontrol config file but I am a little bit lost. Is there updated versions of those config files? Kind regards, Xavier Miller.
  25. Hi my Helios 64 do not boot up anymore. In serial console i can see U-boot crc problem. So what can i do? port is : /dev/ttyUSB0 flowcontrol : none baudrate is : 1500000 parity is : none databits are : 8 stopbits are : 1 escape is : C-a local echo is : no noinit is : no noreset is : no hangup is : no nolock is : no send_cmd is : sz -vv receive_cmd is : rz -vv -E imap is : omap is : emap is : crcrlf,delbs, logfile is : none initstring : none exit_after is : not set exit is : no Type [C-a] [C-h] to see available commands Terminal ready T T DDR Version 1.24 20191016 In channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB 256B stride channel 0 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x1 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x40 ch 1 ddrconfig = 0x101, ddrsize = 0x40 pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 928MHZ channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 928 MHz, current 856MHz OUT Boot1: 2019-03-14, version: 1.19 CPUId = 0x0 ChipType = 0x10, 254 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 SdmmcInit=0 1 StorageInit ok = 67896 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 atags_set_bootdev: ret:(0) GPT 0x3380ec0 signature is wrong recovery gpt... GPT 0x3380ec0 signature is wrong recovery gpt fail! LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xe5674 RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.10-armbian (Jan 05 2021 - 00:07:57 +0100) SoC: Rockchip rk3399 Reset cause: POR DRAM: 3.9 GiB PMIC: RK808 SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB MMC: mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Helios64 Revision: 1.2 - 4GB non ECC Net: eth0: ethernet@fe300000 scanning bus for devices... starting USB... Bus usb@fe380000: USB EHCI 1.00 Bus dwc3: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe380000 for devices... 1 USB Device(s) found scanning bus dwc3 for devices... cannot reset port 4!? 4 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 17 ms (182.6 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 166 bytes read in 13 ms (11.7 KiB/s) 15771935 bytes read in 1514 ms (9.9 MiB/s) 28580352 bytes read in 2727 ms (10 MiB/s) 81989 bytes read in 42 ms (1.9 MiB/s) 2698 bytes read in 32 ms (82 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Moving Image from 0x2080000 to 0x2200000, end=3de0000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15771871 Bytes = 15 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... Bad Data CRC Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing...
  26.