[Bug]: Helios64 - ubuntu only - infinty loop on umount

[BipBip1981]

What happened?

Hi,
Only on ubuntu building, infinty loop on umounting.
Have a good day.

[🌿] Re-enabling [ initramfs-tools hook for kernel ]
[🔨] mode of '/etc/kernel/postinst.d/initramfs-tools' changed from 0644 (rw-r--r--) to 0755 (rwxr-xr-x)
[🌱] Unmounting [ /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674 ]
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/sys: target is busy.
[🔨] chsys /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/sys sysfs rw,relatime 0 0
[🔨] efivarfs /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/dev/pts: no mount point specified.
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/dev: not mounted
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/proc: not mounted.
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/sys: target is busy.
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/tmp: not mounted.
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/var/tmp: not mounted.
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/run/user/0: not mounted.
[🔨] chsys /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/sys sysfs rw,relatime 0 0
[🔨] efivarfs /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/dev/pts: no mount point specified.
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/dev: not mounted
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/proc: not mounted.
umount: /home/armbianbuilder/build/.tmp/mount-0cf338f4-3c36-4528-ab5e-f6c104dbf674/sys: target is busy.

How to reproduce?

git clone https://github.com/armbian/build ; cd build ; ./compile.sh
-> Do not change the kernel configuration
-> helios64
-> current
-> noble
-> image with console interface (server)
-> Minimal (Standard same but more time to reproduce, use Minimal ;-) )

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

Ubuntu 24.04 Noble

Are you building on Windows WSL2?

• Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

log-build-0012b9dd-ace9-4ff8-a3a7-4a3a69349bcf.log

[github-actions]

Hey @BipBip1981! 👋

Thanks for opening your first issue with the Armbian project — we’re glad to have you here! 🧡
Your input doesn’t just help us improve the project — it benefits everyone who uses Armbian.

If you'd like to stay informed about project updates or collaborate more closely with the team,
you can optionally share some personal contact preferences at armbian.com/update-data.
This helps us keep in touch without relying solely on GitHub notifications.

Also, don’t forget to ⭐ star the repo to support the work — and welcome aboard! 🚀

[github-actions]

Jira ticket: AR-2726

[EvilOlaf]

full logs missing

[EvilOlaf]

Confirmed: https://paste.armbian.com/awunurobar

[EvilOlaf]

Hm 2nd attempt with debug enabled successful. https://paste.armbian.com/dekicufiqa

[BipBip1981]

full logs missing

i had it below my message, sorry

[BipBip1981]

Same crash to my side with: ./compile.sh BOARD=helios64 BRANCH=current BUILD_MINIMAL=yes DEBUG=yes KERNEL_CONFIGURE=no RELEASE=noble SHARE_LOGS=yes

[🌱] Unmounting [ /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740 ]
[🐛] Unmounting... [ target: /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740 ]
umount: /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740/sys: target is busy.
[🐛] wait_for_disk_sync: after umount chroot [ sync start, timeout_seconds:30 ]
[🐛] wait_for_disk_sync: after umount chroot [ sync done worked: 1 sync_timeout: 0 ]
[🔨] chsys /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740/sys sysfs rw,relatime 0 0
[🔨] efivarfs /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740/sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
[🐛] Unmounting... [ target: /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740 ]
umount: /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740/dev/pts: no mount point specified.
umount: /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740/dev: not mounted
umount: /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740/proc: not mounted.
umount: /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740/sys: target is busy.
umount: /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740/tmp: not mounted.
umount: /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740/var/tmp: not mounted.
umount: /home/armbianbuilder/build/.tmp/mount-33783eb0-5c8e-46a8-86f0-9e6cfa8e8740/run/user/0: not mounted.
[🐛] wait_for_disk_sync: after umount chroot [ sync start, timeout_seconds:30 ]
[🐛] wait_for_disk_sync: after umount chroot [ sync done worked: 1 sync_timeout: 0 ]

[prahal]

See https://github.com/armbian/os/actions/runs/16793323666/job/47578619551 and other failing jobs in this run.

