Vin

  • Posts

    38
  • Joined

  • Last visited

Recent Profile Visitors

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

Vin's Achievements

  1. Today is the day. After 7 days, probably a corrupted OS again.
  2. Well, fixing the governor to 1,2 ghz did also do the trick for me, whereas at 1,6 ghz it still crashed regularly.
  3. I can understand that, also ist doesnt make a good impression, yet i assume there must be way more people out there with an unstable system wondering what is happening and being disappointed. I would have appreciated any information, even though its just that users reported about stability problems and you are onto it, trying to imporove this and that section of the code. Also i wonder what you are working on to stabilize the system, if you dont know the cause? I already tried the voltage and scheduler workaround without success, and those are the only two specific issues that were pointed out so far. I m running on both, since i have to reflash the system too many times, its currently on the SD, but i also copied it to nand without any difference in stability I already shared some crash logs on other topics, wouldnt be a dedicated topic with just crash logs easier for you guys?
  4. Mine is still crashing like a clockwork every 24 hours and leaves me generally with a corrupted OS and data. I know you are a small team and you had to takle many obstacles to release the Helios64, believe me im a fan of your work, product and armbian in general, i m aware of the effort every involved person puts into this project. But i would appreciate a bit more news about the current status of developement. As far as i can see there is no status or developement overview on the current issues, not on your blog nor on twitter. The only information we get are in various topics across the forum on armbian. Is there a possibility to let us know more about the ongoing research and inform us about the progress and persued assumed solutions? Also I wonder if those issues are genreal rk3399 gonvernor etc. problems, or if it applies specifically for the Helios64? Thank you in advance for your reply.
  5. Im also still having constant crashes. But recently it already happened 3 times where it crashed for no obvious reason (was running for 1-2 days, nothing has been changed) but then doesnt boot up anymore. So i already reinstalled it 3 times, before it happened again right now. Running latest armbian, with OMV, LUKS, Docker
  6. As i said, by software it shouldnt be possible since its fresh installs, i even used older images. The sticker can also be ruled out, since its on for months and before it was running, also i wasnt pushing anything. I really dont understand what or why, but yesterday i let it run on the battery until it was drained, reapplied the cable and restarted some more, and at some point it was even starting from my old nand image again didnt do a restart so far since im worried it wont come up anymore.
  7. seeing a similar issue Helios was already working for some time, aside from regular crashes, but doesnt boot up anymore. It does boot but crashes within a few seconds. Any idea? to rule out unrelated software issues, i flashed the current Armbian_21.02.3_Helios64_buster_current_5.10.21 image on a sd card. Helios doesnt boot form the existing OS on the nand, nor from the fresh one on the sd.
  8. configurating after the installation over serial connection is no problem. the problem is that apparently the installation "breaks" something in the ip configuration. despite set up a static ip in OMV multiple times, after every boot its back to dhcp and resolv.conf is empty. also the startup of the kernel hangs for like 5 minutes until the OS is available http://ix.io/2PWi
  9. Hello together, i experienced network problems with Helios64 and latest Debian Buster Image. I cannot setup a static ip address after installation of OMV5, moreover it crashes on install. I double checked it on a fresh image without any changes and an immediate installation of OMV over softy. The result is the same. After the crash OMV is in fact available, but the network configuration is broken and a static setup doesnt work over the OMV UI, nor armbian-config, also the boot takes about 2-5 minutes due to whatever reason. armbianmonitor http://ix.io/2PPJ
  10. Hello tparys, thank you for you reply service network status Unit network.service could not be found. /etc/network/interfaces.d its empty armbianmonitor -u http://ix.io/2POV tried nmcli con mod "Wired connection 1" ipv4.addresses "192.168.2.64/24" ipv4.gateway "192.168.2.1" ipv4.dns "127.0.0.1,192.168.2.1" ipv4.dns-search "lan" ipv4.method "manual" didnt do the trick EDIT2: I just tried a fresh install and apparently the OMV installation breaks something regarding networking. I setup a static ip via armbian-config and i worked, but when i installed OMV over softy, the CPU run on 100% on one core and the system crashed. After the automated reboot its back to its DHCP IP 192.168.2.101 instead of 192.168.2.64
  11. Hello everybody, im running a Helios64 with most current Debian Buster5.10.16 image. I was freshly setting up the device and i am now failing to assign a static ip address to it. I installed Pi-hole, Home assistant and openmediavault over softy. During the pihole installation i can setup a static ip address, but after a reboot i still get the old DHCP addess. I assigned it over the OMV interface but its not applied after a reboot, the armbian-config tool doesnt open when i want to change to static and i also tried netplan. DHCP is also turned off on my router and switch. i rebooted all of the devices multiple times. OMV netplan network: ethernets: eth0: match: macaddress: 64:62:66:d0:0a:e0 addresses: - 192.168.2.64/24 gateway4: 192.168.2.1 dhcp4: false dhcp6: false link-local: [] nameservers: addresses: - 127.0.0.1 /etc/network/interfaces # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. # interfaces(5) file used by ifup(8) and ifdown(8) # Better use netplan.io or systemd-networkd to configure additional interface stanzas. # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d
  12. Both, the affected HDDs and Ports are random Plugging them in another Port solves the problem, but they can get affected again at a later point, plugging them back to the original ports solves the problem.
  13. SATA Ports are firm, also connection to the HDDs are proper. Just restarted and did a fresh install of the new februar update, two out of three HDDs are not recognized anymore, even though they were recognized before and have not been unplugged.
  14. Hello everybody, im experiencing a similar problem. Sometimes my WD RED 12 TB HDD is not recognized in that slot its in, when i change it to any other it works again. Nevertheless it seems this problem doesnt only apply to one specific slot, but is changing from time to time. EDIT: The LED of that slot doesnt turn on, yet the drive starts and runs Do anybody experience the same problem, or know any help? Thank you in advance. Best Regards.