Jump to content

Recommended Posts

Posted

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!

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Γ—
Γ—
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines