no space left on device upgrading from focal to jammy with do-release-upgrade

[John Greep]

Trying to upgrade to the latest image.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-48-generic 5.15.0-48.54
ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203
Uname: Linux 5.4.0-126-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Oct 2 01:45 seq
 crw-rw---- 1 root audio 116, 33 Oct 2 01:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Sun Oct 2 01:51:16 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: DigitalOcean Droplet
PciMultimedia:

ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic root=UUID=db153994-91fe-426f-bd88-f751e07f97f2 ro console=tty1 console=ttyS0
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu7
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: initramfs-tools
Title: package linux-image-5.15.0-48-generic 5.15.0-48.54 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
UpgradeStatus: Upgraded to jammy on 2022-10-02 (0 days ago)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: DigitalOcean
dmi.bios.version: 20171212
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
dmi.product.family: DigitalOcean_Droplet
dmi.product.name: Droplet
dmi.product.version: 20171212
dmi.sys.vendor: DigitalOcean

[Steve Langasek (vorlon)]

The error in your log is:

Processing triggers for linux-image-5.15.0-48-generic (5.15.0-48.54) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-48-generic
cpio: write error: No space left on device
E: mkinitramfs failure cpio 2
update-initramfs: failed for /boot/initrd.img-5.15.0-48-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

This is not a bug in initramfs-tools, per se; initramfs-tools can't make your root partition larger than it is. And you do not have a separate /boot partition, so this is not a bug of an installer setting up /boot to be an inappropriate size. The only thing that can be done in this circumstance is for you to free up some space on your root partition and try to resume the upgrade with 'apt -f install'.

Were you running apt dist-upgrade manually to go from focal to jammy, or were you using do-release-upgrade, the recommended tool? The release upgrader includes some checks to ensure sufficient free space before committing to the upgrade, so we would want to know if those are inadequate.

[John Greep (jgreep)]

Yes, I eventually figured out I was out of space.
I used the recommended do-release-upgrade, so I would say that the free space check was insufficient.
At this point, I rebuilt the server and migrated my data as I couldn't get the upgrade to resume after making space.
Thanks for looking into this.