[🥑] Group prepare_partitions
[🥑] Group create_image_from_sdcard_rootfs
  [🐳|🌿] Copying files via rsync to [ / (MOUNT root) ]
  [🐳|🔨]   
  [🐳|🔨]   sent 5.61G bytes  received 2.26M bytes  249.31M bytes/sec
  [🐳|🔨]   total size is 5.60G  speedup is 1.00
  [🐳|🌿] Copying files to [ /boot (MOUNT /boot) ]
  [🐳|🔨]   
  [🐳|🔨]   sent 64.55M bytes  received 5.78K bytes  129.11M bytes/sec
  [🐳|🔨]   total size is 64.52M  speedup is 1.00
  [🐳|🌱] Deploying qemu-user-static binary to chroot [ qemu-aarch64-static during initrd# ]
  [🐳|🔨]   '/usr/bin/qemu-aarch64-static' -> '/armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/usr/bin/qemu-aarch64-static'
  [🐳|🌿] Updating initramfs... [ TMPDIR=/tmp update-initramfs -u -k 6.12.41-current-rockchip64 ]
  [🐳|🔨]   update-initramfs: Generating /boot/initrd.img-6.12.41-current-rockchip64
  [🐳|🔨]   update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.12.41-current-rockchip64
  [🐳|🔨]   Image Name:   uInitrd
  [🐳|🔨]   Created:      Fri Aug  8 07:49:45 2025
  [🐳|🔨]   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
  [🐳|🔨]   Data Size:    24071655 Bytes = 23507.48 KiB = 22.96 MiB
  [🐳|🔨]   Load Address: 00000000
  [🐳|🔨]   Entry Point:  00000000
  [🐳|🔨]   update-initramfs: Armbian: Symlinking /boot/uInitrd-6.12.41-current-rockchip64 to /boot/uInitrd
  [🐳|🔨]   '/boot/uInitrd' -> 'uInitrd-6.12.41-current-rockchip64'
  [🐳|🔨]   update-initramfs: Armbian: done.
  [🐳|🌱] Updated initramfs. [ TMPDIR=/tmp update-initramfs -u -k 6.12.41-current-rockchip64 ]
  [🐳|🔨]   '/armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/boot/initrd.img-6.12.41-current-rockchip64' -> '/armbian/cache/initrd/initrd.img-6.12.41-current-rockchip64-612da2842fb59ee93bfe5159b58268ba'
  [🐳|🔨]   '/armbian/.tmp/work-77048063-d3ee-4f4e-9f36-c59af0725f65/initrd.img-6.12.41-current-rockchip64.77048063-d3ee-4f4e-9f36-c59af0725f65.manifest' -> '/armbian/cache/initrd/initrd.manifest-6.12.41-current-rockchip64.last.manifest'
  [🐳|🌿] Re-enabling [ initramfs-tools hook for kernel ]
  [🐳|🔨]   mode of '/etc/kernel/postinst.d/initramfs-tools' changed from 0644 (rw-r--r--) to 0755 (rwxr-xr-x)
  [🐳|🌱] Unmounting [ /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65 ]
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/sys: target is busy.
  [🐳|🔨]   chsys /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/sys sysfs rw,relatime 0 0
  [🐳|🔨]   efivarfs /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/dev/pts: no mount point specified.
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/dev: not mounted
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/proc: not mounted.
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/sys: target is busy.
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/tmp: not mounted.
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/var/tmp: not mounted.
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/run/user/0: not mounted.
  [🐳|🔨]   chsys /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/sys sysfs rw,relatime 0 0
  [🐳|🔨]   efivarfs /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/dev/pts: no mount point specified.
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/dev: not mounted
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/proc: not mounted.
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/sys: target is busy.
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/tmp: not mounted.
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/var/tmp: not mounted.
  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/run/user/0: not mounted.

likely the fault is:

  umount: /armbian/.tmp/mount-77048063-d3ee-4f4e-9f36-c59af0725f65/sys: target is busy.

[igorpecovnik]

Confirmed https://paste.armbian.com/letojisisi Are we seeing this on any other hw?

I started to build more images - https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-standard-support.yml

[EvilOlaf]

Yeah got a couple of stuck Helios64 again, killed them.

[prahal]

Seems not an issue on other boards because odroidm1, also a rockchip64 family, does not reproduce.
Could it be that before unmount, after updating the initramfs in an image_from_sdcard_rootfs qemu chroot, we would trigger systemd-shutdown ?
Because helios64 has systemd-shutdown hook to mangle the gpio via /sys. Could it be it hangs in qemu and prevents unmounting the qemu chroot /sys?