Search the Community

On my Debian13 VM that I use to build images for my boards, I have started to notice new errors that I have not seen before after this part of the logs... [🐳|🌱] After updating and cleaning image apt list cache [ 30 files ] [🐳|🌱] Image installed package hash [ ✅ base-files = 1-trixie-1armbian1-Bb095-U13.8--deb13u4-R55fa ] [🐳|🌱] Image installed package hash [ ✅ linux-image-current-rockchip64 = 6.18.26-S1fe0-Dedd0-P1f35-Cc077-H8200-HK01ba-Vc222-Bed86-R448a ] [🐳|🌱] Image installed package hash [ ✅ armbian-firmware = 1-SAa38b-B96c8-R448a ] [🐳|🌱] Image installed package hash [ ✅ armbian-bsp-cli-rockpro64-current = 1-PC1e15-V9ab0-H3400-Bd2e9-Rf36a ] [🐳|🌱] Image installed package hash [ ✅ linux-u-boot-rockpro64-current = 2025.01-S6d41-P6e2c-Hbf76-V6f3c-Be4e9-R448a ] [🐳|🌱] Image installed package hash [ ✅ linux-dtb-current-rockchip64 = 6.18.26-S1fe0-Dedd0-P1f35-Cc077-H8200-HK01ba-Vc222-Bed86-R448a ] [🐳|🔨] removed '/armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/etc/resolv.conf' [🐳|🔨] removed '/armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/sbin/initctl' [🐳|🔨] removed '/armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/sbin/start-stop-daemon' [🐳|🔨] removed '/armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/usr/sbin/policy-rc.d' [🐳|🌱] Removing qemu-user-static binary from chroot [ qemu-aarch64-static during image ] [🐳|🔨] removed '/armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/usr/bin/qemu-aarch64-static' [🐳|🌱] Unmounting [ /armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210 ] Once the unmounting of rootfs-nouuidgen-yet begins I notice the following errors spam in the logs, 1000+ lines, and finally the target unmounts successfully and the image finishes building. The images still boot fine. umount: /armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/dev: target is busy. [🐳|🔨] tmpfs /armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/dev tmpfs rw,nosuid,size=65536k,mode=755,inode64 0 0 umount: /armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/dev/pts: not mounted. umount: /armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/dev: target is busy. umount: /armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/proc: not mounted. umount: /armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/sys: not mounted umount: /armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/tmp: not mounted. umount: /armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/var/tmp: not mounted. umount: /armbian/.tmp/rootfs-no-uuidgen-yet-15898-49210/run/user/0: not mounted. Is there a way to adjust some kind of timeout for this to prevent the massive amount of "target is busy" outputs in the logs? Thank you for any help or insights!

Hi guys I cloned the build earlier with a view to building an image for a rpi5b git clone --depth 1 --branch main https://github.com/armbian/build and build/config/boards/rpi5b.csc was present. I've just refreshed the clone and it's not there - has it been removed for some reason ? Edit It's not on github either - am I going mad ? 🙂

Hi all, I'm building a rpi5b image with some success. My build machine is a x86_64 GNU/Linux with a 1gb ssd and 32gb of ram . The image builds and boots fine but there is no wlan0 device available in the booted image. I can get it by installing the armbian-firmware-full package and rebooting apt install -y armbian-firmware-full reboot I thought I could include the install in the customize-image.sh script but I get an error E: Unable to locate package armbian-firmware-full ( line 515 in the log ) - any ideas guys