Franky66

No sorry, switched to x86 pc and did not spend any time there.

Actually not, I did not spend any more time in the last weeks and still have to buy a serial adapter for debugging. So sorry, I can't help.

Hello, I did flashing again sd card without any changes: And for comparing I read the sd card back to file Attached please find the corresponding readback file. u-boot-meson-readback.bin.gz

Thankx for your help, I am some days on holiday and will respond as soon as possible.

So I wrote your image to the sd card. Both sd card and emmc are plugged in, but after power on the screen stays black, nothing is shown. I need this serial to usb adapter, that's useless in finding bugs. Time to buy :-(

hello, I have prepared a sd card as described and "nulled" it via dd. So I can flash you firmware on spi for testing.

Ok so is there a reason why they conflict each other. I can try you self-build firmware with only u-boot and flash to spi. I have one odroid n2 for experimenting and testing.

I am sorry, I do not have the separate reader to get the serial console information actually. I will also try to find some support in the hardkernel forum how to get things booting. Maybe something else is broken as the updating petiboot via recovery image didn't work at first time and I had to zero the internal flash areas and try again. There was some advise for this in the forum

How to find out the uboot version? I am not using SPI as it is not working at the moment. Don't know why, flashed the latest version and if sd card is inserted it crashes directly to shell if I press a button on keyboard. From package manager I get the following information: ii linux-u-boot-odroidn2-current 22.02.1 arm64 Uboot loader 2022.01 ii u-boot-tools 2021.01+dfsg-5 arm64 companion tools for Das U-Boot bootloader

Aditionally my actual configuration - upgraded armbian debian 10 build with omv5 installation to armbian debian 11 build with omv6 via omv-upgrade-install successfull - actual kernel running 5.10.102-meson64 #22.02.1 SMP PREEMPT - output from /boot directoy drwxr-xr-x 10 root root 4096 May 19 11:27 . drwxr-xr-x 21 root root 4096 May 17 21:31 .. -rw-r--r-- 1 root root 0 May 13 08:54 .next lrwxrwxrwx 1 root root 24 May 13 08:54 Image -> vmlinuz-5.10.102-meson64 -rw-r--r-- 1 root root 5292029 Feb 27 10:09 System.map-5.10.102-meson64 -rw-r--r-- 1 root root 180 May 19 11:27 armbianEnv.txt -rw-r--r-- 1 root root 1536 Mar 21 2020 armbian_first_run.txt.template -rw-r--r-- 1 root root 4882 Mar 21 2020 boot-desktop.png -rw-r--r-- 1 root root 38518 Mar 21 2020 boot.bmp -rw-r--r-- 1 root root 7823 May 13 08:29 boot.cmd -rw-r--r-- 1 root root 5579 May 13 08:29 boot.ini -rw-r--r-- 1 root root 7895 May 13 08:29 boot.scr -rw-r--r-- 1 root root 229458 Feb 27 10:09 config-5.10.102-meson64 -rwxr-xr-x 1 root root 120 Jan 1 1970 display.bin lrwxrwxrwx 1 root root 20 May 13 08:54 dtb -> dtb-5.10.102-meson64 drwxr-xr-x 2 root root 4096 Aug 23 2020 dtb-4.9.219-meson64 drwxr-xr-x 2 root root 4096 Sep 21 2020 dtb-4.9.232-meson64 drwxr-xr-x 2 root root 4096 Oct 27 2020 dtb-4.9.236-meson64 drwxr-xr-x 2 root root 4096 Feb 7 2021 dtb-4.9.247-meson64 drwxr-xr-x 2 root root 4096 Mar 10 2021 dtb-4.9.250-meson64 drwxr-xr-x 2 root root 4096 May 12 2021 dtb-4.9.260-meson64 drwxr-xr-x 2 root root 4096 May 13 08:53 dtb-4.9.277-meson64 drwxr-xr-x 4 root root 4096 May 13 08:53 dtb-5.10.102-meson64 lrwxrwxrwx 1 root root 19 Aug 31 2021 dtb.old -> dtb-4.9.275-meson64 -rwxr-xr-x 1 root root 256 Jan 1 1970 edid.bin -rw-r--r-- 1 root root 16773114 May 17 21:53 initrd.img-5.10.102-meson64 -rw-r--r-- 1 root root 26329664 May 13 08:54 uImage lrwxrwxrwx 1 root root 24 May 17 21:53 uInitrd -> uInitrd-5.10.102-meson64 -rw-r--r-- 1 root root 16773178 May 17 21:53 uInitrd-5.10.102-meson64 -rw-r--r-- 1 root root 26329600 Feb 27 10:09 vmlinuz-5.10.102-meson64 lrwxrwxrwx 1 root root 23 May 13 08:30 zImage -> vmlinuz-4.9.277-meson64

