package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

Bug #1885013 reported by H.-R. Oberhage
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lilo (Ubuntu)
New
Undecided
Unassigned

Bug Description

Problem occurred during a (longer) system update

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.9
ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
Date: Wed Jun 24 21:21:05 2020
ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2015-07-08 (1813 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt 1.6.12ubuntu0.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
H.-R. Oberhage (oberhage) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Kai Kasurinen (kai-kasurinen) wrote :

Processing triggers for initramfs-tools (0.130ubuntu3.9) ...
update-initramfs: Generating /boot/initrd.img-4.18.0-17-generic
Fatal: open /initrd.img: No such file or directory
run-parts: /etc/initramfs/post-update.d//runlilo exited with return code 1

affects: initramfs-tools (Ubuntu) → lilo (Ubuntu)
Revision history for this message
H.-R. Oberhage (oberhage) wrote :

It is/was probably just a transitional problem: After using the system for some time now, I experience no problem. It boots as reliable as before after it had to re-run the lilo-configuration again, anyhow, because of me phasing out old(er) kernels. Thanks!

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.