3 Jun
2020
3 Jun
'20
1:26 p.m.
HI All,
I was attempting to free up some space, (/boot is over full) and I fear
I have damaged my Ubuntu 18/04 installation.
When I run
sudo apt-get update && sudo apt-get upgrade
the following errors are flagged up in the middle on the
results.
WARNING: missing /lib/modules/4.15.0-101-generic
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/4.15.0-101-generic:
No such file or directory
depmod: FATAL: could not search modules: No such file or directory
depmod: WARNING: could not open
/var/tmp/mkinitramfs_vr26f3/lib/modules/4.15.0-101-generic/modules.order:
No such file or directory
depmod: WARNING: could not open
/var/tmp/mkinitramfs_vr26f3/lib/modules/4.15.0-101-generic/modules.builtin:
No such file or directory
The system does boot, and appears to serve its web sites properly.
If it helps uname -r gives
4.15.0-88-generic
There are no ubuntu updates to apply.
How can I recover? I feel right out of my depth!
Thanks
Ian
--
Ian Hobson
Tel (+351) 910 418 473
--
This email has been checked for viruses by AVG.
https://www.avg.com
3 Jun
3 Jun
1:38 p.m.
Hello,
On Wed, Jun 03, 2020 at 02:26:28PM +0100, Ian Hobson wrote:
I was attempting to free up some space, (/boot is over
full) and I fear I
have damaged my Ubuntu 18/04 installation.
So what did you actually do? .bash_history should have it.
When I run
sudo apt-get update && sudo apt-get upgrade
the following errors are flagged up in the middle on the
results.
WARNING: missing /lib/modules/4.15.0-101-generic
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/4.15.0-101-generic: No
such file or directory
[…]
The system does boot
[…]
uname -r gives
4.15.0-88-generic
But presumably kernel 4.15.0-101 is listed at the top of the grub
menu and doesn't work, then it actually boots with 4.15.0-88?
How can I recover? I feel right out of my depth!
I would like to know more about what was done before giving firm
advice but it seems like you might have deleted
/lib/modules/4.15.0-101-generic when linux-image-4.15.0-101 is the
kernel you are supposed to boot. If so then forcing reinstall of the
package should put the files back.
My general rule when clearing out unused kernel pages is to keep
both the currently-running kernel and the one it's supposed to run.
So in your case that's linux-image-4.15.0-88 and -101.
If this is a result of deleting things from /lib, I wouldn't feel
too bad. I once put /lib on an LVM logical volume in order to free
up space in /. Of course, the kernel modules required to load a file
system off of LVM are in /lib…
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
2:09 p.m.
On 03/06/2020 14:41, Andy Smith wrote:
On Wed, Jun 03, 2020 at 01:38:48PM +0000, Andy Smith
wrote:
Hi Andy,
Thanks for your input. I ran
dpkg -l linux-{image,headers}-"[0-9]*" | awk '/^ii/{ print $2}' | grep
-v -e `uname -r | cut -f1,2 -d"-"` | grep -e '[0-9]' | xargs sudo
apt-get -y purge
And manually removed the files that this complained it could not delete.
Was a bit surprised to see modules for -101 in that list.
Can't pick them up from .bash_history because I was inside mc.
My /boot dir is still full of stuff, most of which I suspect is surplus
to requirements.
ian@hobsoni:/boot$ dir -ls
total 510312
216 -rw-r--r-- 1 root root 217495 Feb 11 18:53 config-4.15.0-88-generic
4 drwxr-xr-x 5 root root 4096 Mar 27 20:29 grub
11384 -rw-r--r-- 1 root root 11655011 Jun 3 14:13
initrd.img-4.15.0-101-generic
14308 -rw-r--r-- 1 root root 14649463 May 8 11:22
initrd.img-4.15.0-45-generic
14308 -rw-r--r-- 1 root root 14649437 May 8 11:21
initrd.img-4.15.0-46-generic
26344 -rw-r--r-- 1 root root 26971904 May 8 11:21
initrd.img-4.15.0-47-generic
14308 -rw-r--r-- 1 root root 14649219 May 8 11:21
initrd.img-4.15.0-48-generic
26344 -rw-r--r-- 1 root root 26970567 May 8 11:20
initrd.img-4.15.0-50-generic
14308 -rw-r--r-- 1 root root 14649557 May 8 11:20
initrd.img-4.15.0-52-generic
26344 -rw-r--r-- 1 root root 26971866 May 8 11:20
initrd.img-4.15.0-54-generic
14308 -rw-r--r-- 1 root root 14649448 May 8 11:19
initrd.img-4.15.0-58-generic
14308 -rw-r--r-- 1 root root 14649467 May 8 11:19
initrd.img-4.15.0-60-generic
14308 -rw-r--r-- 1 root root 14649446 May 8 11:19
initrd.img-4.15.0-62-generic
14308 -rw-r--r-- 1 root root 14649425 May 8 11:19
initrd.img-4.15.0-64-generic
14308 -rw-r--r-- 1 root root 14649448 May 8 11:19
initrd.img-4.15.0-65-generic
14308 -rw-r--r-- 1 root root 14649425 May 8 11:18
initrd.img-4.15.0-66-generic
26360 -rw-r--r-- 1 root root 26988510 May 8 11:18
initrd.img-4.15.0-70-generic
14312 -rw-r--r-- 1 root root 14649452 May 8 11:18
initrd.img-4.15.0-72-generic
26412 -rw-r--r-- 1 root root 27041533 May 8 11:18
initrd.img-4.15.0-74-generic
14308 -rw-r--r-- 1 root root 14649542 May 8 11:17
initrd.img-4.15.0-76-generic
26416 -rw-r--r-- 1 root root 27045245 May 8 11:17
initrd.img-4.15.0-88-generic
14308 -rw-r--r-- 1 root root 14649199 May 8 11:17
initrd.img-4.15.0-91-generic
56856 -rw-r--r-- 1 root root 58212492 May 8 11:17
initrd.img-4.15.0-96-generic
56852 -rw-r--r-- 1 root root 58209031 May 23 16:18
initrd.img-4.15.0-99-generic
14312 -rw-r--r-- 1 root root 14649473 May 8 11:22
initrd.img-4.4.0-112-generic
14308 -rw-r--r-- 1 root root 14649457 May 8 11:22
initrd.img-4.4.0-116-generic
3976 -rw------- 1 root root 4069510 Feb 11 18:53
System.map-4.15.0-88-generic
8176 -rw------- 1 root root 8371864 Feb 11 18:57
vmlinuz-4.15.0-88-generic
ian@hobsoni:/boot$
Regards
Ian
--
Ian Hobson
Tel (+351) 910 418 473
--
This email has been checked for viruses by AVG.
https://www.avg.com
My general rule when clearing out unused kernel
pages is to keep
^^images
> both the currently-running kernel and the one it's supposed to run.
> So in your case that's linux-image-4.15.0-88 and -101.
>
2:44 p.m.
Hello,
On Wed, Jun 03, 2020 at 03:09:10PM +0100, Ian Hobson wrote:
Thanks for your input. I ran
dpkg -l linux-{image,headers}-"[0-9]*" | awk '/^ii/{ print $2}' | grep
-v -e
`uname -r | cut -f1,2 -d"-"` | grep -e '[0-9]' | xargs sudo apt-get -y
purge
And manually removed the files that this complained it could not delete. Was
a bit surprised to see modules for -101 in that list.
Why? The above seems like it would purge -101 if you are currently
running -88. Were you running -88 at the time? The use of -y also
doesn't give any chance for apt-get to say it's a bad idea, not that
I'm sure it does in this instance…
Can't pick them up from .bash_history because I
was inside mc.
Probably something in the dpkg or apt logs.
So does:
$ sudo apt --reinstall install linux-image-4.15.0-101-generic
stop your update-grub complaining and allow you to boot into -101?
My /boot dir is still full of stuff, most of which I
suspect is surplus to
requirements.
Your above command looks like it only purges packages which are
currently installed, so if there are linux-image packages which are
merely removed it won't have purged them. A lot of this stuff could
perhaps be removed by purging them.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Please consider the environment before reading this e-mail.
— John Levine
3:23 p.m.
Hi Andy,
On 03/06/2020 15:44, Andy Smith wrote:
So does:
$ sudo apt --reinstall install linux-image-4.15.0-101-generic
stop your update-grub complaining and allow you to boot into -101?
It appears to,
yes.
Now should I delete the stuff in /boot that is neither -101 nor -88?
And the matching directories in /lib/modules?
Regards
Ian
--
Ian Hobson
Tel (+351) 910 418 473
--
This email has been checked for viruses by AVG.
https://www.avg.com
3:38 p.m.
Hello,
On Wed, Jun 03, 2020 at 04:23:14PM +0100, Ian Hobson wrote:
Now should I delete the stuff in /boot that is neither
-101 nor -88?
And the matching directories in /lib/modules?
I would try purge for the respective packages. Much less error-prone
than rm.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
4 Jun
4 Jun
7:30 a.m.
On Wed, 3 Jun 2020 15:38:00 +0000
Andy Smith (andy(a)bitfolk.com) said:
I would try purge for the respective packages. Much less error-prone
than rm.
On a tangentially related note, I'm finding myself getting very fond of
Debian's "debfoster". It keeps a list of "wanted" packages and,
when
run, will prompt you about any packages that are currently installed,
but not on the "wanted" list or any dependency of packages on that list.
You can then choose to add them to the list or purge the installed
packages and, optionally, their dependencies.
Its "wanted" list lives in /var/lib/debfoster/keepers and is a text
file, so you can edit that freely.
Very reminiscent of the Gentoo "world" file and very helpful in keeping
your system pruned down to stuff you actually need.
It's not perfect, but pretty good.
Cheers,
Alun.
3 Jun
3 Jun
3:24 p.m.
On 03/06/2020 14:41, Andy Smith wrote:
On Wed, Jun 03, 2020 at 01:38:48PM +0000, Andy Smith
wrote:
It has never crossed my mind to remove the image that is currently
running!
I always keep the very first kernel, the current / latest, and the
previous. And usually one or two from a few months back.
There may not be a lot of logic to it but that's what I do.
You should IMO always have a fall-back option. Once upon a time
I had a new kernel that rather bizarrely ran the clock too fast.
This had the effect of totally messing up my time-sheeting for the
day...
@Ian, I had a clear out a while back.
history shows the following
apt-get purge linux-image-4.15.0-74-generic
apt-get purge -y linux-headers-4.15.0-74
apt-get purge -y linux-modules-4.15.0-74-generic
And these to show what was installed:
apt-mark showauto 'linux-image-.*'
apt-mark showmanual 'linux-image-.*'
My general rule when clearing out unused kernel
pages is to keep
^^images
> both the currently-running kernel and the one it's supposed to run.
> So in your case that's linux-image-4.15.0-88 and -101.
1514
days inactive
1515
days old
8 comments
4 participants
participants (4)
-
Alun -
Andy Smith -
Dom Latter -
Ian Hobson