arch-linux – Failed to Boot After System Update on Arch Linux

arch linuxbootpacmansystemd

After I updated the system through pacman, the system fails to boot. It seems that some services are not started during boot time. It shows like this: Error

Boot errors

Failed to start Hostname Services.
Failed to Start WPA supplicant.
Failed to start Network Manager Script Dispatcher Services.
Failed to start dhcpd on various interfaces.
Failed to start Permit User Sessions.

Solutions I tried:

  1. By using bootable USB,

    1. I mounted the drive,
    2. arch-chroot to enter the system,
    3. Updated the packages, re-installed linux, mkinitpcio and systemd as suggested in troubleshooting in arch-wiki.

  2. As above method failed, I opened the system in 'rescue' mode and I manually started the services systemd-hostnamed, systemd-user-sessions and dhcpd. Then, my PC booted. And it became normal. But, it did not last.

Next time after reboot, same problem arises. Every time, need to open the system in rescue mode.

Please suggest the solution. I exactly don't know the cause. Thank you in advance.

Best Answer

Have same issue. @fra-san: Thank you for the hint, how to get easily more information from logs, so here's what I got from that:

Apr 23 22:30:19 myhost systemd[1]: systemd-hostnamed.service: Failed to create cgroup /system.slice/systemd-hostnamed.service: No such file or directory
Apr 23 22:30:19 myhost systemd[1]: Starting Hostname Service...
Apr 23 22:30:19 myhost systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=219/CGROUP
Apr 23 22:30:19 myhost systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'.
Apr 23 22:30:19 myhost systemd[1]: Failed to start Hostname Service.

On my system, after some warm reboots it was starting up again, so looks like timing or race condition issue.

This same issue has been posted on the Arch Linux Forums. It turned out to be a bug in dhcpcd 9.0.1 (for details: the report on Arch's bug tracker and the one on dhcpcd's mailing list).
A working temporary solution is to downgrade dhcpcd to a pre-9.0.1 version. The bug was fixed in version 9.0.2.

Related Question