Upgrade from 17.10 to 18.04 LTS out of diskspace on /boot
Hi. I'm upgrading my servers from 17.10 to 18.04 LTS. However, when it gets to the kernel updates it runs out of disk space in /boot.
####
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for initramfs-tools (0.130ubuntu3.3) ...
update-initramfs: Generating /boot/initrd.
gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Processing triggers for linux-image-
/etc/kernel/
update-initramfs: Generating /boot/initrd.
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/
gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.
run-parts: /etc/kernel/
dpkg: error processing package linux-image-
installed linux-image-
Processing triggers for systemd (237-3ubuntu10.3) ...
Processing triggers for libapache2-
Errors were encountered while processing:
initramfs-tools
linux-
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1)
*** Send problem report to the developers?
####
At this point I'm able to exit the installation. I manually removed the old kernels created during the update to free up more space in /boot. When I enter update commands there is nothing to update so it seems to be done. But I don't know what it was trying to finish.
This is what is left in /boot after the removal of older initrd.
# ls -ltr /boot
total 129610
drwx------ 2 root root 12288 Jun 1 2014 lost+found
-rw-r--r-- 1 root root 184840 Jan 28 2016 memtest86+
-rw-r--r-- 1 root root 184380 Jan 28 2016 memtest86+.elf
-rw-r--r-- 1 root root 182704 Jan 28 2016 memtest86+.bin
-rw------- 1 root root 7870224 Jun 11 19:25 vmlinuz-
-rw------- 1 root root 3884611 Jun 11 19:25 System.
-rw-r--r-- 1 root root 255 Jun 11 19:25 retpoline-
-rw-r--r-- 1 root root 213212 Jun 11 19:25 config-
-rw-r--r-- 1 root root 1501528 Jun 11 19:25 abi-4.13.
-rw------- 1 root root 4046393 Sep 24 10:08 System.
-rw-r--r-- 1 root root 0 Sep 24 10:08 retpoline-
-rw-r--r-- 1 root root 216954 Sep 24 10:08 config-
-rw-r--r-- 1 root root 1537821 Sep 24 10:08 abi-4.15.
-rw------- 1 root root 8277752 Sep 24 11:54 vmlinuz-
-rw-r--r-- 1 root root 50368264 Oct 2 20:14 initrd.
-rw-r--r-- 1 root root 53703477 Oct 2 20:14 initrd.
drwxr-xr-x 5 root root 1024 Oct 2 20:14 grub
I looks like it's a mix of old 4.13.0-46 and new 4.15.0-36 files. Did the upgrade complete?
The server is working but I rather it complete without a space issue. I don't have a way to expand /boot without a rebuild.
Is there a way to run do-release-upgrade without it updating the new kernels? The process does not autoremove them. If it just does one kernel then I can do the others after the upgrade is done.
Is there another option other than do-release-upgrade that gives me more control over the update process?
Thanks for the help.
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- actionparsnip
- Solved:
- Last query:
- Last reply: