Skip to main content ↑ ↓
Topic: fatal: unable to exec /etc/s6/current/scripts/rc.init: no such file or directory (Read 432 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

fatal: unable to exec /etc/s6/current/scripts/rc.init: no such file or directory

During the update, my computer turned off. After the reboot, I tried to restore the download of pacman packages (pacman successfully updated everything). I reboot my computer but it couldn't boot.  https://imgur.com/a/JX0HLfm

Re: fatal: unable to exec /etc/s6/current/scripts/rc.init: no such file or directory

Reply #1 –
Uh is that openrc output above the s6-linux-init line? Whatever it is, it's not something from s6. Something is horribly broken with your system. Pick one init system.

Re: fatal: unable to exec /etc/s6/current/scripts/rc.init: no such file or directory

Reply #2 –
Above the S6-Linux-INIT line its a normal output. It's not openrc.  Here is the normal output of the artix s6 iso image. https://imgur.com/a/EwwsTHK



After the computer turned off, the pacman was broken. I remember that pacman said that pyrcc5 and a few other files already existed so I made rm pyrcc5. After that, I forcibly reinstalled the python package that broke during the update. And pacman no longer gave errors. After rebooting I couldn't boot and got this output.  https://imgur.com/a/w36b9JP
 

Re: fatal: unable to exec /etc/s6/current/scripts/rc.init: no such file or directory

Reply #3 –
Oh okay, the output on the iso image is from the artix-live services which is specific to a live iso. You shouldn't have this on a normal install. Something is still terribly broken/misconfigured with your system however. /etc/s6/current/scripts/rc.init is provided by s6-linux-init.