Boot error: cannot execute "/etc/init.d/rcS/"

[marconicoletti]

After having upgraded my Debian Unstable version I got a problem in booting the system, something like:

Code: Select all

INIT:cannot execute "etc/init.d/rcS
entering runlevel 3
INIT:cannot execute "etc/init.d/rc"

If I execute :

Code: Select all

apt-get install -f

It says to try the command:

Code: Select all

dpkg -reconfigure -a

but it stops answering that:

Code: Select all

Read-only file system

If I try to execute

Code: Select all

fsck -f

it says that the disk is clean!

Please HELP ME!!

[edbarx]

Code: Select all

INIT:cannot execute "etc/init.d/rcS
entering runlevel 3
INIT:cannot execute "etc/init.d/rc"

What are rcS and rc? I am suspecting they are directories and that init doesn't expect any directories under /etc/init.d.

Did you create them yourself? If yes, the obvious solution is to undo the changes manually.

[marconicoletti]

Actually I don't know what they are.

But for sure I did not create them manually.

[hazel]

After having upgraded my Debian Unstable version I got a problem in booting the system, something like:

Code: Select all

INIT:cannot execute "etc/init.d/rcS
entering runlevel 3
INIT:cannot execute "etc/init.d/rc"

They're meant to be there. They are the scripts that start up your system. rcS runs the system initialisation stuff in rcS.d and rc runs the runlevel-specific scripts. The question is why can't init execute them? It's not a permissions issue because you get a different message for that.

[edbarx]

Both of the files you mentioned are scripts. I checked on my Debian Lenny installation. My previous posts in this thread were answered from a Windows machine as I did not have physical access to my Debian machine. Now the problem should be to find why the scripts cannot be executed. As I suspect that the problem can be caused by file attributes, I am posting mine for your information: (from Lenny)

Code: Select all

-rwxr-xr-x 1 root root    117 2005-12-02 17:44 rcS
-rwxr-xr-x 1 root root  10036 2008-08-12 13:33 rc

[smallchange]

The read-only filesystem may indicate that a problem has occured with the disc so that it was remounted read-only. Run

Code: Select all

mount -o remount /

and it will get remounted read-write. Then you can try

Code: Select all

dpkg --configure -a

That much should work and then you may be able to reboot and have the init scripts run so that you can use aptitude to clean up.

[marconicoletti]

Thanks, I got it in the end.

I rebooted using the Debian CD and operating in rescue mode. The problem was that the /bin/sh disappeared after system update. I have created a link to bash shell (ln bash sh) and then I could run the dpkg --configure -a command.

Thanks

[biggingerbear]

I have experienced the same problem but have not been able to solve it using the same method that you have here.

My setup of debian is different however. Being somewhat of a beginner with debian and GNU linux in general, and a bit short of time, I have been using a turnkey wordpress server running on a vmware virtual machine (base system WS2012). Debian is the operating system of choice for this turnkey distribution.

I restarted my virtual machine after adding some extra ram to my server to see the same error that you marconicoletti, experienced.

I then booted into a debian rescue install but I could only run a shell from the installer, not the root for some reason, and then I couldn't use the commands that you have used.

I have booted into systemrescuecd to hopefully make it able to use the same method that you have but I have had no luck.

Could you tell me the exact commands you used, as I presume I am making a mistake in trying to link to the bash shell.

I would really appreciate the help, I know it was a post form a long time ago, but maybe you could remember it?

Thanks
// Alan

[biggingerbear]

This link also explains the problem quite nicely, but due to my noob-ishness and inexperience I haven't been able to use it to solve the problem that he points out

http://www.linux-pages.com/2011/03/cann ... nit-d-rcs/

I am not sure how to actually go about using his solution.

Could anyone dumb it down and take me through it step by step?

I would be ridiculously grateful! Thanks

//Alan

[biggingerbear]

Here are the actual errors I receive when booting...

[AnInkedSoul]

You should probably start a new thread.