Jayctheriot: Created page with "Snipped from: https://unix.stackexchange.com/questions/402999/is-it-ok-to-change-etc-machine-id Although `systemd-machine-id-setup` and `systemd-firstboot` are great for systems using systemd, `/etc/machine-id` is not a systemd file, despite the tag. It is also used on systems that do not use systemd. So as an alternative, you can use the `dbus-uuidgen` tool: `rm -f /etc/machine-id` and then `dbus-uuidgen --e..."`


2025-05-05T12:11:42Z
Created page with "Snipped from: https://unix.stackexchange.com/questions/402999/is-it-ok-to-change-etc-machine-id  Although <code>systemd-machine-id-setup</code> and <code>systemd-firstboot</code> are great for systems using systemd, <code>/etc/machine-id</code> is not a systemd file, despite the tag. It is also used on systems that do not use systemd. So as an alternative, you can use the <code>dbus-uuidgen</code> tool:  <code>rm -f /etc/machine-id</code> and then  <code>dbus-uuidgen --e..."
New page
Snipped from: https://unix.stackexchange.com/questions/402999/is-it-ok-to-change-etc-machine-id



Although <code>systemd-machine-id-setup</code> and <code>systemd-firstboot</code> are great for systems using systemd, <code>/etc/machine-id</code> is not a systemd file, despite the tag. It is also used on systems that do not use systemd. So as an alternative, you can use the <code>dbus-uuidgen</code> tool:

 <code>rm -f /etc/machine-id</code>

and then

 <code>dbus-uuidgen --ensure=/etc/machine-id</code>

As mentioned by Stephen Kitt, Debian systems may have both a <code>/etc/machine-id</code> and a <code>/var/lib/dbus/machine-id</code> file. If both exist as regular files, their contents should match, so there, also remove <code>/var/lib/dbus/machine-id</code>:

 <code>rm /var/lib/dbus/machine-id</code>

and re-create it:

 <code>dbus-uuidgen --ensure</code>

This last command implicitly uses <code>/var/lib/dbus/machine-id</code> as the file name and will copy the machine ID from the already-newly-generated <code>/etc/machine-id</code>.



The <code>dbus-uuidgen</code> invocation may or may not already be part of the regular boot sequence. If it is part of the boot sequence, then removing the file and rebooting should be enough. If you need to run <code>dbus-uuidgen</code> yourself, pay attention to the warning in the man page:<blockquote>If you try to change an existing machine-id on a running system, it will probably result in bad things happening. Don't try to change this file. Also, don't make it the same on two different systems; it needs to be different anytime there are two different kernels running.</blockquote>So after doing this, definitely don't continue using the system without rebooting. As an extra precaution, you may instead reboot first into rescue mode (or as you suggested, boot from a live USB stick), but from my experience, that is not necessary. Bad things may happen, but the bad things that do happen are fixed by the reboot anyway.

Change Machine-ID - Revision history