[Voyage-linux] Reboot failure after apt-get upgrade - unstable

[Beat Meier]

Edwin Whitelaw wrote:

> I've just unfortunately duplicated something that I thought was simply a
goof on my part but may be an apt-get/package problem.
>
> I've got my apt sources file set to us.voyage.hk for the unstable tree so
I could get the latest kernel and madwifi-ng stuff.  Everything upgrades
fine when running
>
> apt-get dist-upgrade
>
> and the system then reboots to the new kernel fine.  However, after
loading a few other things (that should really have nothing to do with this
problem) such as rsync and quagga, the unit fails on reboot. with
>
> INIT: Id "T0" respawning too fast: disabled for 5 minutes
> INIT: no more processes left in this runlevel
> INIT: Id "T0" respawning too fast: disabled for 5 minutes
> .
> .
> .
> etc.
>
>
Hello Edwin

What do you mean with reboot fails. You cannot anymore login of reboot
really
does not work anymore i.e. you must do a power-off-on cycle?

It seems that T0 entry (I guess /sbin/getty) dies ...
I think this packages was updated and dumps now or your devcies was changed
by the upgrade so ttyS0 is no more the same
(if this is used in entry T0).  But how did you get the console log? Remote
logger?
BTW: getty is in package util-linux  and I have version  2.12p-4. Don't know
which version has new voyage versions.
Of course if you can login via serial console (see below) getty does not
dump ...

> I've made no changes to inittab from the initial load through the
upgrades.  I do have the serial speed set to 38400 but that's never been a
problem until now.
>
> Any comments?  How does one interrupt the boot on a WRAP to boot single
user, BTW?

If you use serial console press tab or cntrl  and you should have in
/etc/lilo.conf something like
prompt
timeout=50

If you don't use serial console (or want use this way) lilo -R
<cmdline>;reboot
In your case it's a little bit difficult because reboot doesn't work and of
course
in sinlge user the network services are not up so login with ssh is
difficult. What you can do if need this is
configure that sshd comes up even in single user ...

BTW: Is seems that you have a problem with /var that it is not writeable ...
This is not good for ssh etc.

What about
Configuring network interfaces.../etc/network/interfaces:14: duplicate
interface
log?

Greetings

Beat

-- 
Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%!
Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer