@technik007_cz I see I also posted here, I initially thought the problem was in kernel or initrd or armbian scripts, but it turned out HW related (power). Is all sorted now and all understood and also situation for my ROCK3A is very different now. And also ROCK3A is Rockchip, BPiM2ultra is Allwinner. What is common it seems is that the storage device where the rootfs is on is unavailable to the kernel+initrd. If you have a running Armbian system and you do apt update && apt full-upgrade, you get new kernel and new u-boot if those packages are updated. BUT, the U-Boot blob is not written to storage device automatically, so this seems like a problem as I have had and seen various times before: older U-Boot and newer kernel. As you also it have a non-working with a pre-installed/pre-generated image, the problem is also there its seems. However, it needs more details. You need U-Boot log and kernel log posting here. Attach a serial console cable and set kernel loglevel to 7 Just for (my) reference, the board is this: https://wiki.banana-pi.org/Getting_Started_with_M2_Ultra_%26_Berry

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.

Thank you. Could you recommend a system where all the hardware can work together?

We neither deal with nor do we support 3rd party images/OS.

Thank you for your reply, Werner. As I mentioned, all firmware versions from the very old ones to the latest are already installed. Since then, after some trial and error, I have confirmed that it works by building the RELEASE as resolute. The command I used for the build is as follows: ./compile.sh BOARD='nanopi-r5c' BRANCH=edge RELEASE=resolute DISABLE_IPV6=no EXTRAWIFI=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=no BUILD_MINIMAL=no PREFER_DOCKER=no CONSOLE_AUTOLOGIN=no && pigz -9 -v output/images/*r5c*.img