problem with update dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

D

demon13

Member
Oct 27, 2022
3
0
6
When updating
apt --fix-broken install
Get:1 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 pve-kernel-5.15.64-1-pve amd64 5.15.64-1 [76.7 MB] Fetched 76.7 MB in 10s (7608 kB/s) (Reading database ... 119398 files and directories currently installed.) Preparing to unpack .../pve-kernel-5.15.64-1-pve_5.15.64-1_amd64.deb ... Unpacking pve-kernel-5.15.64-1-pve (5.15.64-1) ... dpkg: error processing archive /var/cache/apt/archives/pve-kernel-5.15.64-1-pve_5.15.64-1_amd64.deb (--unpack): cannot copy extracted data for './boot/vmlinuz-5.15.64-1-pve' to '/boot/vmlinuz-5.15.64-1-pve.dpkg-new': failed to write (No space left on device) dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Examining /etc/kernel/postrm.d. run-parts: executing /etc/kernel/postrm.d/initramfs-tools 5.15.64-1-pve /boot/vmlinuz-5.15.64-1-pve update-initramfs: Deleting /boot/initrd.img-5.15.64-1-pve run-parts: executing /etc/kernel/postrm.d/proxmox-auto-removal 5.15.64-1-pve /boot/vmlinuz-5.15.64-1-pve run-parts: executing /etc/kernel/postrm.d/zz-proxmox-boot 5.15.64-1-pve /boot/vmlinuz-5.15.64-1-pve Re-executing '/etc/kernel/postrm.d/zz-proxmox-boot' in new private mount namespace.. No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync. run-parts: executing /etc/kernel/postrm.d/zz-update-grub 5.15.64-1-pve /boot/vmlinuz-5.15.64-1-pve Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.60-1-pve Found linux image: /boot/vmlinuz-5.15.53-1-pve Found initrd image: /boot/initrd.img-5.15.53-1-pve Found linux image: /boot/vmlinuz-5.15.39-4-pve Found initrd image: /boot/initrd.img-5.15.39-4-pve Found linux image: /boot/vmlinuz-5.15.39-3-pve Found initrd image: /boot/initrd.img-5.15.39-3-pve Found linux image: /boot/vmlinuz-5.4.195-1-pve Found initrd image: /boot/initrd.img-5.4.195-1-pve Found linux image: /boot/vmlinuz-5.4.65-1-pve Found initrd image: /boot/initrd.img-5.4.65-1-pve Found linux image: /boot/vmlinuz-4.19.0-16-amd64 Found initrd image: /boot/initrd.img-4.19.0-16-amd64 Found linux image: /boot/vmlinuz-4.19.0-14-amd64 Found initrd image: /boot/initrd.img-4.19.0-14-amd64 Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done Errors were encountered while processing: /var/cache/apt/archives/pve-kernel-5.15.64-1-pve_5.15.64-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
How to fix it ?

Thanks
 
#uname -r
5.15.53-1-pve
dpkg --list | grep linux-image
rc linux-image-4.19.0-11-amd64 4.19.146-1 amd64 Linux 4.19 for 64-bit PCs (signed)
rc linux-image-4.19.0-12-amd64 4.19.152-1 amd64 Linux 4.19 for 64-bit PCs (signed)
ii linux-image-4.19.0-14-amd64 4.19.171-2 amd64 Linux 4.19 for 64-bit PCs (signed)
ii linux-image-4.19.0-16-amd64 4.19.181-1 amd64 Linux 4.19 for 64-bit PCs (signed)
 
Last edited:
demon13 said:
cannot copy extracted data for './boot/vmlinuz-5.15.64-1-pve' to '/boot/vmlinuz-5.15.64-1-pve.dpkg-new': failed to write (No space left on device)
Click to expand...
Your root filesystem appears to be full. Maybe you can recover some space by deleting old logs from /var/log?

EDIT: Maybe there was an mounting issue with your storage configuration and you accidentally stored backups on your root filesystem? And check /var/tmp and /tmp for old/failed uploads that might take up space.
 
Last edited:
You must log in or register to reply here.
Top Bottom