Severe Upgrade Issues

P

pma66271

Member
Oct 31, 2021
15
2
23
21
Hi all,

I tried to upgrade from 7.0.6-2-pve to 7.0.14-8-pve.

During that upgrade I faced the error messages below:
Failed to copy data from "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/B791-118F/EFI/systemd/.#systemd-bootx64.efi01029a360a392119": No space left on device
Failed to copy data from "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/B791-118F/EFI/BOOT/.#BOOTX64.EFI5247c37d17910daa": No space left on device

After reboot the old kernel is still active.

root@pve1:/var/tmp/espmounts# /usr/sbin/proxmox-boot-tool kernel list
Manually selected kernels:
None.
Automatically selected kernels:
7.0.14-8-pve
7.0.6-2-pve

root@pve1:/var/tmp/espmounts# /usr/sbin/proxmox-boot-tool clean
Checking whether ESP 'B791-118F' exists.. Found!
Checking whether ESP 'B791-6A03' exists.. Found!
Sorting and removing duplicate ESPs..

root@pve1:/var/tmp/espmounts# /usr/sbin/proxmox-boot-tool reinit
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
UUID="B791-118F" SIZE="536870912" FSTYPE="vfat" PARTTYPE="c12a7328-f81f-11d2-ba4b-00a0c93ec93b" PKNAME="nvme1n1" MOUNTPOINT=""
Mounting '/dev/disk/by-uuid/B791-118F' on '/var/tmp/espmounts/B791-118F'.
Adding memtest86+x64.efi ..
Installing systemd-boot..
Failed to copy data from "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/B791-118F/EFI/systemd/.#systemd-bootx64.efid9d9eb4b4ddaebcf": No space left on device
Failed to copy data from "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/var/tmp/espmounts/B791-118F/EFI/BOOT/.#BOOTX64.EFIa75c6ecfbdd55cc0": No space left on device


Can you please help me to solve this issue?
Something seems to be wrong with the mount

root@pve1:/var/tmp/espmounts# ls /var/tmp/espmounts/B791-118F
root@pve1:/var/tmp/espmounts#
 
Thanks, @Neobin
This helped a lot. The machine is now running again on the latest kernel.
The question is why this happed as I never had this issue before.
 
To prevent it in the future:
Neobin

[SOLVED] Post in thread 'Kernel upgrade gets No space left on device'

  • List installed kernels: apt list --installed | grep kernel
  • Purge all from old series (verify with the output from above!), e.g.:
    • apt purge pve-kernel-5*
    • apt purge proxmox-kernel-6*
  • Run: apt autoremove or: apt autoremove --purge regularly
  • Like

The following rules apply:
fabian

Post in thread 'clean old kernels'

PVE 6.x will now allow easy autoremoval of kernels. Only the following will be marked as not eligible for autoremoval:
- currently running kernel
- last installed kernel
- two latest kernels
- last kernel of each series
  • Like

So, when a kernel series gets the new default and you experience no problems with it for a while, you should (/ need to) manually remove the previous/old kernel series.
 
  • Like
Reactions: pma66271 and Johannes S
There have been some quick successions of kernel versions (and many minor updates to each of them) in PVE 9.x. If the ESP is on the small side (I think they were smaller in earlier PVE versions) then it can fill up unexpectedly.
I believe that if you don't remove the old default kernel versions, like proxmox-kernel-6.8, proxmox-kernel-6.14 and proxmox-kernel-6.17, then at least one of them remains on the ESP. Or maybe that happens only to me because I install the kernel headers (for vendor-reset dkms)? I religiously run apt autoremove --purge after each update.
 
  • Like
Reactions: pma66271, Neobin and Johannes S
You must log in or register to reply here.
Top Bottom
Back