Bug#986721: live-boot: Failed to unmount /run/live/medium: Device or resource busy - which might corrupt live USB sticks
As I posted on https://github.com/systemd/systemd/issues/17988, it seems systemd 248 has fixed this issue? I tired systemd (248.3-1ubuntu1) from Ubuntu impish and systemd (248.3-1) from Debian experimental, this are no such error messages anymore: Failed to unmount /run/live/medium: Device or resource busy systemd-shutdown[1]: Could not detach loopback /dev/loop0: Device or resource busy systemd-shutdown[1]: Failed to finalize file systems, loop devices, ignoring. Not sure if the error messages are hidden or is this issue really fixed... Steven On 4/16/21 1:25 AM, Marcel Partap wrote: > […] > > The key problem is the deletion of the original root ramdisk in its > init scripts. This needs to be avoided so there is a valid root (and > upper mount) to switch back to on shutdown. > > My attempts of getting the mount chain to untangle without changing > that were fruitless xD > ( https://github.com/systemd/systemd/issues/17988 ) > > […] > > On 10/04/2021 09:51, Steven Shiau wrote: >> Failed to unmount /run/live/medium: Device or resource busy >> Is any workaround we can try to avoid this? > -- Steven Shiau Public Key Server PGP Key ID: 4096R/163E3FB0 Fingerprint: EB1D D5BF 6F88 820B BCF5 356C 8E94 C9CD 163E 3FB0
Bug#986721: live-boot: Failed to unmount /run/live/medium: Device or resource busy - which might corrupt live USB sticks
[…] The key problem is the deletion of the original root ramdisk in its init scripts. This needs to be avoided so there is a valid root (and upper mount) to switch back to on shutdown. My attempts of getting the mount chain to untangle without changing that were fruitless xD ( https://github.com/systemd/systemd/issues/17988 ) […] On 10/04/2021 09:51, Steven Shiau wrote: Failed to unmount /run/live/medium: Device or resource busy Is any workaround we can try to avoid this?
Bug#986721: live-boot: Failed to unmount /run/live/medium: Device or resource busy - which might corrupt live USB sticks
Package: live-boot Version: 1:20210208 Severity: important Dear Maintainer, * What led up to the situation? When rebooting or halting the Debian live system, it gives these error messages: Failed to unmount /run/live/medium: Device or resource busy systemd-shutdown[1]: Could not detach loopback /dev/loop0: Device or resource busy systemd-shutdown[1]: Failed to finalize file systems, loop devices, ignoring. This error might corrupt the file system on the live USB flash drive. It been reported on different forums: https://github.com/systemd/systemd/issues/17988 https://github.com/grml/grml/issues/109 https://github.com/grml/grml/issues/150 https://github.com/systemd/systemd/issues/2814 System developers mentioned: "isn't the simpler and better fix to change debian to not set things up that way? Specifically, why expose the "components" of the overlayfs at all? why not just leave them outside the tree when pivotting into the overlayfs?" This issue is not solved yet in live-boot 1:20210208. Is any workaround we can try to avoid this? Thank you very much. -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 (SMP w/6 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages live-boot depends on: ii live-boot-initramfs-tools [live-boot-backend] 1:20210208.drbl2 Versions of packages live-boot recommends: ii live-boot-doc 1:20210208 ii live-tools 1:20190831 ii rsync 3.2.3-4 ii uuid-runtime 2.36.1-7 Versions of packages live-boot suggests: pn cryptsetup pn curlftpfs pn httpfs2 ii wget 1.21-1+b1 -- no debconf information -- Steven Shiau Public Key Server PGP Key ID: 4096R/163E3FB0 Fingerprint: EB1D D5BF 6F88 820B BCF5 356C 8E94 C9CD 163E 3FB0
