Franky66

Members
  • Content Count

    27
  • Joined

  • Last visited

About Franky66

  • Rank
    Member

Recent Profile Visitors

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

  1. I flashed the image Armbian_20.08.1_Odroidc4_buster_current_5.8.5.img on my new odroid c4 without installing the latest updates (see my other post with no boot anymore after kernel update). After this I started via softy installation of omv5. During installation I wondered why my ssh connection was gone without any output. During installation there is a reboot of the os and the networking is not coming up anymore. I tried to find out and found: - armbian uses network manager for networking and the default config file is for dhcp - after omv5 installation network ma
  2. Some strange thing is that on the C4 the mac adress changes after installing updates after initial deploying image to emmc card: MAC after deploying image - U-Boot.armv8, 00:50:43:84:FB:2F MAC after updates without kernel - 02:0B:18:CC:AF:CB
  3. I am using two Odroid N2 and a new Odroid C4. The N2 installation with OMV5 is using Kernel 4.9.236 actually and the C4 is using the kernel 5.8 used in the latest download image for debian buster. When I try to install newer kernels after the following linux kernel packages the installation gets broken and the odroids are not booting anymore. There is also no output on hdmi to see what problem could be exist. On Odroid N2 I hear the USB drives starting, stopping, starting and then nothing happens. All other updates are installing without problems in rebooting. The N2 ar
  4. Yes that is right, with the update package "linux-buster-root-legacy-xxx 20.08.3 on my odroid n2 it is fixed and new versions of the files are installed. After rebooting with installing the other updates everything is fine now.
  5. I saw on github that the problem should be fixed but I didn't see any update in the last 14 days which installed new version of the necessary files. Will there be an update available which fixes this or do I have to manually change files and if yes what files where to change?
  6. For now I have downgraded the script temporary to the old version and cron jobs are working again.
  7. Some days ago I installed the latest armbian updates to my armbian buster installation / openmediavault 5 on my odroid n2. After the installation of the following updates the cron jobs, which were setup on omv5 gui (not in crontab os) are not working anymore and are not started because of error: Here the update packages: armbian-config 20.08 armbian-firmware 20.08 linux-buster-root-legacy-odroidn2 20.08 linux-dtb-legacy-meson64 20.08 linux-image-legacy-meson64 20.08 linux-u-boot-odroidn2-legacy 20.08 Here the error message: /var/lib/openmediavaul
  8. Yes I found one after a hint from another person. This is what I did in changing default iptables usage: After changing iptables usage it worked: Switching to the legacy version: # update-alternatives --set iptables /usr/sbin/iptables-legacy # update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy # update-alternatives --set arptables /usr/sbin/arptables-legacy # update-alternatives --set ebtables /usr/sbin/ebtables-legacy
  9. The corresponding entry in syslog in long: dockerd[3322]: time="2020-05-04T19:34:03.278587409+02:00" level=error msg="Handler for POST /v1.40/networks/create returned error: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-c723c76c6721 -j DOCKER: iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argument): rule in chain FORWARD\n (exit status 4)"
  10. Hi there, I have just do a fresh install of armbian (Armbian_20.02.5_Odroidn2_buster_legacy_4.9.216) on odroid n2 and installed omv 5 via armbian softy tool. Docker was installed via omv gui - omv extras - docker / portainer. When I now try to setup a separate network in docker / bridged mode I get the following error: docker network create --driver=bridge --subnet=192.168.151.0/24 --gateway=192.168.151.1 home Error response from daemon: Failed to program FILTER chain: iptables failed: iptables --wait -I FORWARD -o br-7a5194cdef64 -j DOCKER: iptables v1.8.2 (nf_tables): RU
  11. @maxlinux2000 the actual setup is working fine for me. Igor give the right hint for tuning the log destination. I will check this. If I understand right, armbian is configured for delay write the log files to disk (specially sd cards) so that the sd cards are longer usable during less writing. Removing the partitions is not useful as a lot of linux services need this standard locations :-) @Igor Thankx for your hint. I was not sure were armbian is configured for the ram log disk. So will have a look and tune.
  12. I went into a problem after setting up mariadb / nextcloud installation nativ on my armbian installation odroid n2. per default the logfiles for mariadb (bin files) are logged to /var/log which is only 50 mb because of in memory usage (zram). So after some usage the whole installation stucked because of "out of disk usage" in /var/log. So I stopped nginx, php and mariadb and created a new logfile location in /var/log.mariadb and changed the necessary entries in /etc/mysql/my.conf and started the necessary services again. For now the usage is propper again in /var/log. M
  13. @Igor My big thank to you for your work. I will check the images and will give feedback for errors etc.
  14. Hello Igor, sorry for asking but did you find some time for fixing the buster image for the odroid n2?
  15. Ok no problem I will just wait until you can fix it.