I have a huuuge problem and need help. While trying to speed up the boot process on my LMDE4 machine by disabling/masking "unnecessary" services, I masked systemd-logind.service
and can no longer boot. I've already tried booting into the console by editing the grub2 configuration, but the boot process interrupts with an error:
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press Enter to continue.
So I prepared a live LMDE4 USB stick, booted into the recovery system, unlocked and mounted the LUKS encrypted LVM host volume (the one I've locked myself out of), and now at least I have access to the file system.
How can I proceed from here to unmask the service unit on that volume?
The problem is that doing sudo systemctl unmask systemd-logind.service
will unmask the service unit of the running USB recovery system and not the one on the host system. How does systemd recognize a service unit as masked? Is it something within the service file, i.e. can I just modify its content in order to unmask the service, or is it more involved?
I already checked file /lib/systemd/system/systemd-logind.service
and it says
./systemd-logind.service: ASCII text
so it does not seem to be pointing to /dev/null
(as usually happens when a service unit is masked by systemctl mask name.service
).