Hi.
On Tue, Oct 06, 2015 at 02:03:37PM +0100, Tony van der Hoff wrote:
> >>>
> >>> As long as "uname -v" output is consistent with "apt-cache policy
> >>> linux-image-3.2.0-4-amd64" output there's nothing to worry about IMO.
> >>>
> >>> They stopped to change kernel version (i.e. 3.2.0-4) as of Squeeze IIRC,
> >>> "because our updates do no change kernel ABI". Since then the full
> >>> kernel version ("uname -v") became the only criteria one should check.
> >>> As a side note - now we see how stable abovementioned ABI really is.
> >>>
> >>
> >> Well, even after a night's sleep, I'm getting increasingly confused here.
> >>
> >> According to synaptic, I have selected the metapackage
> >> linux-image-amd-64, which depends on linux-image-3.2.0-4-amd64, the
> >> installed version of which is 3.2.68-1+deb7u4.
> >>
> >> According to uname -v, I am running #1 SMP Debian 3.2.57-3+deb7u2.
> >>
> >> So, that appears to mean I'm running an out-of-date kernel on this box.
> >> As I understand you, that's probably because the boot loader (grub) has
> >> become corrupt. I've never touched it, primarily because I don't
> >> understand it.
> >>
> >> But how do I fix it now?
> >
> > First, ensure that you're using grub.
> >
>
> Thanks for your help, Reco,
>
> OK, when I boot, I get a "Welcome to Grub" screen. Various kernel
> options, but the default is 3.2.0-4-amd64
So, grub locates a single kernel. It means nothing by itself.
> > Something like 'file -sL /dev/sda' should help here. It says "GRand
> > Unified Bootloader" for me (along with other things, of course).
>
> No... root@tony-lx:~# file -sL /dev/sda
> /dev/sda: sticky x86 boot sector; partition 1: ID=0x5, starthead 32,
> startsector 2046, 976769026 sectors, code offset 0x63
Maybe wheezy's file is unable to display grub entry, or maybe it's
something else.
>
> > While you're at it, check /boot/vmlinuz-3.2.0-4-amd64 with file too.
> >
> root@tony-lx:~# file -sL /boot/vmlinuz-3.2.0-4-amd64
> /boot/vmlinuz-3.2.0-4-amd64: Linux kernel x86 boot executable bzImage,
> version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) #1 SMP Debian 3.,
> RO-rootFS, swap_dev 0x2, Normal VGA
Seems ok so far.
> > Second, check /boot/grub/grub.cfg *and* /boot/grub/menu.lst to determine
> > what are you really booting by default.
> >
> I have no /boot/grub/menu.lst
>
> in grub.cfg, I think this is the relevant part:
>
> ### BEGIN /etc/grub.d/10_linux ###
> menuentry 'Debian GNU/Linux, with Linux 3.2.0-4-amd64' --class debian
> --class gnu-linux --class gnu --class os {
> load_video
> insmod gzio
> insmod raid
> insmod mdraid1x
This. How many disks does your system contain? Are you using RAID1? Can
RAID mirrors be out of sync?
> > Last, check /boot for anything off such as extra kernels or initrds.
> >
>
> Nothing untoward, I think:
>
> root@tony-lx:~# ls -l /boot
> total 16788
> -rw-r--r-- 1 root root 129281 Sep 20 17:40 config-3.2.0-4-amd64
> drwxr-xr-x 3 root root 8192 Oct 6 12:09 grub
> -rw-r--r-- 1 root root 12012066 Sep 22 08:52 initrd.img-3.2.0-4-amd64
> drwxr-xr-x 2 root root 49152 Dec 22 2011 lost+found
> -rw-r--r-- 1 root root 2114662 Sep 20 17:40 System.map-3.2.0-4-amd64
> -rw-r--r-- 1 root root 2842592 Sep 20 17:33 vmlinuz-3.2.0-4-amd64
Comparing vmlinuz-3.2.0-4-amd64 mtime and size with wheezy's deb I
conclude that you have kernel version 3.2.68-1+deb7u4 there.
Hence, grub apparently finds a kernel and initrd elsewhere.
I propose an experiment.
1) Remove "insmod mdraid1x" from grub.cfg. By using any text editor, *do
not* run update-grub.
2) Reboot.
3) While in grub, press 'e' while the default boot entry is selected.
4) Check whenever boot entry still contains "insmod mdraid1x".
5) Boot (Ctrl+x).
6) Run "uname -v".
Reco
