On Friday 06 August 2021 05:59:09 pm dep wrote:
said Michael:
| No real reason to keep really old boot images, the last working one
| definitely keep though. Do a full tarball of /boot and then try this:
|
| # ls -al --color=always /boot # Will show if you have screwy stragglers
| not shown in next step.
ls -al --color=always /boot
total 202732
drwxr-xr-x 5 root root 20480 Aug 6 17:15 .
drwxr-xr-x 28 root root 4096 Aug 6 14:22 ..
-rw-r--r-- 1 root root 1166936 Jul 20 2017 abi-3.13.0-126-generic
-rw-r--r-- 1 root root 1168650 May 2 2018 abi-3.13.0-147-generic
-rw-r--r-- 1 root root 1251054 May 2 2018 abi-4.4.0-124-generic
-rw-r--r-- 1 root root 166050 Jul 20 2017 config-3.13.0-126-generic
-rw-r--r-- 1 root root 166136 May 2 2018 config-3.13.0-147-generic
-rw-r--r-- 1 root root 190654 May 2 2018 config-4.4.0-124-generic
-rw-r--r-- 1 root root 237851 Jul 9 11:49 config-5.4.0-80-generic
drwxr-xr-x 19 root root 4096 Dec 31 1969 efi
drwxr-xr-x 3 root root 4096 May 15 2018 extlinux
drwxr-xr-x 7 root root 12288 Aug 6 17:37 grub
lrwxrwxrwx 1 root root 27 Jul 21 10:41 initrd.img ->
initrd.img-5.4.0-80-generic
-rw-r--r-- 1 root root 20438488 Jun 30 13:02 initrd.img-3.13.0-126-generic
-rw-r--r-- 1 root root 20438510 Jun 30 13:02 initrd.img-3.13.0-147-generic
-rw-r--r-- 1 root root 20470196 Jun 30 13:02 initrd.img-4.4.0-124-generic
-rw-r--r-- 1 root root 95055861 Jul 23 06:45 initrd.img-5.4.0-80-generic
lrwxrwxrwx 1 root root 28 Aug 6 17:15 initrd.img.old ->
initrd.img-4.4.0-124-generic
-rw-r--r-- 1 root root 182704 Aug 18 2020 memtest86+.bin
-rw-r--r-- 1 root root 184380 Aug 18 2020 memtest86+.elf
-rw-r--r-- 1 root root 184884 Aug 18 2020 memtest86+_multiboot.bin
-rw-r--r-- 1 root root 691 May 2 2018 retpoline-3.13.0-147-generic
-rw-r--r-- 1 root root 255 May 2 2018 retpoline-4.4.0-124-generic
-rw------- 1 root root 3400307 Jul 20 2017 System.map-3.13.0-126-generic
-rw------- 1 root root 3413068 May 2 2018 System.map-3.13.0-147-generic
-rw------- 1 root root 3898100 May 2 2018 System.map-4.4.0-124-generic
-rw------- 1 root root 4751959 Jul 9 11:49 System.map-5.4.0-80-generic
lrwxrwxrwx 1 root root 24 Jul 21 10:41 vmlinuz ->
vmlinuz-5.4.0-80-generic
-rw------- 1 root root 5851792 Jul 20 2017 vmlinuz-3.13.0-126-generic
-rw------- 1 root root 5887024 May 2 2018 vmlinuz-3.13.0-147-generic
-rw------- 1 root root 7143952 May 2 2018 vmlinuz-4.4.0-124-generic
-rw------- 1 root root 11768064 Jul 9 12:09 vmlinuz-5.4.0-80-generic
lrwxrwxrwx 1 root root 25 Aug 6 17:15 vmlinuz.old ->
vmlinuz-4.4.0-124-generic
| # dpkg -l 'linux-image-*' | grep '^ii'
dpkg -l 'linux-image-*' | grep '^ii'
ii linux-image-5.4.0-80-generic 5.4.0-80.90 amd64
Signed kernel image generic
ii linux-image-generic 5.4.0.80.84 amd64
Generic Linux kernel image
See the problem? Three versions that the package manager doesn't see.
Internet serches render nothing I haven't tried. dpkg shows only the
current kernel. The other three are there, and based on their numbering I
have to assume that they came in as .deb packages. How they dropped off
the radar I do not know
Okay, time for Slávek, or someone else with deeper knowledge to chime in. It
might be as simple as just deleting the files, but IDK :(
Did you run the dpkg --configure -a ? There's a small possibility it'll
re-attach the older cruft so you can remove it through the traditional
apt-get purge. Again IDK if that’ll work, and I wouldn’t myself* try it
until Slávek gives the go ahead...
Best,
Michael
* Well if it was a test box or something sure, but not my main daily driver.