18
Systemd/Init Issues
(lemy.lol)
Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.
From here I’d boot from a rescue usb stick or something and mount the system partitions under it to continue troubleshooting.
If you don’t have one or it doesn’t work, you may be able to get into the system by passing
init=/bin/sh
or similar on the kernel cmdline. You’ll get a bare minimum root shell without a login prompt.I did both, and I don't know what I should do next.
Edit: grammar
chroot /mnt
(if permission denied, run it with sudo)journald
was the first to fail, maybe check its logs first)If you get errors like "no proc filesystem mounted", then you also need to mount special filesystems before entering the chroot. Run these commands as root: