forum.excito.org

After a reboot, my Bubba Two with mixed upgrades (claire and upstream debian), fails to boot.
A rescue boot from USB lets me inspect the logs, which contain the following suspicious bits:

Jan 1 01:00:32 menace ifplugd(eth0)[2281]: ifplugd 0.28 initializing.
Jan 1 01:00:33 menace ifplugd(eth0)[2281]: Using interface eth0
Jan 1 01:00:35 menace ifplugd(eth0)[2281]: Initialization complete, link beat not detected.
Jan 1 01:00:35 menace ifplugd(eth0)[2281]: Could not open /dev/tty, cannot beep.
Jan 1 01:00:35 menace ifplugd(eth1)[2333]: ifplugd 0.28 initializing.
Jan 1 01:00:36 menace ifplugd(eth1)[2333]: Using interface eth1
Jan 1 01:00:39 menace ifplugd(eth1)[2333]: Initialization complete, link beat not detected.
Jan 1 01:00:39 menace ifplugd(eth1)[2333]: Could not open /dev/tty, cannot beep.

Now I have no idea why ifplugd cannot detect a link beat: the rescue system works fine (although that doesn't seem to have an ifplugd).
Should I be looking at ifplugd options, missing kernel modules, missing support programs or others?

Some system info:

Jan 1 01:00:21 menace kernel: Linux version 2.6.30.1 (tor@sid) (gcc version 4.3.2 (GCC) ) #1 Thu Jul 9 13:33:23 CEST 2009

ifplugd-0.28-2.3ex1

It's mostly probable that you have installed an non-functional kernel (in claire, they can easily be broken, due to the unstable nature). Theoretically to fix this would be to use an rescue stick, and from there chroot into the system and either upgrade bubba-kernel and bubba-modules to latest version (which can be manually downloaded from our archives) or downgrade same packages to latest found in marielle.

carl wrote:It's mostly probable that you have installed an non-functional kernel (in claire, they can easily be broken, due to the unstable nature).

Ok, I was almost at the point of accepting that conclusion. The rescue system's dmesg shows messages detecting the network device(s), and the installed kernel's dmesg doesn't.
I'll try a different kernel.
Are you interested in more details if I get it to work again?

zweije wrote:I'll try a different kernel.

Well, an update to the latest claire kernel didn't work; will have to go back to marielle. Unfortunately I'm not there to start the rescue system, so it'll have to wait until tonight. More later.
Does the kernel normally use a console on the serial port (over usb)?

zweije wrote:Well, an update to the latest claire kernel didn't work; will have to go back to marielle.

I was too quick to draw my conclusion. The system just needed a little longer to reboot and is now up and running. Perfect!
Thanks for your help.
By the way, I'm now seeing the network device detection message in dmesg again which was in the rescue system's dmesg but not in the broken kernel's one, so that was probably indeed the problem.

zweije wrote:

zweije wrote:Well, an update to the latest claire kernel didn't work; will have to go back to marielle.

I was too quick to draw my conclusion. The system just needed a little longer to reboot and is now up and running. Perfect!
Thanks for your help.
By the way, I'm now seeing the network device detection message in dmesg again which was in the rescue system's dmesg but not in the broken kernel's one, so that was probably indeed the problem.

Remember that claire is our development repository, and thus packages has an high probability to be broken.