technik007_cz

For that dts file must be changelog somewhere explaining changes. I decompiled both dts files but it is hard for me to decode changes in short time.

logs with verbosity=7 BOOTLOG-NOK.TXT BOOTLOG-OK.TXT

After inspecting the differences between those 2 bootlogs, it looks like it hangs up for some reason when trying to check the root filesystem for errors.

Bootlog with non-working and working dtb file. bootlog-OK.txt bootlog-NOK.txt

root@bpim2u:~# sudo dd if=/dev/mmcblk0 count=32k | strings | grep "U-Boot SPL" U-Boot SPL 2024.01_armbian-2024.01-S866c-P7738-Hadc5-Vc46c-B2eb2-R448a (Feb 20 2026 - 04:58:43 +0000)

I am getting closer to resolving this issue ... I took the latest image Armbian_community_26.2.0-trunk.732_Bananapim2ultra_noble_current_6.18.22_xfce_desktop.img.xz, flashed it, and it hung on Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems Removed microsd and replaced file sun8i-r40-bananapi-m2-ultra.dtb in /boot-dtb folder with file supplied with linux-image-6.1.24-sunxi kernel. And do you know what ? It successfully booted up after this change!

When I replaced 6.12.58-current-sunxi with armbian-utility to 6.6.16-current-sunxi It did not fully boot up again. Hopefully, replacing the whole content of /boot with the 6.1.24-sunxi kernel from the original image worked and brought m2u back to life. Also, the related modules folder was transferred. So it looks like it is a kernel problem.

Just doing upgrades 2nd time on the same image, and it upgraded u-boot and linux-image regardless of armbian-utility put them on hold... I will try to get the kernel from the original image, but if it fails due to the u-boot version difference, I will need to flash it 3rd time, and then I will prevent it from upgrades on these essential packages, like Back In Time.

Just found out after upgrading everything on Armbian_23.05.0-trunk_Bananapim2ultra_jammy_current_6.1.24.img.xz, there is no way back once it stops booting. Tried the lowest legacy kernel and also sunxi u-boot and legacy u-boot, everything in chroot, and no success. So I need to start again, reflash the image and prevent the kernel and u-boot upgrades via armbian-config. Is it everything after kernel 6.1.24 when it breaks? Actually, it should be after 6.1.37, which is part of another functional system image.

I is not looking like a powering issue, see the first pic.

I can confirm the situation with the latest Armbian Noble system image for M2U, which is Armbian_community_26.2.0-trunk.703_Bananapim2ultra_noble_current_6.18.21_xfce_desktop.img.xz. lead to the same result and it hangs at messages: Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems For those which looking for a functional system, I found 2 : Armbian_23.05.0-trunk_Bananapim2ultra_jammy_current_6.1.24.img.xz Armbian_23.08.0-trunk_Bananapim2ultra_bookworm_current_6.1.37_xfce_desktop.img.xz However, if you upgrade the system on this image to the latest, it will result in an unbootable system again. So you need to prevent kernel and U-Boot from upgrades.

I just tested the latest Armbian distros, Armbian 26.2.0-trunk.493 XFCE and Armbian 26.2.0-trunk.493 Minimal / IOT, and none worked. Then I tried Radxa system images, rock-4se_bookworm_kde_r4.output_512.img.xz did not work. So I got confused because my Rock 4SE v 1.53 SBC worked a long time ago. Found backup of old boot image, which I used with the NVMe drive, because it could not boot on its own. And do you know what? Finally, I saw a picture on the screen with boot log information, which made me happy because it proved my SBC had not died. Then I started looking at some old system images for this board and found one which is booting, it is rock-4se_debian_bullseye_kde_b38.img.

Hi, I redownloaded the key and replaced it, and it works!

Same issue there apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://deb.debian.org/debian trixie-backports InRelease Get:5 https://mirror.vinehost.net/armbian/apt trixie InRelease [39.4 kB] Err:5 https://mirror.vinehost.net/armbian/apt trixie InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound: No binding signature at time 2026-02-26T23:23:28Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature. Fetched 39.4 kB in 4s (10.2 kB/s) All packages are up to date. Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://mirror.vinehost.net/armbian/apt trixie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound: No binding signature at time 2026-02-26T23:23:28Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature. Warning: Failed to fetch https://apt.armbian.com/dists/trixie/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DF00FAF1C577104B50BF1D0093D6889F9F0E78D5 is not bound: No binding signature at time 2026-02-26T23:23:28Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Missing key 8CFA83D13EB2181EEF5843E41EB30FAF236099FE, which is needed to verify signature. Warning: Some index files failed to download. They have been ignored, or old ones used instead.

I just run into this problem again but on different SBC. With new apt apgrade a new version of kernel came, initramfs complainend about "Invalid architecture" and failed to finish. I tried to fix it differently and it also worked. Removed armbian-bsp-cli-rock-4se-current, with this new attempt to do initramfs started and was completed without error. Then I installed armbian-bsp-cli-rock-4se-current again. Just bear in mind you need to know which armbian-bsp-cli you had previously installed because it could be also -edge , -vendor , etc.