free space check doesn't take into account kernel upgrades
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
Fix Released
|
Medium
|
Brian Murray | ||
Xenial |
Fix Released
|
High
|
Brian Murray |
Bug Description
[Test Case]
If you don't have a separate /boot partition you can create a file which will be loopback mounted as boot and then test having a full /boot.
1) Install xenial hwe backport kernel
2) dd if=/dev/zero of=fake-boot bs=1024 count=204800
3) mkfs -t ext3 fake-boot
4) copy your real /boot somewhere
5) sudo mount -t ext3 fake-boot /boot
6) copy the files from your old /boot into the /boot
7) fill /boot up some more e.g. fallocate -l 50M filler.txt
8) upgrade from Trusty to Xenial (do-release-
With the version of the release-upgrader in the archive you'll receive an error regarding "gzip: stdout: No space left on device... mkinitramfs failure cpio 141 gzip 1".
With the version of the release-upgrader from -proposed you'll receive an error notification that there is "Not enough free disk space" and the upgrade will not proceed.
[Regression Potential]
There is little chance of regression as we are just checking to see if linux-image or linux-image-debug packages are marked for upgrade.
Could not install 'linux-
ProblemType: BugDistroRelease: Ubuntu 16.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Wed Nov 9 20:11:19 2016
InstallationDate: Installed on 2015-05-24 (535 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitec
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_CA.UTF-8
SHELL=
Symptom: release-upgrade
UpgradeStatus: Upgraded to xenial on 2016-11-10 (0 days ago)
VarLogDistupgra
VarLogDistupgra
tags: | added: trusty2xenial |
summary: |
- subprocess installed post-installation script returned error exit status - 2 + free space check doesn't take into account kernel upgrades |
Changed in ubuntu-release-upgrader (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Brian Murray (brian-murray) |
Changed in ubuntu-release-upgrader (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in ubuntu-release-upgrader (Ubuntu Xenial): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Brian Murray (brian-murray) |
description: | updated |
description: | updated |
description: | updated |
You seem to have run out of disk space, likely in /boot if that is a separate partition.
Examining /etc/kernel/ postinst. d. postinst. d/apt-auto- removal 4.4.0-38-generic /boot/vmlinuz- 4.4.0-38- generic postinst. d/dkms 4.4.0-38-generic /boot/vmlinuz- 4.4.0-38- generic postinst. d/initramfs- tools 4.4.0-38-generic /boot/vmlinuz- 4.4.0-38- generic img-4.4. 0-38-generic x86_64- linux-gnu/ plymouth/ /.so) missing, skipping that theme.
run-parts: executing /etc/kernel/
run-parts: executing /etc/kernel/
run-parts: executing /etc/kernel/
update-initramfs: Generating /boot/initrd.
W: plymouth module (/usr/lib/
gzip: stdout: No space left on device img-4.4. 0-38-generic with 1. postinst. d/initramfs- tools exited with return code 1
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.
run-parts: /etc/kernel/
Please try removing some old kernels and running 'sudo apt-get -f install'. Thanks!