Arch Linux
Since the last update i cannot start my computer, i cant even switch to a TTY to revert the last pacman update.
Heres how the boot screen shows up :
I really have no idea what to do here. if any one could offer assistance id be a very happy man.
Last edited by SilverOne (2014-03-21 23:47:14)
#2 2014-03-18 21:01:36
ewaller Administrator From: Pasadena, CA Registered: 2009-07-13 Posts: 19,356
Re: [SOLVED] Can’t boot : failed to start login service
You say you cannot switch to a TTY, please confirm you tried Ctrl-Alt-F2 (or F3 through F6).
If that does not work, boot from an installation disk, chroot in to your arch system, and disable gdm using systemctl. Then reboot.
Alternately, from within the chroot (or the tty if that worked) and ensure your system is fully up to date with a pacman -Syu. It is possible you caught a mirror in the middle of its updating.
Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way
#3 2014-03-18 21:49:00
Re: [SOLVED] Can’t boot : failed to start login service
Thank you so much for your fast reply. I managed to chroot into the drive and disabled gdm, i can now login. I ran pacman -Syu i got a failed to initialize alpm library error (could not find or read the directory). The directory /var/cache/pacman/pkg does exit and contains packages.
pacman updated the following packages:
bash(4.2.05-5 to 4.3-2)
acpid(2.0.21-1 to 2.0.22-1)
freetype2(2.5.3-1 to 2.5.3-2)
libwbclient(4.1.5-1 to 4.1.6-1)
mpg123 (1.18-1-1 o 1.19.0-1)
netctl(1.4-2 to 1.6-1)
openssh (6.5p1-2 to 6.6p1-2)
python2-pillow (2.3.0-3 to 2.3.1-1)
talloc(2.0.8-2 to 2.1.0-1)
tevent (0.9.19-2 to 0.9.21-2)
smbclient (4.1.5-1 to 4.1.6-1)
soundtouch (1.7.1.1 to 1.8.0-1)
thunderbird(24.3.0-1 to 24.4.0-1)
When the system was working , i mistakenly wrote the following command:
notice i forgot to add a destination. im thinking this might have something to do with the state my system is currently in.
At this point im guessing only a reinstall will fix this.
systemd reports the following units fail:
avahi-daemon.service
bluetooth.service
networkmanager.service
systemd-logind.service
Last edited by SilverOne (2014-03-18 21:53:53)
Как запустить систему
Gave up waiting for suspend/resume device
/dev/sdc1: recovering journal
/dev/sdc1: clean, 172491/959104 files, 3835904/3840000 blocks
[[0;1;31mFAILED[0m] Failed to start kesl.
See ‘systemctl status kesl-supervisor.service’ for details.
[[0;32m OK [0m] Started Save/Restore Sound Card State.
[[0;32m OK [0m] Started PARSec events logging daemon.
[[0;32m OK [0m] Started Login Service.
[[0;32m OK [0m] Started LSB: Start some power management scripts.
[[0;32m OK [0m] Started Raise network interfaces.
[[0;1;31mFAILED[0m] Failed to start Hostname Service.
See ‘systemctl status systemd-hostnamed.service’ for details.
[[0;32m OK [0m] Started VirtualBox Linux kernel module.
Starting vboxballoonctrl-service.service.
Starting vboxweb-service.service.
Starting vboxautostart-service.service.
[[0;32m OK [0m] Started vboxballoonctrl-service.service.
[[0;32m OK [0m] Started vboxweb-service.service.
[[0;32m OK [0m] Started vboxautostart-service.service.
[[0;32m OK [0m] Started Intitialize Parsec Subsystem.
[[0;32m OK [0m] Started Network Manager.
[[0;32m OK [0m] Reached target Network.
Starting Permit User Sessions.
Starting OpenBSD Secure Shell server.
Starting Network Manager Wait Online.
[[0;32m OK [0m] Started Permit User Sessions.
Starting Network Manager Script Dispatcher Service.
Starting Hold until boot process finishes up.
Starting Terminate Plymouth Boot Screen.
[[0;32m OK [0m] Started The FLY get exec service.
[[0;32m OK [0m] Started The FLY login manager.
[[0;32m OK [0m] Started Network Manager Script Dispatcher Service.
Failed to start login service astra linux
Уже на двух компах за сегодня появилась одинаковая проблема: после перезагрузки, комп очень долго загружается и останавливается на черном экране с курсором. На терминал перейти могу. Попробовал установить nomodeset, вывод при загрузке такой.
[FAILED] Failed to start Raise network interfaces
.
[FAILED] Failed to start Login Service (6 раз повторяется)
Удалил все, что связано с nvidia (стояло только nvidia-prime-applet), ошибка та же.
Попытки запустить startx или перезапустить lightdm тоже ничего не дают
Система: Linux Mint 19 Tara
Возможно дело в критической ошибке после обновления base-file 19.0.2. Почитать подробнее можно здесь .
В общем и целом, если не знаете английского, то вот инструкции в переводе:
— Включить комп
— Нажать SHIFT пока идет загрузка, чтобы появилось загрузочное меню
— Выбрать Advanced options for Linux Mint 19
— Затем выбрать «recovery mode»
— После появления Recovery Menu выбрать «root — Drop to root shell prompt»
— Нажать Enter
Теперь можно вводить команды. Вводим следующие:
mount -o rw,remount / rm -rf /var/run ln -s /run /var/runПерезагружаемся. Компьютер теперь должен нормально загрузиться.
Чтобы полностью избавиться от проблемы, открываем терминал и вводим следующее:
wget linuxmint.com/tmp/base-files_19.0.1_all.deb sudo dpkg -i base-files_19.0.1_all.debCannot login: Failed to start Login Service
I’ve got a VirtualBox instance of Oracle Linux 7.2 which won’t start because of Failed to start Login Service . On the booting sequence the process hangs on this message and doesn’t continue, so I can’t even log in and execute systemctl status systemd-logind.service . The probable cause for this is, that I removed zsh while all my users (including root) have zsh set as the default shell (duh!). After that the machine started and I got to the login prompt, but I couldn’t login since the shell couldn’t be found. I then inserted a Live CD and went into /etc/passwd to change the default shell for users to /bin/bash . After this the login service won’t start at all. Any ideas how to fix this?
3 Answers 3
I found out that after changing /etc/passwd it didn’t have the right SELinux settings anymore. I don’t really need SELinux on my machine so I solved the problem by disabling SELinux altogether. This is easily done by modifying the file /etc/selinux/config and setting the option SELINUX=permissive (if you want to keep SELinux file labeling to enable it later) or SELINUX=disabled (turning it off completely).
I encountered this today with CentOS 7.2 on VirtualBox. I was able to ssh in as a regular user and issued
Then rebooted to reset all contexts. It takes a while to boot, but worked.
After using chage in single user mode because of expired password, it is required to boot with SELINUX=permissive set in /etc/selinux/config to restore proper labels.
Get proper SELinux context for each modified file from a sane system with ls -Z /etc/passwd /etc/shadow and apply context back to broken system.
As an example, here are set of commands used on a CentOS 7 after chage — DO NOT APPLY without comparison from a sane system (test or preproduction) !
chcon system_u:object_r:passwd_file_t:s0 /etc/passwd chcon system_u:object_r:passwd_file_t:s0 /etc/group chcon system_u:object_r:shadow_t:s0 /etc/shadow chcon system_u:object_r:shadow_t:s0 /etc/gshadow Review SELinux context of any file you have modified in single mode, before rebooting with SELINUX=enforcing to get back to normal operations.
Arch Linux
What’s up guys!
I checked the wiki and searched the forum + google but I can’t seem to find an answer to this darn puzzle.
DISCLAIMER: I am new to linux so please be patient with me.
My system was working fine and all of a sudden I get this error in startup:
systemd-logind.service failed
output of «systemctl status systemd-logind.service» is:
root:~/ # systemctl status systemd-logind.service ● systemd-logind.service - Login Service Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled) Active: failed (Result: start-limit) since Fri 2015-01-09 21:21:40 EST; 28min ago Docs: man:systemd-logind.service(8) man:logind.conf(5) [url]http://www.freedesktop.org/wiki/Software/systemd/logind[/url] [url]http://www.freedesktop.org/wiki/Software/systemd/multiseat[/url] Process: 403 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE) Main PID: 403 (code=exited, status=1/FAILURE) Status: "Shutting down. " Jan 09 21:21:40 Katana systemd[1]: Failed to start Login Service. Jan 09 21:21:40 Katana systemd[1]: Unit systemd-logind.service entered failed state. Jan 09 21:21:40 Katana systemd[1]: systemd-logind.service failed. Jan 09 21:21:40 Katana systemd[1]: start request repeated too quickly for systemd-logind.service Jan 09 21:21:40 Katana systemd[1]: Failed to start Login Service. Jan 09 21:21:40 Katana systemd[1]: Unit systemd-logind.service entered failed state. Jan 09 21:21:40 Katana systemd[1]: systemd-logind.service failed.The ouput of journalctl _PID=403 is:
root:~/ # journalctl _PID=403 [21:50:19] -- Logs begin at Mon 2015-01-05 20:58:15 EST, end at Fri 2015-01-09 21:26:07 EST. -- Jan 09 05:16:22 Katana systemd-logind[403]: Failed to connect to system bus: No such file or directory Jan 09 05:16:22 Katana systemd-logind[403]: Failed to fully start up daemon: No such file or directory -- Reboot -- Jan 09 06:35:39 Katana systemd-logind[403]: Failed to connect to system bus: No such file or directory Jan 09 06:35:39 Katana systemd-logind[403]: Failed to fully start up daemon: No such file or directory -- Reboot -- Jan 09 21:21:40 Katana systemd-logind[403]: Failed to connect to system bus: No such file or directory Jan 09 21:21:40 Katana systemd-logind[403]: Failed to fully start up daemon: No such file or directoryI tried to reinstall systemd + reboot — no luck.
I tried
systemctl disable systemd-logind.service+ reboot — no luck. Strangely it still loads after reboot.
I tried
systemctl disable systemd-logind+ reboot — no luck. Strangely it still loads after reboot.
My system seems to be running normally otherwise so I don’t know if this can be ignored, but I’d rather have an error-free system.
Any suggestions would be greatly appreciated. Thank you in advance for your time and concern!
Last edited by rujutsu (2015-01-11 21:46:02)