Migration script Pi4 - umount: /boot: target is busy.

[KapriQ]

Migration script Pi4 - umount: /boot: target is busy.

[KapriQ]

Gonna try it. And let you know the results. Thx bro.

[terminet85]

Check if vmtouch is holding the dietpi.txt

ps aux | grep vmtouch

lsof -c vmtouch

If there is match stop vmtouch

systemctl stop vmtouch.service

[MichaIng]

Probably there was a concurrent cron job execution.

Oh, I see we need to unmount the temporary rootfs mount on failure. Please run umount /tmp/dietpi-rpi-firmware-migration/rootfs && rm -R /tmp/dietpi-rpi-firmware-migration before retrying the script.

If it fails again please check e.g. via htop which other process runs and accesses files in /boot.

[KapriQ]

root@pi:~# umount /tmp/dietpi-rpi-firmware-migration/rootfs && rm -R /tmp/dietpi-rpi-firmware-migration umount: /tmp/dietpi-rpi-firmware-migration/rootfs: no mount point specified.
After i run script, the same issue: umount: /boot: target is busy.

So I have tried to add -l to umount. And now it is running. "umount -l ...."

...
Script FINISHED. Gonna try to put SD Card to Pi5- ... ALL DONE! Wroking ...

[MichaIng]

It generally makes sense to check which process actually accesses /boot, before breaking something potentially unintended 😉. Usually nothing but our scripts and APT commands should access this mount point.

However, whatever it was should continue as before after a reboot.

[MichaIng]

Oh right, we used vmtouch a long time ago when removing the /boot tmpfs. I'll have a look whether we can identify our build/config and in case remove it. Something like:

[[ -f '/etc/default/vmtouch' ]] && grep -q dietpi /etc/default/vmtouch && G_AGP vmtouch