I broke my machine and can not log anymore. When at login prompt, I can log as user or root, I am rejected. I have no idea what broke the system (upgrade, wrong behavior, a 100% full ssd...). The box is clean, up to date, no fancy hacks (I think so...). Some info: Distro : Arch linux systemd : systemd-git 212.250.gd67006f-1
I am on a chroot, so I can't use systemctl. Please find below part of journalctl. I may have an insaine /var or /run partition following stupid rsynck backup script. Thank you for help as I vae no idea how to log again. I of course reinstall systemd. May 02 17:02:41 hortensia systemd-logind[370]: Failed to connect to system bus: No such file or directory May 02 17:02:41 hortensia systemd-logind[370]: Failed to fully start up daemon: No such file or directory May 02 17:02:41 hortensia systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE May 02 17:02:41 hortensia systemd[1]: Failed to start Login Service. May 02 17:02:41 hortensia systemd[1]: Unit systemd-logind.service entered failed state. May 02 17:02:41 hortensia systemd-logind[394]: Failed to connect to system bus: No such file or directory May 02 17:02:41 hortensia systemd-logind[394]: Failed to fully start up daemon: No such file or directory May 02 17:02:41 hortensia systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE May 02 17:02:41 hortensia systemd[1]: Failed to start Login Service. May 02 17:02:41 hortensia systemd[1]: Unit systemd-logind.service entered failed state. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
