Meaningless Drivel is fun!*
The moose likes Linux / UNIX and the fly likes Linux OS Problem Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Engineering » Linux / UNIX
Bookmark "Linux OS Problem" Watch "Linux OS Problem" New topic
Author

Linux OS Problem

panda mohan
Greenhorn

Joined: Mar 16, 2005
Posts: 4
hi..there
I m facing a serious problem on my Linux Macine.When i on my Machine's power btn it shows that RedHat-Linux and ask me to press Enter(or it will automattically start with in som 8 seconds).
When i press Enter,it starts Like a Matrix Movies numbers and finally it stoped with following Error.....Plz help me.



INT: entering runlevel 3
> >INT ID " 1" respawing too fast: disabled for 5 minutes
> >INT ID " 2" respawing too fast: disabled for 5 minutes
> >INT ID " 3" respawing too fast: disabled for 5 minutes
> >INT ID " 4" respawing too fast: disabled for 5 minutes
> >INT ID " 5" respawing too fast: disabled for 5 minutes
> >INT ID " 6" respawing too fast: disabled for 5 minutes
> >INT: NO MORE PROCESS LEFT

Additionally....i have one more qurey

Can u just guide me....tht how can i take a BKUP from Linux Machine ,if i want to reload the Linux-OS.
Ernest Friedman-Hill
author and iconoclast
Marshal

Joined: Jul 08, 2003
Posts: 24187
    
  34

There's a file /etc/inittab which tells init (the ultimate parent of all processes on a Linux system) what processes to start when the system boots up. The "respawning" error message means that init tried to launch one of these processes and failed. You're seeing it six times, with six different ID numbers (the numbers correspond to the numbers in the inittab) so it's almost certainly the /sbin/mingetty processes that handle terminal logins that are broken.

Why they're broken, I can't say. The executable could be deleted, or moved or renamed, or overwritten; a disk error could have wiped it out; the /etc/inittab could be configured to work with /sbin/mingetty, but mingetty isn't installed; the /dev/ttyXXX files are missing, or have the wrong permissions; there are all kinds of reasons.

Your first order of business is to be able to get on the system again. What I would do would be to boot with the RedHat recovery disk, mount the existing disk in read-write mode, then edit /etc/inittab so that the getty lines look like

1:2345:respawn:/bin/sh
2:2345:respawn:/bin/sh
...

Then when you reboot, you should just get a root prompt, with no login.

From there, you have to figure out why /sbin/mingetty can't launch. Good luck.


[Jess in Action][AskingGoodQuestions]
Stefan Wagner
Ranch Hand

Joined: Jun 02, 2003
Posts: 1923

I agree but like to note:

a) /sbin/getty
is my logincommand and perhaps yours is a third one.

b) if you're booting with lilo, you may add a runlevel, so instead of

linux-2.6

bootoption, you would manually type:

linux-2.6 1

to bootup in runlevel 1, which is often implemented as recovery login, without loginprompt, but bash as loginless login, which would make it more easy to fix things.


http://home.arcor.de/hirnstrom/bewerbung
 
GeeCON Prague 2014
 
subject: Linux OS Problem