systemd-setup-machine-id leaving mount behind? (was "Bug#871835: Call for help: review patches for debootstrap")

Michael Biebl email at
Wed Jun 13 00:20:56 BST 2018


Am 22.04.2018 um 15:09 schrieb Antonio Terceiro:

> # findmnt | grep machine-id
> ├─/root/patched2/etc/machine-id                        /dev/mapper/lemur--vg-root[/root/patched2/run/machine-id] ext4            ro,relatime,errors=remount-ro,data=ordered
> This explains the crash in mkosi and points the problem to something
> that happens during the debootstrap run.
> I compared the output of debootstrap from unstable with the patched
> debootstrap, and they are idential, i.e. packages are installed in the
> same order, but for some reason, when running with the faster
> debootstrap, the above mount is left over.
> Looking around, I suspect that this could be left behind by
> systemd-machine-id-setup, however, I couldn't understand yet why this
> would happen.
> systemd team: could you provide any insight? for reference, I am
> attaching the current diff between debootstrap master branch, and a
> local branch where I have Thomas Lange's patched applied.

I just stumbled over this today myself when using vmdebootstrap where I
ran into the same issue as in [1]

As I couldn't reproduce the failure with cdebootstrap or debootstrap
from stretch, I ran a git bisect against debootstrap.

The first faulty commit is

And sure enough, reverting that commit fixed the dangling machine-id
mount for me.

Henrich, do you want a bug report against debootstrap for that?


Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the Pkg-systemd-maintainers mailing list