Hi there, yesterday I tried to use nand install skript tool to move the content from my sd card on odroid n2 to emmc card for booting and using emmc card only. The process itself worked and the content of the sd cards was moved, but after unplugging sd card and plugging emmc card the boot process is not starting and nothing is shown on the hdmi monitor. I compared the /boot filesystems and both are identically. I checked the "armbianEnv.txt" file and it is ok for the new uuid of the emmc card. Everything seems to be identically but why is it not booting. Does someone have a hint what to check additionally what is maybe missing at beginning of the boot process. The LED is not blinking on boot process so something in the first steps of booting and loading does not work. Thank you in advance

I can confirm that only power cycle works actually. But this problem was posted on my other thread. Please read my problem in this thread. I will post this in omv forum additionally.

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 manager seems to be deinstalled and also there is a new empty config file under /etc/networking (which is not used from network manager) - so I have to repair this manually via direct access to the shell and after reboot network is ok I didn't see this behavior on my odroids n2 which I installed some month before. Should I also post this on openmediavault forum because this shouldn't happen. Seems that there is a mismatch in the salt config when using this armbian version and using installation skript via softy.

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

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 are using on my test N2 a micro sd card and on my prod n2 a emmc card. The C4 is also using a emmc card. Can someone help to fix this or are there other persons using these odroids with same problems? Here are the actually installed packages without problems: ii linux-dtb-legacy-meson64 20.08.6 arm64 Linux DTB, version 4.9.236-meson64 ii linux-image-legacy-meson64 20.08.6 arm64 Linux kernel, version 4.9.236-meson64 And here is the output from installing the newer kernel which is actually available Reading package lists... Building dependency tree... Reading state information... Suggested packages: linux-firmware-image-legacy-meson64 The following packages will be upgraded: linux-dtb-legacy-meson64 linux-image-legacy-meson64 apt-listchanges: Reading changelogs... 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/21.9 MB of archives. After this operation, 2632 kB of additional disk space will be used. (Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 62535 files and directories currently installed.) Preparing to unpack .../linux-dtb-legacy-meson64_20.08.13_arm64.deb ... Unpacking linux-dtb-legacy-meson64 (20.08.13) over (20.08.10) ... dpkg: warning: unable to delete old directory '/boot/dtb-4.9.236-meson64': Directory not empty Preparing to unpack .../linux-image-legacy-meson64_20.08.13_arm64.deb ... update-initramfs: Deleting /boot/initrd.img-4.9.236-meson64 Removing obsolete file uInitrd-4.9.236-meson64 Unpacking linux-image-legacy-meson64 (20.08.13) over (20.08.10) ... Setting up linux-dtb-legacy-meson64 (20.08.13) ... Setting up linux-image-legacy-meson64 (20.08.13) ... update-initramfs: Generating /boot/initrd.img-4.9.238-meson64 update-initramfs: Converting to u-boot format Fertig ...

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.

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?

For now I have downgraded the script temporary to the old version and cron jobs are working again.

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/openmediavault/cron.d/userdefined-ee6e5e4d-afef-449f-88fb-b6b4d0e4f1a5: 20: /etc/profile.d/armbian-check-first-login.sh: Syntax error: "(" unexpected So there seems to be a syntax problem in the new version of the "armbian-check-first-login.sh" script. I am not sure why it is used on starting the user defined cron jobs from omv5, but for now there are not working anymore. Maybe some one has the same issue?

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

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)"

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): RULE_INSERT failed (Invalid argument): rule in chain FORWARD (exit status 4) Searching google doesn't find a possible solution. Anyone here that have a hint for this?

@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.

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. Maybe this is useful for other people or other had another solution for this. Regards

@Igor My big thank to you for your work. I will check the images and will give feedback for errors etc.