Upgrade error - zstd: error 70 : Write error : cannot write block : No space left on device

Apr 11, 2024
5
1
3
Hi All,

Since a few months I'm a very happy user of Proxmox.
The only thing at the moment is that I'm always having an issue with upgrading the PVE kernel.
"zstd: error 70 : Write error : cannot write block : No space left on device"

So, during setup of the system, I had to choose a larger boot partition.....
Can I decrease the size of "nvme1n1p3" with 1 GB and add the 1 GB to "nvme1n1p2"?
If yes, how....using lvextend and/or parted?

xyz@xyz:/boot$ uname -a
Linux nwm 6.8.12-4-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-4 (2024-11-06T15:04Z) x86_64 GNU/Linux
xyz@xyz:/boot$ dpkg --list|grep proxmox-kernel.*-pve
ii proxmox-kernel-6.8.12-4-pve-signed 6.8.12-4

lsblk -fm
NAME FSTYPE FSVER LABEL FSAVAIL FSUSE% MOUNTPOINTS SIZE OWNER GROUP MODE
loop0 ext4 1.0 8G root disk brw-rw----
loop1 ext4 1.0 50G root disk brw-rw----
loop2 ext4 1.0 20G root disk brw-rw----
loop3 ext4 1.0 8G root disk brw-rw----
loop4 ext4 1.0 12G root disk brw-rw----
nvme0n1 1.8T root disk brw-rw----
├─nvme0n1p1 zfs_member 5000 tank 1.8T root disk brw-rw----
└─nvme0n1p9 8M root disk brw-rw----
nvme1n1 476.9G root disk brw-rw----
├─nvme1n1p1 vfat FAT32 499.1M 2% /boot/efi 512M root disk brw-rw----
├─nvme1n1p2 ext2 1.0 259.4M 38% /boot 488M root disk brw-rw----
└─nvme1n1p3 LVM2_member LVM2 476G root disk brw-rw----
├─xyz--vg-root ext4 1.0 418.4G 5% / 475G root disk brw-rw----
└─xyz--vg-swap_1 swap 1 [SWAP] 980M root disk brw-rw----


xyz@xyz:/boot$df -h
Filesystem Size Used Avail Use% Mounted on
udev 16G 0 16G 0% /dev
tmpfs 3.2G 2.9M 3.2G 1% /run
/dev/mapper/xyz--vg-root 467G 25G 419G 6% /
tmpfs 16G 37M 16G 1% /dev/shm
tmpfs 5.0M 8.0K 5.0M 1% /run/lock
efivarfs 150K 78K 68K 54% /sys/firmware/efi/efivars
/dev/nvme1n1p2 456M 172M 260M 40% /boot
/dev/nvme1n1p1 511M 12M 500M 3% /boot/efi
/dev/fuse 128M 20K 128M 1% /etc/pve
tmpfs 3.2G 96K 3.2G 1% /run/user/1000

Thank you in advance!
 
Hi,

what does pveversion -v report?
You probably have (a lot of) old kernels installed, which do not get automatically removed during/after an upgrade for various reason (e.g. booting an old kernel in case a newer one doesn't work).

I'd suggest simply removing some of them, that should clear space on your boot partition. 512MiB-1GiB is normally more than enough for at least 4-5 kernel.
 
Hi,

what does pveversion -v report?
You probably have (a lot of) old kernels installed, which do not get automatically removed during/after an upgrade for various reason (e.g. booting an old kernel in case a newer one doesn't work).

I'd suggest simply removing some of them, that should clear space on your boot partition. 512MiB-1GiB is normally more than enough for at least 4-5 kernel.
Hi,

what does pveversion -v report?
You probably have (a lot of) old kernels installed, which do not get automatically removed during/after an upgrade for various reason (e.g. booting an old kernel in case a newer one doesn't work).

I'd suggest simply removing some of them, that should clear space on your boot partition. 512MiB-1GiB is normally more than enough for at least 4-5 kernel.
Hi Christoph,
Herewith the result:

xyz@xyz:~$ pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.12-4-pve)
pve-manager: 8.2.8 (running version: 8.2.8/a577cfa684c7476d)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx9
intel-microcode: 3.20240910.1~deb12u1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.8
libpve-cluster-perl: 8.0.8
libpve-common-perl: 8.2.8
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.11
libpve-storage-perl: 8.2.6
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.2.8-1
proxmox-backup-file-restore: 3.2.8-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.0
pve-cluster: 8.0.8
pve-container: 5.2.1
pve-docs: 8.2.4
pve-edk2-firmware: not correctly installed
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.0.7
pve-firmware: 3.14-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.4
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!