17 17

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. Any news on this side? I'm really looking forward to be able to suspend and use wol!
  3. Guys, try to run your helios in whatever mode but always under 1.4GHz. I have mine set to performance and throttling from 400MHz to 1.4GHz. Uptime is 9 days now. Only two of the CPU cores can run above 1.4GHz (see these posts for reference) and that might be one of the cause of the crashes.
  4. My comment might be late to the party - if there was a possibility to add an optional display and a few user-configurable buttons to the Front Panel, that would be great. I know it would mess a bit with the airflow, but it could be used for system monitoring and few other specific use cases.
  5. Mine is running absolutely stable. Only ever have to reboot due to updates. I am running OMV - I have 5 x WDC WD40EFRX-68WT0N0 drives with Raid-6 and then LVM via the OMV LVM plugin - I'm running NFS, Samba, cloudflare tunnel daemon, and Docker (in docker there's portainer, duplicacy, traefik and authelia) If it helps I'm only using the 1GB NIC and I do have the battery for power supply stability. Oh and I'm on 5.10.21-rockchip64 #21.02.3 SMP PREEMPT
  6. Just wanted to add my experience as maybe someone can get something semi-useful out of it. I started out with 3 - 4TB drives with 2 of them in Raid 1 and the 3rd on it's own. I installed OMV and CUPS on a Micro SD card. Even from the very beginning, I always had trouble restarting the system. Sometimes it would boot after 3 tries, sometimes it would take 20 tries. I watched and it was never the same issue twice that caused the boot failure. I removed drives, plugged in different combo's, several fixes on the forums, anything I could think of and nothing really seemed to make
  7. I can confirm, I'm running with a 400MHz to 1.4GHz range; up since 9 days.
  8. So on my side, after my latest reinstallation (due to corrupted OS) : - with default installation / configuration out of the box, i had one freeze every 24h - by switching to "powersave", or to "performance" mode, and with min CPU frequency = max CPU frequency = either 1.8Ghz either 1.6Ghz : still the same (one freeze per day) - by switching to "performance" mode, with min CPU frequency = max CPU frequency = 1.4Ghz, it seems now more stable (uptime = 5 days for now) So my guts feeling is really that these issues : - are mainly related to the cpufreq mechanizm
  9. My system is still unstable and I have no idea what to do. I've given every suggestion I've seen on the internet a try and I think the only thing I can do is move on.
  10. HI, My poor little Kobol has to work very hard for a living: Plex NTP (GPSD) server SMB share Webmin Zabbix agent Zerotier client/bridge Docker Storj node Raid 5 across 5 disks And is as good as gold! Had a few niggles to start with ie first week, since then its only rebooted as the OS requests otherwise excellent! Running on a 64Gb SD Card CPU full speed Very pleased! Rup
  11. My Helios is stable, running LUKS, MergerFS, SnapRAID, OMV and 9 Docker containers from SD Card and with 3 HDDs. Although in order to get a stable system I had to lock CPU frequency at 1.2GHz, otherwise CPU intensive tasks (like SnapRAID's scrub) would cause my Helios to reboot. ================================================================================ = System information ================================================================================ Linux helios64 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 GNU/Linux ============
  12. Thanks for the updated firmware. Unfortunately, I'm seeing the same as Wofferl: At first the programming didn't seem to work (I used balenaEtcher without unpacking the file, it seemed to understand that it was compressed though so went ahead with it), there was no reboot either. Here's the output: Then I tried flashing it again, unpacked it first this time around and the flashing worked as described:
  13. @aprayoga I have updated to the new firmware, but the problem is still there. Shortly after starting a zfs scrub I get the HSM violations. [ 544.719820] ata3.00: exception Emask 0x2 SAct 0x30000030 SErr 0x400 action 0x6 [ 544.719830] ata3.00: irq_stat 0x08000000 [ 544.719836] ata3: SError: { Proto } [ 544.719845] ata3.00: failed command: READ FPDMA QUEUED [ 544.719856] ata3.00: cmd 60/80:20:d0:ec:63/00:00:0d:00:00/40 tag 4 ncq dma 65536 in res 40/00:e0:d0:eb:63/00:00:0d:00:00/40 Emask 0x2 (HSM violation) [ 544.719860] ata3.00: status: { DRDY }
  14. Thanks @aprayoga. What's new or has changed in the latest SATA firmware image?
  15. Hi all, you could download the SATA firmware update at https://cdn-kobol-io.s3-ap-southeast-1.amazonaws.com/Helios64/SATA_FW/Helios64_SATA_FW_update_00021_200624.img.xz Instruction: 1. Download the sd card image 2. Flash the image into a microSD card 3. Insert microSD card into Helios64 and power on. Helios64 should automatically boot from microSD. If Helios64 still boot from eMMC, disable the eMMC 4. Wait for a while, the system will do a reboot and then power off if firmware flashing succeed. If failed, both System Status and System Fault LEDs will bl
  16. @wurmfood The script looks goods. I like the check for main power before the battery level verification, it solves the use case @clostro mentioned. @aprayoga Looking forward to the new release
  17. Today is the day. After 7 days, probably a corrupted OS again.
  18. It could be caused by power supply failure. Could you check the following thread ?
  19. Thanks for that feedback, noise is something I would want to indeed avoid and I'm not ready to upgrade to 10Gbe (not enough devices). That's reassuring that between vendors there isn't anything to watch out for in particular, since these are mainly unmanaged switches there isn't really an interface to compare between them. I did see this on reddit though for the QNAP so just monitoring if there's other potential faults. But whatever I can easy source seems in the EU seems fine for my case. Thanks all!
  20. Hi, Using 4 HDDs in my Helios 4 with Openmediavault 5.5. After a update & restart all the HDD's are gone (not shown at all in lsblk anymore). After poking around in the the systemmessages i found this in dmsg, but don't know what to do with it. ``` [ 1.746837] ahci-mvebu f10a8000.sata: supply ahci not found, using dummy regulator [ 1.746909] ahci-mvebu f10a8000.sata: supply phy not found, using dummy regulator [ 1.747062] platform f10a8000.sata:sata-port@0: supply target not found, using dummy regulator [ 1.747207] platform f10a8000.sata:sata-po
  21. I have the Netgear MS510TXPP which has POE, 4 x 1Gbe, 2 x 2.5Gbe, 2 x 2.5/5Gbe, 1 x 2.5/5/10Gbe, 1 x 10 Gbe SFP Works well but is noisy for home environment, louder than the Helios64 or rather because of a small fan with a noise that is higher pitched so not great. It did negotiate 2.5Gbe with the Helios though.
  22. I'm using Zyxel XGS1010-12. Has 8x1gbe, 2x2.5gbe, and 2x10gb sfp+ ports. Works ok, does what I need.
  23. There are few more brands offering 5 ports 2.5GbE network switch. Most likely they are all based on the same exact network chip. 2.5GbE doesn't require any special high quality component, so my guess it's the build quality is more or less the same of all those models. So end of the day you are just buying the name among all those 5x port 2.5Gbe models. You could also consider maybe a switch with more ports even though some of them might only be 1Gbps. But if you don't have the need for more ports, then any model you listed will do the job.
  24. ## Executing script at 09000000 Bad Linux ARM64 Image magic! @scottf007, it could be filesystem corruption or something wrong during update and kernel symlink was not updated to correct file. If you have access to Linux PC, you can use recovery button to enter UMS mode and do fsck or fixed the symlink. @wurmfood, it is not a problem. Rockchip loader expect the storage to be partitioned and formatted in certain way but it also can load using raw offset. Armbian does not use GPT, so the loader will print such errors.
  25. @SIGSEGV @clostro the service is triggered by udev rules. @wurmfood, I didn't realize the timer fill the the log every 20s. Initial idea was one time timer, poweroff after 10m of power loss event. Then it was improved to add polling of the battery level and poweroff when threshold reached. Your script look good, we are considering to adapt it to official release. Thank you
  26. I'm in the process of upgrading my network and with the Helios64 capable of 2.5 GbE, what are some people's switch recommendations? My needs aren't really too high so I think 5 ports should be enough until the rest of the infrastructure catches up in my home network. My short-list are: * QNAP QSW-1105-5T * TP Link TL-SG105-M2 * TRENDnet TEG-S350 Article from servethehome
  27.