package linux-image-3.19.0-68-generic 3.19.0-68.76~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 on boot after autoupgrade while /boot was 100% full
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-lts-vivid (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
A virtual machine running on a Windows Server 2012R2 Hyper-V system rebooted as part of an automated upgrade last night. It seems to have just installed the new 3.19.0-68-generic kernel. The system failed to boot and instead kernel paniced.
As part of investigating the problem we tried booting the previously installed kernel (66 I think) and could bring up the system OK. It asked to perform a disk check on / and /boot as it came up, which seemed to go fine. Once we were running a `df -h` showed that /boot was 100% full with no space left at all. To improve the system an `apt-get autoremove` was run which uninstalled a bunch of older kernels, freeing just over 100MB of space from /boot. Power cycling the system allowed us to boot successfully under the new 3.19.0-68 kernel.
Hopefully the /var/crash/
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.19.0-68-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Tue Aug 30 06:51:28 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationDate: Installed on 2016-02-08 (204 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageV
dpkg 1.17.5ubuntu5.7
apt 1.0.1ubuntu2.14
SourcePackage: linux-lts-vivid
Title: package linux-image-
UpgradeStatus: No upgrade log present (probably fresh install)
| Thomas A. F. Thorne (tafthorne) wrote | #1 |
| Thomas A. F. Thorne (tafthorne) wrote | #2 |
| Thomas A. F. Thorne (tafthorne) wrote | #3 |
Oh, this is not the kernel panic I was thinking that I was reporting. It does show that there was some kind of problem with the upgrade process though. That may relate to the kernel panic which I saw.