On Fri, 2013-05-24 at 06:06 +0200, nobswolf wrote: > Am 21.05.2013 02:54, schrieb Ben Hutchings: > > > > A kernel installation should run update-grub anyway, so running > > that only 'solves the problem' until the next security update that > > doesn't get properly installed. > > For some reason in file /etc/kernel-img.conf the entry do_bootloader > was set to "no". I guess this was set by the initial installation as I > can not remember having fiddled with such settings.
This was actually the correct setting for a system using GRUB, and is now ignored. All boot loaders are updated by scripts installed under /etc/kernel. > > Have you moved the /boot partition on this system in the last year > > or so? (The kernel you were running, Debian version 2.6.32-41, > > dates from January 2012.) > > No. The harddisks and the partitions have not changed since the > installation. Do you remember which release you originally installed? > > Assuming you're using GRUB 2, what does 'debsums -a grub-pc' say? > > Lots of lines, all ending with OK: > > http://pastebin.com/7RmqPBwa Do you have a separate /boot partition, and is there a /boot/boot/grub directory? Ben. -- Ben Hutchings friends: People who know you well, but like you anyway.
signature.asc
Description: This is a digitally signed message part
