[Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
Brian Murray
brian at ubuntu.com
Thu Oct 5 18:31:19 UTC 2017
The verification of this has failed as the fix was incorrect.
Removing linux-image-4.10.0-19-generic (4.10.0-19.21) ...
Examining /etc/kernel/prerm.d.
run-parts: executing /etc/kernel/prerm.d/dkms 4.10.0-19-generic /boot/vmlinuz-4.10.0-19-generic
removed '/boot/initrd.img-4.10.0-19-generic.old-dkms'
dkms: removing: r8168 8.043.02 (4.10.0-19-generic) (x86_64)
-------- Uninstall Beginning --------
Module: r8168
Version: 8.043.02
Kernel: 4.10.0-19-generic (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
r8168.ko:
- Uninstallation
- Deleting from: /lib/modules/4.10.0-19-generic/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod...
Backing up initrd.img-4.10.0-19-generic to /boot/initrd.img-4.10.0-19-generic.old-dkms
Making new initrd.img-4.10.0-19-generic
(If next boot fails, revert to initrd.img-4.10.0-19-generic.old-dkms image)
update-initramfs...
DKMS: uninstall completed.
Examining /etc/kernel/postrm.d .
The .old-dkms file is removed before a new one is created (see the
Backing up bits). So the remove_initrd_backup run needs to be reordered
for after the dkms call.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1515513
Title:
/boot/initrd.img-*.old-dkms files left behind
Status in dkms package in Ubuntu:
Fix Released
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in dkms source package in Xenial:
Fix Committed
Status in initramfs-tools source package in Xenial:
New
Status in dkms source package in Zesty:
Fix Committed
Status in initramfs-tools source package in Zesty:
New
Status in dkms package in Debian:
New
Bug description:
[Impact]
If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel.
[Test Case]
On a system with two old kernels and one new kernel available in -updates:
1) install r8168-dkms
2) install the dkms module for the old kernel e.g. 'sudo dkms install -m r8168 -v 8.041.00 -k 4.4.0-31-generic'
3) upgrade your kernel e.g. "sudo apt install linux-image-generic'
4) sudo apt autoremove
5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot without a corresponding "initrd.img-4.4.0-31-generic"
With the version of dkms in -proposed, the .old-dkms file will be
removed when the kernel is auto removed.
[Regression Potential]
Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation.
One notices *.old-dkms files being left behind still sitting on the
disk after purging the related kernel. This can cause /boot to become
full, and when it gets really bad, even sudo apt-get autoremove won't
fix the problem - only deleting the old-dkms files manually solves the
problem.
Note: Filling up the /boot partition causes updates to fail.
ProblemType: BugDistroRelease: Ubuntu 15.04
Package: dkms 2.2.0.3-2ubuntu3.3
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.7
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Nov 12 08:17:10 2015
InstallationDate: Installed on 2015-05-05 (190 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: allSourcePackage: dkms
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+subscriptions
More information about the foundations-bugs
mailing list