Bug#457044: Same problem with the new security update to linux-image-2.6.22-3-686
Hello,
this morning, I had exactly the same problem while installing
linux-image-2.6.22-3-686 (2.6.22-6.lenny1 Debian-Security:None/testing)
The box didn't reboot.
The last time it happened, this is how our distant hostmaster managed to correcte the problem :
>The technician had to boot the server using a live CD Linux.
>Then he made a dpkg-reconfigures on the kernel package, this made it possible to rebuild the initrd and to
>repair Lilo.
Reading the apt-get session I had before the reboot, I think the problem could be here :
? The kernel version running is the same as the one being installed ?
? ?
? You are attempting to install a kernel version that is the same as the version you are currently running (version 2.6.22-3-686). The modules list is quite ?
? likely to have been changed, and the modules dependency file /lib/modules/2.6.22-3-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
And here :
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.22-6 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.22-6 was configured last, according to dpkg)
It seems that in the case of the installation of a kernel with the same number, dpkg doesn't verify that initrd symbolic
links really exists just because it consider that they "should" be correct in the case of an update. But if for some
reason those links were broken they are not recreated and lilo isn't updated
Reply to: