12 Feb
2020
12 Feb
'20
3:49 p.m.
Thanks Andy!
That's absolutely ancient and I am amazed that
your system works at
all.
Any ideas how you have managed to end up running a Debian 6
(squeeze) era kernel on a Debian 10 user land?
I have no idea! I got this server in 2013 and have downloaded updates
regularly, if less consistently. I might have overlooked something. I
know I haven't been paying enough attention to this server, which is
something I decided to change, but I don't think I've had issues
upgrading since 2014.
That kernel went end of life for security updates in
2014 by the
way!
That's... embarrassing given that I work in security. :-)
(I don't sell my services as a Linux server expert. But still, it's
bad. I should have known better.)
Are you sure you're actually running Debian
stable, i.e. you have
previously done an "apt-get update" and then an "apt-get
dist-upgrade" which all completed okay in the past?
I think so, but I didn't write that down, so I can't be 100% sure...
What kernels do you actually have installed right
now?
$ dpkg -l | grep linux-image
ii linux-image-2.6-686-bigmem 2.6.32+29
i386 Linux 2.6 for PCs with 4GB+ RAM (meta-package)
rc linux-image-2.6.32-3-686-bigmem 2.6.32-9
i386 Linux 2.6.32 for PCs with 4GB+ RAM
ii linux-image-2.6.32-5-686-bigmem 2.6.32-48squeeze19
i386 Linux 2.6.32 for PCs with 4GB+ RAM
ii linux-image-686-bigmem 2.6.32+29
i386 Linux for PCs with 4GB+ RAM (meta-package)
What is the output of:
$ ls -la /boot/
total 27652
drwxr-xr-x 3 root root 4096 Feb 3 07:53 .
drwxr-xr-x 22 root adm 4096 Jan 16 14:09 ..
-rw-r--r-- 1 root root 1328749 Feb 5 2016 System.map-2.6.32-5-686-bigmem
-rw-r--r-- 1 root root 111663 Feb 5 2016 config-2.6.32-5-686-bigmem
drwxr-xr-x 2 root root 4096 Sep 26 2016 grub
-rw-r--r-- 1 root root 12217326 Feb 3 07:53 initrd.img-2.6.32-5-686-bigmem
-rw-r--r-- 1 root root 12217371 Feb 3 07:51
initrd.img-2.6.32-5-686-bigmem.dpkg-bak
-rw-r--r-- 1 root root 2373728 Feb 5 2016 vmlinuz-2.6.32-5-686-bigmem
What happens when you update your grub config:
$ sudo update-grub
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.32-5-686-bigmem
Updating /boot/grub/menu.lst ... done
I would really hope that it is just a case of there
being an old
kernel hanging around that your boot loader keeps selecting but
honestly this is so weird that I would not trust your system to come
back up correctly if you rebooted it right now.
It's been rebooted several times, most recently on 31 October. Never any issues.
Martijn