HELP: new baselayout breaks reboot - SOLVED

Message

Moriah · Post by **Moriah** » Mon May 09, 2011 6:45 am

I just did an emerge --sync ; emerge --deep --newuse --update system on an "expendable" machine (I ain't dumb!

) and installed the fancy new baselayout. The box now boots OK, and seems fairly normal after a few minutes of running, but it will no longer reboot!

By "reboot", I meant it will no longer execute the "reboot" command from the root user's command line prompt. It seems to go well up to the point where it says:

Code: Select all

*     Remounting / read only ...

but then it says:

Code: Select all

INIT: no more processes left in this runlevel

and just sits there forever (well, for several minutes anyway). It never finishes the shutdown completely and starts the actual rebooting part of the reboot. I must cycle power to get it to boot again.

This is totally unacceptable, as I administer this and 15 other gentoo machines remotely most of the time. While I do have ibootbar ethernet remotely controlled power strips, so I can cycle power from hundreds of miles away, and I do have an ipeps hardware vnc kvm-over-ip device on the kvm, so I can see the boot console remotely, and interact with it, it is always better if one does not have to cycle power, as strange things can happen, like disk drives not powering up properly, fuses blowing, etc. and I cannot fix these remotely. The president of the company has asked when I will make a little robot to do these things remotely, but she was not really serious.

Is there something I did wrong/ Or are other people having this problem too, but think it is no big deal to just cycle power, or push a reset button?

avx · Post by **avx** » Mon May 09, 2011 6:49 am

You did run etc-update/dispatch-conf, read all the related `eselect news` and acted accordingly? Can't reproduce that here, but maybe that's just because I'm running bl2/openrc for years now...

Moriah · Post by **Moriah** » Mon May 09, 2011 4:47 pm

Yes, did all of that. Its weird, because everything else seems just fine. Maybe it was something else in the update that did it, and not related to the baselayout change at all.

Sysa · Post by **Sysa** » Mon May 09, 2011 4:54 pm

Did you read OpenRC migration Guide?

It mentions not about dispatch-conf only but some changes in rc-update levels, networking etc.

Please read it again, maybe you'll find an answer yourself.

Moriah · Post by **Moriah** » Mon May 09, 2011 10:10 pm

Yes, I read it, and followed it step by step.

I have a bunch of other machines to do this to also, so we will see if a pattern develops, or if this is a onesy.

k01 · Post by **k01** » Tue May 10, 2011 8:20 am

i've the same problem shutting down to, not only reboot. same problem on two different computer, i686 and x86_64 arch, upgraded after stabilization, instead on the notebook i've upgraded just a couple of week before stabilization and all works fine

adriansi7 · Post by **adriansi7** » Tue May 10, 2011 8:28 am

I had the same problem but i have managed to fix it by adding these lines to /etc/inittab :

Code: Select all

16r:6:wait:/sbin/reboot -dk
10s:0:wait:/sbin/halt -dhip

Just add them under 16:6:wait:/sbin/rc reboot

k01 · Post by **k01** » Tue May 10, 2011 12:36 pm

that's worked for me, thanks

dberkholz · Post by **dberkholz** » Tue May 10, 2011 4:17 pm

What version of sysvinit did you hit that problem on? I've already got those lines in my inittab.

Moriah · Post by **Moriah** » Tue May 10, 2011 4:20 pm

I will have to check on all my machines to see if I have those lines in inittab, but where did they come from? I will also check what version on sysvinit I have on each machine. Probably will not appen before tonight though...

dberkholz · Post by **dberkholz** » Tue May 10, 2011 4:46 pm

We've been talking about this on IRC. What we're thinking is that back when inittab was updated in sysvinit 2.86-r11, you might've accidentally picked the old version instead of the new one. It wouldn't have any effect till now, because it's only incompatible with openrc.

Moriah · Post by **Moriah** » Tue May 10, 2011 9:32 pm

Since the pick was chosen by default, as I made no particular choice, but followed the handbook on installation, and took the default updates as they appeared, then who was it that made the wrong choice?

And more to the point now, what do I do to correct it?

dberkholz · Post by **dberkholz** » Tue May 10, 2011 9:46 pm

This wouldn't have been at install time, but some later update to system or world. Anyway..

Try

Code: Select all

emerge -va --noconfmem sysvinit

Then accept any updates to /etc/inittab.

Moriah · Post by **Moriah** » Wed May 11, 2011 2:56 am

Thanks, that did the trick!