package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

Bug #1875407 reported by Tom M
276
This bug affects 63 people
Affects Status Importance Assigned to Milestone
initramfs-tools (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Received this error when doing do-release-upgrade from ubuntu 18.04.4 to 20.4

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Apr 27 09:59:42 2020
ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2016-01-12 (1567 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-04-27 (0 days ago)

Revision history for this message
Tom M (reslip) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in initramfs-tools (Ubuntu):
status: New → Confirmed
Revision history for this message
Rosen Sama (rosensama) wrote :

I think this is occurring because /boot is filling up. I have a boot partition sized to defaults by the Unbuntu installer. That's 721392 1K-blocks per df. Lately, as 20.04.3 has picked up newer kernels, too many have been retained. I had associated files for one 5.10.0, one 5.11.0, and two 5.13.0 on there. `apt autoremove` didn't affect those retained. I believe that left initramfs-tools with too little space to update an existing version. Most of the space are the initrd.img files.

Revision history for this message
edward prest (edwardprest) wrote :

while installing kicad v6 on brand new 20.04 install on ssd

using

sudo add-apt-repository --yes ppa:kicad/kicad-6.0-releases
sudo apt update
sudo apt install --install-recommends kicad
# If you want demo projects
sudo apt install kicad-demos

fails with

Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for initramfs-tools (0.136ubuntu6.6) ...
update-initramfs: Generating /boot/initrd.img-5.13.0-28-generic
E: /usr/share/initramfs-tools/hooks/iscan failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.13.0-28-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
Mikkel Kirkgaard Nielsen (mikini) wrote :

Like #3 experienced, logs seems to make it plausible that this is caused by inadequate storage on /boot.

See Df.txt;
/dev/sda1 240972 190591 37940 84% /boot

See end of DpkgTerminalLog.txt;
update-initramfs: Generating /boot/initrd.img-5.4.0-26-generic
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-26-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1

Revision history for this message
Benjamin Drung (bdrung) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 798414, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.