I fixed the shitty dd stuff i did previously. I got it to boot now. It seems that the partitions need to be included in the image for it to work. From inside the armbian image: mmcblk0 179:0 0 28.9G 0 disk ├─mmcblk0p1 179:1 0 4M 0 part ├─mmcblk0p2 179:2 0 12M 0 part └─mmcblk0p3 179:3 0 28.8G 0 part /var/log.hdd I will build my own img and see if there is anything I can do about the non working usb. I think it might likely be related to dts

LC_ALL=C apt update Hit:1 http://security.debian.org bookworm-security InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 https://download.docker.com/linux/debian bookworm InRelease Hit:5 http://deb.debian.org/debian bookworm-backports InRelease Hit:6 https://github.armbian.com/configng stable InRelease Hit:7 https://dtcooper.github.io/raspotify raspotify InRelease Hit:8 http://fi.mirror.armbian.de/beta bookworm InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. root@orangepi3-lts:~# apt list --upgradable Listing... Gotowe armbian-bsp-cli-orangepi3-lts-current/bookworm 25.11.0-trunk.439 arm64 [upgradable from: 25.8.0-trunk.49] N: There is 1 additional version. Please use the '-a' switch to see it

I see now with some examination this: [ 1.995057]3 614e0000-0000-4b53-8000-1d2800995194] No filesystem could moun ext4 [ 1.995269] [ 1.9g: VFS: Unable to mount root fs 002577] CPU2: stopping The reason for the missing characters is likely the shitty CH340 I have connected as the serial monitor. Should still be able to see the issue.

So I am not a person to give up on this I basically took the partition scheme of a working ubuntu img and inserted the armbian partition and got further along. I changed it to below and got further along! Check the log for more information. Hint it threw some panic stuff, I wasn't expecting much but got further along. Hope someone can see what is wrong and help me troubleshoot. sudo fdisk -l /dev/sdd Disk /dev/sdd: 28.85 GiB, 30979129344 bytes, 60506112 sectors Disk model: Storage Device Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 863CE3B9-B148-45D1-B850-79AC22F0EB72 Device Start End Sectors Size Type /dev/sdd1 8192 16383 8192 4M Linux filesystem /dev/sdd2 16384 40959 24576 12M Linux filesystem /dev/sdd3 65536 60504063 60438528 28.8G Linux filesystem screenlog.log

If you have used RadxaOS before there might be an older U-Boot variant in SPI-flash and at least on ROCK3A SPI take preference over SD-cards, so the Armbian U-Boot from SD-card is not use. AFAIR Radxa OS ROCK5 U-Boot does not have the 1 sec autoboot timeout and also uses extlinux script and not bootcmd. But I might mix-up versions and platforms. So rewrite SPI-flash from Armbian is option to fix it.