[SOLVED] First boot problem: Init Id "3" respawning too fast: disabled for 5 minutes

Zimo · 10-31-2012, 09:10 AM

Hi guys.

I have finished with LFS and at reboot it should work. I can select my LFS system from GRUB ( I reconfigured my old one ). But the boot process stops after a while, and I get:

Quote:

INIT: Id "3" respawning too fast: disabled for 5 minutes
INIT: no more processes left in this runlevel

INIT: Id "4" respawning too fast: disabled for 5 minutes
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: Id "2" respawning too fast: disabled for 5 minutes

After about ten minutes output switchs from , for example, INIT: Id "4".. to INIT: Id "1"..and so on. After half an hour I give up.
I have no possibilities to write any command. I can only reboot the computer and go where I built everything, trying to solve the problem.

But..How? Ideas?

Thanks for answers.

druuna · 10-31-2012, 09:25 AM

This normally indicates an error/typo in your /etc/inittab file.

Use your host or a liveCD to access and rectify it.

Zimo · 10-31-2012, 01:38 PM

This is my inittab:

Quote:

# Begin /etc/inittab
id:3:initdefault:
si::sysinit:/etc/rc.d/init.d/rc S
l0:0:wait:/etc/rc.d/init.d/rc 0
l1:S1:wait:/etc/rc.d/init.d/rc 1
l2:2:wait:/etc/rc.d/init.d/rc 2
l3:3:wait:/etc/rc.d/init.d/rc 3
l4:4:wait:/etc/rc.d/init.d/rc 4
l5:5:wait:/etc/rc.d/init.d/rc 5
l6:6:wait:/etc/rc.d/init.d/rc 6
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
su:S016: once:/sbin/sulogin
1:2345:respawn:/sbin/agetty
2:2345:respawn:/sbin/agetty
3:2345:respawn:/sbin/agetty
4:2345:respawn:/sbin/agetty
5:2345:respawn:/sbin/agetty
6:2345:respawn:/sbin/agetty
--noclear tty1 9600
tty2 9600
tty3 9600
tty4 9600
tty5 9600
tty6 9600
# End /etc/inittab

But it seems to be exatly the same of the book..

druuna · 10-31-2012, 01:45 PM

Don't know which book you are using, but that is wrong.

Assuming you use LFS 7.2, have a look here for the correct one:7.7.1. Configuring Sysvinit

Zimo · 10-31-2012, 02:13 PM

I don't really know. I have 7.2, I copied it from there. However, it's solved. And now everything it's OK! Thanks!