Just a note the download of latest release Armbian_25.8.1_Odroidxu4_noble_current_6.6.102.img works fine, so something in the build system.

Hi again Werner. Please excuse the long waiting time. It's taken me a long time to place back the device at its intended location. Here's the requested output. https://paste.armbian.com/alefaladep At the moment I've got it running on a realtek usb-ethernet dongle at full speed (confirmed throughput up to about 300Mbit). Last year when I created the thread we were using the Nanopi Neo4's onboard realtek ethernet port. No matter what we did it wouldn't run at speeds over 10Mbit. And no, the port isn't faulty. It's happening on ALL armbian devices (official and unofficial) on current distributions still to this day. Bookworm/Trixie/Noble/Jammy, with kernels 6.12, 6.6, 6.1 and 5.15 tested. On x86 debian it works right out of the box at full speed and we're talking much weaker hardware (Intel z8350). Thanks for your work. Armbian is definitely the future IMO.

Yeah fan working on :- https://github.com/radxa-build/rock-5b-plus/releases/download/rsdk-b2/rock-5b-plus_bookworm_kde_b2.output.img.xz

Nicely done 👍 I remember dealing with similar problems when I upgraded my desktop to an nvme drive. I transferred the partition to the new drive but the OS would not boot from it due to nvme modules being missing.

@Igor @belegdol I was able to get it working, but maybe this can be fixed in the build? Fix: Odroid XU4 – Armbian-unofficial_25.11.0-trunk_Noble_6.6.108 fails to boot from SATA after nand-sata-install Problem After running nand-sata-install on an Odroid XU4 (kernel 6.6.108), the system copies to SATA correctly but fails to boot afterward, dropping into the initramfs shell. Checking the loaded modules shows only: usbhid meaning no USB or SCSI drivers are available to detect /dev/sda1. Inspecting the initramfs with: lsinitramfs /boot/initrd.img-6.6.108-current-odroidxu4 | grep usb reveals that usb-storage.ko, uas.ko, and other USB mass-storage modules are missing. Root Cause The file /etc/initramfs-tools/initramfs.conf already had: MODULES=most so the base configuration was fine. However, Armbian’s initramfs build process did not automatically include the USB/SCSI modules, because the system was booted from SD and those drivers were not "in use" during image generation. As a result, the cloned SATA system lacked the drivers needed to mount its root filesystem. Solution Fix the SD card initramfs before running nand-sata-install. This ensures the SATA copy inherits a working image with all required modules. 1️⃣ Boot from SD and verify Confirm you are booted from SD: df -h / You should see /dev/mmcblk0p* as /. 2️⃣ Verify initramfs configuration Open /etc/initramfs-tools/initramfs.conf and confirm it contains: MODULES=most 3️⃣ Add required USB and SCSI modules Create or edit /etc/initramfs-tools/modules: USB host + storage + SCSI stack for SATA boot usbcore usb-common ehci-hcd ehci-platform ehci-fsl fsl-mph-dr-of xhci-hcd xhci-pci xhci-plat-hcd scsi_mod sd_mod sg uas usb-storage 4️⃣ Rebuild the initramfs and regenerate uInitrd sudo update-initramfs -c -k $(uname -r) cd /boot sudo mkimage -A arm -O linux -T ramdisk -C none -n uInitrd -d initrd.img-$(uname -r) uInitrd sync 5️⃣ Verify the new initramfs lsinitramfs /boot/initrd.img-$(uname -r) | grep usb/storage Expected output (partial): .../usb-storage.ko .../uas.ko .../ums-*.ko 6️⃣ Reboot from SD to confirm it works sudo reboot If it boots normally, the rebuilt initramfs is valid. 7️⃣ Run nand-sata-install sudo nand-sata-install Select your SATA target. Because the SD image is now fixed, the SATA copy will contain a working initramfs. 8️⃣ Update boot.ini Edit /media/mmcboot/boot.ini and set: setenv rootdev "UUID=<your SATA UUID>" 9️⃣ Reboot and verify SATA root df -h / Expected result: /dev/sda1 → / /dev/mmcblk0p1 → /media/mmcboot Result ✅ SATA boots successfully ✅ Kernel loads usb-storage, uas, sd_mod, scsi_mod early ✅ / mounts from SATA cleanly — no initramfs prompt ✅ nand-sata-install works correctly on Odroid XU4 (Noble 6.6.108) Summary Even though MODULES=most was already set, the USB/SCSI stack was not automatically included in the initramfs when booting from SD. Manually listing the required modules in /etc/initramfs-tools/modules before rebuilding ensures the image contains usb-storage.ko, uas.ko, and related drivers. Once rebuilt, both SD and SATA boots work reliably.