After over a year of running ArchLinux with no issues, the unspeakable has just happened: my laptop won’t boot up!
So I go about checking the ArchLinux website to make sure there’s no indication that any recent updates may cause my computer to implode. Check. I run
pacman -Syu, and notice systemd is being updated. This isn’t my first rodeo, I’ve seen systemd being upgraded before. No big deal right?
Wrong. I run the updates and restart my laptop only to be stuck at the following message:
Job getty.target/start deleted to break ordering cycle Job systemd-user-sessions.service/start deleted to break ordering cycle Job local-fs.target/start deleted to break ordering cycle
Well, that’s just great. The first two services that were deleted are possibly responsible for the boot up process sticking with a lack of a command prompt. Preliminary searches have not been promising; this one is going to be a doozy.
Update: June 27, 2014
The issue has been semi-resolved!
The following was done:
- Boot up with ArchLinux iso USB and arch-chroot into my mounted hard drive.
downgradepackage from the AUR.
- Downgrade from systemd-214-2 to systemd-213-9.
Oddly enough, I seem to be the only one in the entire universe experiencing this issue. This will require further investigation while systemd goes on the pacman ignore list.
Update: July 19, 2014
This issue seems to have resolved itself somewhere between systemd-214-2 and systemd-215-4 in the Arch repository.