After making a typo in a change to /etc/inittab, I can no longer do a normal reboot. I end up with these lines: Master Resource Control: run level 6 has been reached. Init: no more processes left in this run level and the keyboard is frozen. I have been getting back to my normal KDE by getting to run level 1 and remountiing the file system. But I have not found a way to restore normal shutdowns. Can anyone help me with this? I am using Suse 7.1. Jack Reilly
On 5 Nov 2001, Jack Reilly wrote:
After making a typo in a change to /etc/inittab, I can no longer do a normal reboot. I end up with these lines: Master Resource Control: run level 6 has been reached. Init: no more processes left in this run level
and the keyboard is frozen.
I have been getting back to my normal KDE by getting to run level 1 and remountiing the file system. But I have not found a way to restore normal shutdowns.
Can anyone help me with this? I am using Suse 7.1.
Two solutions: A. I think you may have screwed up your /etc/inittab. SuSEconfig, I believe, can fix it. Boot into runlevel 1 (single user mode) and make sure CHECK_INITTAB is set to yes in /etc/rc.config. Then run 'SuSEconfig' and you should be fine. B. This is the hands-on approach, maybe the faster one. Boot into single user mode and check your /etc/inittab. In the beginning will be line like so: id:3:initdefault: Or in your case, I believe: id:6:initdefault: Change this to: id:5:initdefault: And reboot... You should be fine now. -- Karol Pietrzak PGP KeyID: 3A1446A0
On Monday 05 November 2001 18:17, Karol Pietrzak wrote:
Two solutions:
A. I think you may have screwed up your /etc/inittab. SuSEconfig, I believe, can fix it. Boot into runlevel 1 (single user mode) and make sure CHECK_INITTAB is set to yes in /etc/rc.config. Then run 'SuSEconfig' and you should be fine.
B. This is the hands-on approach, maybe the faster one. Boot into single user mode and check your /etc/inittab. In the beginning will be line like so:
id:3:initdefault:
Or in your case, I believe:
id:6:initdefault:
Change this to:
id:5:initdefault:
Thanks for your suggestions but I had no luck . CHECK_INITTAB is set to yes. The default line in inittab is: # default runlevel id:5:initdefault: I had replaced /etc/inittab with the original when I was able to access my files. Attached is the file I am using. Maybe I missed something. If you have any other suggestions please fire away. I've been in this mess for three weeks! Jack Reilly aa6vn@pacbell.net * * * * * * * * * * * * * * * * * * * *
Jack Reilly wrote:
I had replaced /etc/inittab with the original when I was able to access my files. Attached is the file I am using. Maybe I missed something.
What's in the rc.6 directory (I can't remember where it is, but probably under /etc/rc.d or /etc/init.d)? These are the commands that are executed (in order) as runlevel 6 is entered. Do any of them report problems? Cheers, -nick
Nick Battle wrote wrote:
What's in the rc.6 directory (I can't remember where it is, but probably under /etc/rc.d or /etc/init.d)? These are the commands that are executed (in order) as runlevel 6 is entered. Do any of them report problems?
/etc/init.d/rc6.d contains only: lrwxrwxrwx 1 root root 9 Mar 13 2001 S20reboot -> ../reboot I thought surely that was the problem ...only one command to execute. But then I found in the /etc/init.d README: 6 This level is used for rebooting the system. The only valid service for this level is the script reboot, which is linked into /etc/init.d/rc6.d/. The script reboot executes /etc/init.d/halt.local. Specials system issues for halt or reboot should be added there. I could not find any clue in halt.local, but then I don't do too well reading scripts. Rooting thru a lot of the scripts I am still unable to find the two lines I get before things freeze: Master Resource Control: run level 6 has been reached. Init: no more processes left in this run level If I could find the echo commands that produce these two lines I would think that could show the problem. The directories /etc/init.d and /etc/rc.d appear to be identical. Is that normal? The identical READMEs that they have, show /init.d as the subject. Many thanks. 73 ....Jack
On Wed, Nov 07, 2001 at 11:17:28AM -0800, Jack Reilly wrote:
Nick Battle wrote wrote:
What's in the rc.6 directory (I can't remember where it is, but probably under /etc/rc.d or /etc/init.d)? These are the commands that are executed (in order) as runlevel 6 is entered. Do any of them report problems?
/etc/init.d/rc6.d contains only: lrwxrwxrwx 1 root root 9 Mar 13 2001 S20reboot -> ../reboot
I thought surely that was the problem ...only one command to execute. But then I found in the /etc/init.d README:
6 This level is used for rebooting the system. The only valid service for this level is the script reboot, which is linked into /etc/init.d/rc6.d/. The script reboot executes /etc/init.d/halt.local. Specials system issues for halt or reboot should be added there.
I could not find any clue in halt.local, but then I don't do too well reading scripts.
By default there won't be anything in halt.local, just a preamble and a "." of the system configuration file. It is meant for you to put anything special you want to happen when shutting down the system.
Rooting thru a lot of the scripts I am still unable to find the two lines I get before things freeze:
Master Resource Control: run level 6 has been reached. Init: no more processes left in this run level
If I could find the echo commands that produce these two lines I would think that could show the problem.
I dont think that would help. The first is a standard message when run-level 6 is reached, probably issued by /sbin/halt. The second is from init, but you shouldn't normally get it.
The directories /etc/init.d and /etc/rc.d appear to be identical. Is that normal? The identical READMEs that they have, show /init.d as the subject.
/etc/rc.d is a symbolic link to /etc/init.d, so whether you cd /etc/rc.d or cd /etc/init.d You end up in the same place, so don't worry about that. It is for historical compatibility. What you should have in /etc/rc.d/rc.6 is: S20reboot -> ../reboot If you look at ../reboot you will see it itself is a symbolic link to a local file called "halt". This "halt" determines if it has been called by the name "reboot" or the name "halt", in order to decide what action to take. In the case of "halt" it will eventually call /sbin/halt, which is what actually causes the system to "halt". Simple huh ? Mmm..I just tried to find the original source of this thread, but I cannot see it. What was the problem, you cannot reboot ? -- Regards Cliff
Cliff Sarginson wrote:
Master Resource Control: run level 6 has been reached. Init: no more processes left in this run level
[snip] The first is a standard message when run-level 6 is reached, probably issued by /sbin/halt. The second is from init, but you shouldn't normally get it.
I wonder whether this is a different manifestation of the common "apm" trouble that lots of people are having? It sounds like it's managed to clean up the processes. It knows it's reached level 6 (so all the scripts have run), init is shrugging its shoulders saying "nothing running any more, just me". What hasn't happened is the trigger to poke the system to restart. I don't know how that happens, but my guess is it's related to the same apm interface that causes a shutdown... and as we know that has problems in 2.4.10. Jack: you said you were using SuSE 7.1. What version of kernel are you using? Cheers, -nick
participants (4)
-
Cliff Sarginson -
Jack Reilly -
Karol Pietrzak -
Nick Battle