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 <steven _at_ stevenshiau org> Public Key Server PGP Key ID: 4096R/163E3FB0 Fingerprint: EB1D D5BF 6F88 820B BCF5 356C 8E94 C9CD 163E 3FB0
