Boot failure: /sbin/init exists but couldn't execute it

I'm getting boot errors is

[2.556845] Starting init: /etc/init exists but couldn't execute it (error -)
[2.558646] Run /bin/init as init process
[2.561250] Run /bin/sh as init process
/bin/sh: 0: can't access tty; job control turned off

Does anyone have any idea about this issue?

1 Reply

@aiesectw --

On my Debian 10(.10) distro, I have the following:

[email protected]:~$ ll /sbin/init
lrwxrwxrwx 1 root root 20 Mar 18 12:59 /sbin/init -> /lib/systemd/systemd


[email protected]:~$ ll /lib/systemd/systemd
-rwxr-xr-x 1 root root 1489208 Mar 18 12:59 /lib/systemd/systemd

Please verify that the ownership/permissions are correct.

Another day, another problem with systemd(1)

systemd(1) is 70 binaries and over 1.4 million lines of (non-POSIX-compliant) code (~10MiB of stuff). SysV init for Arch Linux (& *BSD) is less than 2100 lines of code in a single binary (~800KiB of stuff).

I have more problems with systemd(1) than any other part of Linux!!! Someone remind me again what problem systemd(1) was supposed to solve anyway? If the problem was that sysadmin unemployment was too high because SysV init was too stable, systemd(1) succeeds at solving that problem admirably.

-- sw


Please enter an answer

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct