My Rpi fails to boot. I get /sbin/init exists but couldn't execute it (error -13). Following the symlink leads to /lib/systemd/systemd. However it seems to be a directory rather than a executable.

Any chance to recover?


  • "However it seems to be a directory rather than a executable." -> I hope not, otherwise things have gone very wrong. In any case, the first thing you should do is run e2fsck on the root filesystem. – goldilocks May 29 '19 at 13:19
  • unfortunately it is. How can I run it? it says can't run on mounted FS. Also can't run shutdown -rF now - Failed to talk to init daemon – Maxim_united May 29 '19 at 13:35
  • No, don't run it on a mounted filesystem. The init system does this automatically at boot if it appears necessary, before the fs is (re-)mounted read-write. If this system is broken it probably won't happen, so the easiest thing to do is put the card in another computer (where e2fsck is available). – goldilocks May 29 '19 at 13:45
  • Are you confusing /lib/systemd/systemd (a file) with /lib/systemd/system, (a directory)? Both exist on a non-broken system. – Mark Stosberg May 29 '19 at 14:27
  • I wish I was confusing it, but no, both are a directory. One thing that stands out is that system dir is owned by root, while systemd is owned by man (why?!) – Maxim_united May 29 '19 at 15:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.