You are not logged in.
Pages: 1
Hey guys,
I rebooted my arch this morning, and found the error above on my screen. I looked on the arch forums to solve the problem but made it worst so I did a fresh install of arch (I had backups fortunatly!!). Still, what I found is that the problem was with /sbin/init symlink. When I tried to arch-chroot from a live system, I had another error saying that /bin/bash was not found.
My question is does anyone know how is that I get this error on boot even though I didn't update any packages since last reboot?
Thanks
Error:Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own.Good luck.
sh: can't access tty; job control turned off
[rootfs ]#Last edited by luquf (2018-11-16 17:23:06)
Offline
Details about how you have set up your system, specifically, how you have configured your boot loader/manager are necessary.
Moving to NC...
Offline
Hi,
I am using grub, os-prober and efibootmg.
I installed grub on my efi partition as follow:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=archlinux --recheckFrom what I understood, the problem may be due to the fact that "systemd-sysvcompat" has been deleted (detected as an orphan).
Happened twice in two months.
Offline
From what I understood, the problem may be due to the fact that "systemd-sysvcompat" has been deleted (detected as an orphan).
Deleted by what?
Offline
Well that's what I don't know because I did reboot with no issues after the previous update, and this happened after a casual reboot of my computer
Offline
What detected systemd-sysvcompat as an orphan or what makes you believe it has been?
Offline
If you installed systemd-sysvcompat as part of the package group base following the official installation guide, it would be "explicitely installed" and thus not show up as an unneeded package, nor as an orphaned package as long as you have the repository [core] enabled.
However, you can live happily without systemd-sysvcompat as I do with all of my systems, by specifying the option "init=/usr/lib/systemd/systemd" in your kernel command line.
Please also note, that not having systemd-sysvcompat installed also means, that you will not have shutdown, reboot, etc. available and you'd have to use systemctl for that.
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Pages: 1