axeleroy

  • Content Count

    17
  • Joined

  • Last visited

About axeleroy

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'm using the 2.5Gbps NIC exclusively with a 2.5Gbps switch for a month with no issues so far.
  2. 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 ============
  3. Hi, quick update: no reboots in the two weeks following the frequency tweak. Reboot still happened shortly after my February 11 post (but before I applied gprovost's advice).
  4. Updating to the latest Armbian seems to have improved stability, though it has only been 72 hours since the update, I might be talking too quickly. @gprovost Do I need rebooting after applying this configuration? Out of curiosity: how does it improve stability?
  5. It happened again. Should I try updating to the Armbian version that jiust came out? When should I run armbianmonitor (whenever I can or just after a reboot?) and what should I be looking for (because nothing seems odd to me, but I'm not that of an advanced user) Thanks !
  6. Oh, I didn't know about this utility. Here are the logs: http://ix.io/2Ok2
  7. Hi, I'm very pleased with my Helios 64, but since I updated to Armbian 20.11.6 (from 20.08.11 or 21, not really sure) it reboots at random times: it can run fine for over two weeks and reboot twice in 36 hours, always when idling. It's running OMV as well a multiple Docker containers: PiHole, Wireguard, Nginx, Transmission, restic-server and n8n. Is it a common issue? What fixes do you recommend? What should I look for to diagnose the issue? Thank you. Edit: forgot to mention that I'm using SnapRAID and mergerFS, as well as NFS shares.
  8. That what I thought as I read on the forums that the logs were in ramdisk, but I am confused since syslog had entries from before the reboot, as if there was an exception for this file (though I guess I'm probably wrong). How can I make the logs persistent, at least temporarily? I also had reboots when trying to backup OMV using openmediavault-backup and dd, I would like to diagnose those too (though I stop using dd in favor of borgbackup).
  9. Hello there, My board had just rebooted with no notice, so I wanted to take a look at /var/log/syslog in order to diagnose the issue, but for some reason, there are no logs between Dec 30 and the moment my board rebooted. Why are logs missing? What do I need to do in order to keep them the next time my board reboots? Also, am I looking at the right place to diagnose reboots? Thanks for you help! PS1: My board is the Helios64 and I'm running Armbian 20.11.4 Buster with OMV 5. PS2: I know there is an Helios64 Club, though I did not choose to post there as
  10. Since OMV alters so much of Debian/Armbian, I would recommend deploying the Docker container. Docker also has the benefit of using any port you want. If you want an easy to use GUI, you can install Portainer using OMV-Extras (in the left menu, then under the Docker tab of OMV-Extras).
  11. Welp, I removed the SD card and it did not boot to eMMC.
  12. Hello, I just tried to copy my Armbian install from the SD Card to the eMMC, but I'm not sure it has been successful, how can I be sure? For information, I also encrypted my HDDs using LUKS and I use MergerFS to pool their data. Boot sequence from serial console Output from df /etc/fstab
  13. I switched to eth1 to install it, then switched back to eth0 and ran arp-scan. There are lots of reference to my decommissioned Raspberry Pi on 192.168.0.110. Turns out I forgot to delete the ARP binding on my router to make sure my old Pi was given 192.168.0.110. PEBKAC… Thanks a lot anyway!
  14. Forgot to add ifconfig output, it might be useful root@helios64:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.110 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::5550:854d:6ad0:b6d7 prefixlen 64 scopeid 0x20<link> ether 64:62:66:d0:03:7c txqueuelen 1000 (Ethernet) RX packets 390 bytes 60863 (59.4 KiB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 384 bytes 35588 (34.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device inte