joejoe44 Posted 2 hours ago Posted 2 hours ago 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! 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.