LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   'respawning too fast:' bootup dies.... (https://www.linuxquestions.org/questions/linux-software-2/respawning-too-fast-bootup-dies-4103/)

jwf593 07-10-2001 12:00 AM

'respawning too fast:' bootup dies....
 
Hope someone can help this Redhat newbie...

I've been running Redhat 7.0 for a couple of months. For a
newbie I've gotten quite a bit done, got it online via DSL,
managed to share that DSL with my WIN 2000 box. But now,
I am stuck again.

Just got done 'upgrading' my c libs via the RedHat Network
and now can't boot.

I get pretty much the same thing booting either the 2.17
or 2.16 kernel...

INIT: version 2.78 booting
INIT: Entering runlevel: 3
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: Id "2" respawning too fast: disabled for 5 minutes
INIT: Id "3" respawning too fast: disabled for 5 minutes
INIT: ........... and so it goes.



The 2.17 kernel gives me a bunch of 'cannot execute
/sbin/mingetty' in between the 'respawning' errors,
but still ends the same way... no boot.



I assume I have to boot from a floppy and edit something,
but what, I have no idea.

Thanks for any help,

Jeff

jharris 07-10-2001 03:18 AM

It sounds like /sbin/mingetty is broken, yet as init's job is to respawn the getty when it dies its just going around in a few quick loop, hence the 'respawning too fast' message. Booting from a straight forward boot disk won't help as it will bring the system up and then use the normal file systems from you hard disk(s) and hit the same proble with init/mingetty.

What you want to do is boot from something like a demo CD (there was a link recently on the forum, I think it mentioned 'demolinux' or something) so that the system comes up without touching the hard disks (it'll use filesystems on the CD). Once the system is up and you're logged on then you can mount your existing partitions somewhere (if its /dev/hdb for your root file system then you do a mkdir someDir; mount /dev/hdb /someDir) and have a look at /someDir/sbin/mingetty to check if its there, and probably copy over it with a known good version.

However if it broke after you upgraded your C libs then you might have something a little more serious to sort out. The version of mingetty you have might not work with the new C libs, so you may need to get find a version of mingetty that works with the new ones. Either that of the libs you've installed are broken, in which case I think you'll need to do the same procedure as above (mounting from a demo CD) and replace your C libs with know good versions.

If you post exactly what upgrade you did (versions etc) then someone on the forum may have done the same upgrade in the past and be able to sort you out.

Not a nice one to fix really :(

Cheers, good luck

Jamie...

linuxcool 07-10-2001 04:48 PM

Go here and use the rescue mode to enter into linux that doesn't use your root partition. That way your inittab file and any other startup files won't be run. You can then mount your root partition and try to find out what's wrong.


All times are GMT -5. The time now is 09:24 AM.