Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#708965: grub-config was needed
5 views
Skip to first unread message
nobswolf
May 20, 2013, 3:20:02 AM5/20/13
to
Although this problem is not kernel related I leave the solution here
for completeness:
For some reason a manual update of GRUB was needed, so ...
update-grub
grub-install ...
... solved the problem.
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
for completeness:
For some reason a manual update of GRUB was needed, so ...
update-grub
grub-install ...
... solved the problem.
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ben Hutchings
May 20, 2013, 9:00:02 PM5/20/13
to
On Mon, 2013-05-20 at 09:12 +0200, nobswolf wrote:
> Although this problem is not kernel related I leave the solution here
> for completeness:
>
> For some reason a manual update of GRUB was needed, so ...
>
> update-grub
> grub-install ...
>
> ... solved the problem.
A kernel installation should run update-grub anyway, so running that
> Although this problem is not kernel related I leave the solution here
> for completeness:
>
> For some reason a manual update of GRUB was needed, so ...
>
> update-grub
> grub-install ...
>
> ... solved the problem.
only 'solves the problem' until the next security update that doesn't
get properly installed.
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.)
Assuming you're using GRUB 2, what does 'debsums -a grub-pc' say?
Ben.
--
Ben Hutchings
friends: People who know you well, but like you anyway.
nobswolf
May 24, 2013, 12:10:02 AM5/24/13
to
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
>
> 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.
was set to "no". I guess this was set by the initial installation as I
can not remember having fiddled with such settings.
> 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.)
installation.
> Assuming you're using GRUB 2, what does 'debsums -a grub-pc' say?
http://pastebin.com/7RmqPBwa
nobs
Ben Hutchings
May 24, 2013, 8:10:02 AM5/24/13
to
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
> 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.
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.
> > Assuming you're using GRUB 2, what does 'debsums -a grub-pc' say?
>
> Lots of lines, all ending with OK:
>
> http://pastebin.com/7RmqPBwa
directory?
nobswolf
May 24, 2013, 11:00:03 AM5/24/13
to
Am 24.05.2013 14:02, schrieb Ben Hutchings:
> Do you remember which release you originally installed?
No idea by myself, but:
> Do you remember which release you originally installed?
root@okami:~# cat /var/log/installer/lsb-release
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="6.0 (squeeze) - installer build 20110106+squeeze4"
X_INSTALLATION_MEDIUM=cdrom
> Do you have a separate /boot partition, and is there a /boot/boot/grub
> directory?
no /boot/boot/grub but /boot/grub :
root@okami:/boot# ls -l
insgesamt 14296
-rw-r--r-- 1 root root 106193 10. Mai 14:09 config-2.6.32-5-amd64
drwxr-xr-x 3 root root 8192 20. Mai 08:49 grub
-rw-r--r-- 1 root root 9957187 19. Mai 23:11 initrd.img-2.6.32-5-amd64
-rw-r--r-- 1 root root 124648 21. Mär 2010 memtest86.bin
-rw-r--r-- 1 root root 165084 21. Okt 2010 memtest86+.bin
-rw-r--r-- 1 root root 167264 21. Okt 2010 memtest86+_multiboot.bin
-rw-r--r-- 1 root root 1667938 10. Mai 14:09 System.map-2.6.32-5-amd64
-rw-r--r-- 1 root root 2426848 10. Mai 13:57 vmlinuz-2.6.32-5-amd64
Ben Hutchings
May 25, 2013, 10:10:02 PM5/25/13
to
Well, I don't understand how this went wrong and it's probably fixed
now.
Next time you update the kernel (for a security update or point
release), please check after rebooting that the new version is actually
running (use 'cat /proc/version'). If the same thing happened, then
open a new bug report against grub-pc.
Ben.
--
Ben Hutchings
Computers are not intelligent. They only think they are.
now.
Next time you update the kernel (for a security update or point
release), please check after rebooting that the new version is actually
running (use 'cat /proc/version'). If the same thing happened, then
open a new bug report against grub-pc.
Ben.
--
Ben Hutchings
Computers are not intelligent. They only think they are.
0 new messages