16 16

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. Sigh. Except that doesn't solve the problem. Now it's just cron filling up the log. New solution, using the sleep option. Modified helio64-ups.service: [Unit] Description=Helios64 UPS Action [Install] WantedBy=multi-user.target [Service] #Type=oneshot #ExecStart=/usr/bin/helios64-ups.sh Type=simple ExecStart=/usr/local/sbin/powermon.sh Modified powermon.sh: #!/bin/bash #7.0V 916 Recommended threshold to force shutdown system TH=916 # Values can be info, warning, emerg warnlevel="emerg" while [ : ] do main_power=$(cat '/sys/class/power_supply/gpi
  3. While something that sleeps for 20 seconds might be better, I've set up the following script in cron to go off every minute. <removed> My crontab looks like: <removed> I've tested this and it seems to work. The pipe to systemd-cat lets this log to the system journal at a set warn level. -- Edit: Removed extra stuff here to clean things up a little. This didn't work the way I wanted.
  4. Thanks for your help - I played around with that for a while, but ended up just reinstalling. It was pretty annoying actually, but fast. How does something like this go wrong in a system that is just sitting there?? Anyhow back on deck.
  5. Can maybe disable the service and put the script it is running, /usr/bin/helios64-ups.sh to root cron for every minute. You could make it run every 20 seconds by adding a while loop that goes 3 turns and sleeps 20 seconds in each turn. However, I don't see where this script checks to see if mains power is active. What I see is a script that will continually shutdown the device if the battery voltage is low even when the mains returns. Is that function provided by the service timer, as in the timer stops when there is mains? If so absolutely do NOT cron helios64-ups.sh as it is
  6. It looks like you have been booting from the eMMC, right? I think you're going to need to boot off an SD card and try to fix the GPT. This may help you with doing that.
  7. Hi All, My helios64 died the other day - well failing to boot. It had been solid for quite some time, then I might have made the mistake of updating it.... This is from putty on booting: 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 Channe
  8. @SIGSEGV It is disabled by default, but since I had some time the last few days I've been digging into things and came across this. There's a corresponding service, but all it does is check to see the state of the battery and then exit. If something else is monitoring the battery, I don't know what it is. The service could be rewritten as a script that has an loop that checks the state of the battery every 20 seconds and then sleeps.
  9. @wurmfood On my system the helios64-ups.timer is disabled by default. Is this a timer that has to be manually enabled ?? I thought that the Helios would check if it had the battery and activate this automagically. It might be better to have a daemon in the background that checked the battery value every 20 seconds and only printed out output when there was a change.
  10. While I like having the helios-ups.timer in case of power failure, I don't like that my logs get three lines written to them every 20 seconds. Apr 09 07:43:26 helios64 systemd[1]: Starting Helios64 UPS Action... Apr 09 07:43:26 helios64 systemd[1]: helios64-ups.service: Succeeded. Apr 09 07:43:26 helios64 systemd[1]: Finished Helios64 UPS Action. Does anyone know if there is a way to keep the timer on but not fill the logs this way? Everything I've found about silencing systemd messages is about the output of the command, not the systemd activity itself.
  11. Well, for anyone else interested in trying this, here's the basic order I did: stop armbian-ramlog disable armbian-ramlog create a zfs dataset and mount it at /var/log cp -ar everything from /var/log.hdd to the new /var/log modify /etc/logrotate to disable compression (since the dataset is already using compression) modify /etc/default/armbian-ramlog to disable it there as well modify /etc/default/armbian-zram-config to adjust for new numbers (I have ZRAM_PERCENTAGE and MEM_LIMIT_PERCENTAGE at 15). reboot
  12. Actually that is what I would do at first try.
  13. Is there an accepted procedure for moving from using ramlog to logging to disk? I've looked but everything I can find is about setting up ramlog. I assume it's more complicated than just creating a partition (or ZFS dataset) and mounting it /var/log, disabling ramlog, and rebooting.
  14. You can change the settings in /etc/default/armbian-zram-config Maybe the default settings are effectively overkill with 4GB of RAM.
  15. Most of them do not run of a sdcard which limited life span so they can rely on a normal swap partition.
  16. Thank you. I wanted to make sure I understood it correctly since I hadn't encountered this on other Linux systems.
  17. Yes. Also yes. Armbian by default uses 50% if available memory for zram. If you have a fast harddrive like SSD or NVMe attached it of course makes sense to put a common swap there.
  18. I'm trying to understand the role of zram and having some difficulties with it. I've looked in several places and my understanding is this: - It's a block device in RAM that uses compression - It functions similar to swap I notice that mine is set to about 2 Gb: wurmfood@helios64:~$ cat /proc/swaps Filename Type Size Used Priority /dev/zram0 partition 1945084 0 5 My questions: 1. Does that mean 2 Gb of the device RAM is used for the z
  19. Just for anyone reading this, this might be related. Someone suggested prioritizing gzip in order to escape the slowness of LZ4 on ARM platforms. Here is the solution, which was also merged in Armbian itself:
  20. Hi, Yes it's not a problem at all. Both connectors are actually connected to the same power rails, so there is no difference between the 2. The reason we put 2 connectors was to be sure we don't exceed max power rating of the Molex pin, but honestly it was a bit overkill. So technically you could also not bother and just use one of the 2x connectors instead of both.
  21. Hello everyone, I am thinking about moving the Helios4 into a Inter-Tech SC-4100 case. The backplane in that case has only one Molex powerconnector. So is it possible to combine both power connectors on the board (J14 + J19) into one ? https://wiki.kobol.io/helios4/img/hardware/board_legend.jpg Thanks Br, Joe
  22. @tionebrr Source : https://www.rockchip.fr/RK3399 datasheet V1.8.pdf 1.2.1 Microprocessor  Dual-core ARM Cortex-A72 MPCore processor and Quad-core ARM Cortex-A53MPCore processor, both are high-performance, low-power and cached application processor  Two CPU clusters.Big cluster with dual-coreCortex-A72 is optimized for high-performance and little cluster with quad-core Cortex-A53 is optimized for low power. <... >  PD_A72_B0: 1st Cortex-A72 + Neon + FPU + L1 I/D cache of big cluster  PD_A72_B1: 2nd Cortex-A72+ Neon + FPU + L1 I/D cache of big cluster
  23. Not sure. I changed both policies to 1.6GHz and I get the same min/max as you: Changed back to 1GHz and both policy are back the same again. Okay, and I just noticed that not all core have the same frequencies available: So maybe the policies are made to fit the available frequencies? And yep, setting the min max to 1.4GHz makes both policies equal. Not sure why some cores doesn't accept 1.6 and 1.8GHz tho. Isn't this supposed to be the same clock for every core?
  24. I'm a bit confused to not have the same values on my side for all policies ... Whereas : (> i set min = max = 1.6Ghz through armbian-config) What are these two different policies in /cpufreq/ ? (policy0 + policy4 in /cpufreq/ on my side) Is it like "policy0" is used by "performance" governor mode and policy4 by "powersave" ? (in which case it would make sense for me to have different values)
  25. I had instability too, I just dialed back on the performances and it hasn't crashed in a while. However, throttling is disabled. I fixed the cpufreq at about 1GHz. Hadn't had the time to do more testing.
  26.