[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#457044: marked as done (My box doesn't reboot after each upgrade of linux-image)

Your message dated Wed, 4 Jun 2008 00:17:57 +0200
with message-id <20080603221757.GD17007@stro.at>
and subject line Re: My box doesn't reboot after each upgrade of linux-image
has caused the Debian Bug report #457044,
regarding My box doesn't reboot after each upgrade of linux-image
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
457044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457044
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-4-686
Version: linux-image-2.6.18-4-686 2.6.18.dfsg.1-12etch2
Severity: critical
Justification: breaks the whole system

This morning, as usual I did :
apt-get update
apt-get upgrade

today, there was a security update on linux-image-2.6.18-4-686
I followed the given instructions : 
>You are attempting to install a kernel version that is the same as the version you are currently running (version 2.6.18-4-686). 
>The modules list is quite likely to have been changed, and the modules dependency file /lib/modules/2.6.18-4-686/modules.dep needs to be re-built. 
>It can not be built correctly right now, since the module list for the running kernel are likely to be different from the kernel installed. 
>I am creating a new modules.dep file, but that may not be correct. It shall be regenerated correctly at next reboot.                                                                                               ?
>
>I repeat: you have to reboot in order for the modules file to be created correctly. Until you reboot, it may be impossible to load some modules. 
> Reboot as soon as this install is finished (Do not reboot right now, since you may not be able to boot back up until installation is over, but boot immediately after). 
>I can not stress that too much. You need to reboot soon.

So I rebooted my machine (a distant one)
And then... nothing else. My production server never came up until now.
I asked to my hosting provider an electrical reboot as I had no way to act, but the machine didn't boot.
As it's a distant server, I can't tell you what error messages it can show.

The only thing I can provide is the listing of the session from the apt-get upgrade command to the reboot command
I'll send it in a next post
Of course, I'm not sending this report for the concerned server, as at the moment it's dead, but from a local test box with a very similar configuration

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 
Locale: LANG=fr_FR.iso885915@euro, LC_CTYPE=fr_FR.iso885915@euro (charmap=ISO-8859-15) (ignored: LC_ALL set to fr_FR.iso885915@euro)
Shell: /bin/sh linked to /bin/bash

-- 
Ce message a été vérifié par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a été trouvé.
For all your IT requirements visit: http://www.transtec.co.uk

--- End Message ---
--- Begin Message --- 
closing as real boot error didn't come up.

most probably a missing lilo run.
using lilo is masochistic, grub is the default since some time.

all the best.

-- 
maks

--- End Message ---
Reply to: