Updated/upgraded Just Now

N

Nollimox

Member
Mar 9, 2023
273
22
23
So, I just updated/upgraded just now and as usual, I like to run apt-get autoremove...but then got fix broken install. So, I did and got an error...now wondering, how I might proceed?

Linux pve 6.8.12-9-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-9 (2025-03-16T19:18Z) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Mar 24 12:46:40 CDT 2025 on pts/0
root@pve:~# apt-get autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
proxmox-kernel-6.8 : Depends: proxmox-kernel-6.8.12-10-pve-signed but it is not installed or
proxmox-kernel-6.8.12-10-pve
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
root@pve:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
proxmox-kernel-6.8.12-10-pve-signed
The following NEW packages will be installed:
proxmox-kernel-6.8.12-10-pve-signed
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
48 not fully installed or removed.
Need to get 0 B/103 MB of archives.
After this operation, 577 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 69096 files and directories currently installed.)
Preparing to unpack .../proxmox-kernel-6.8.12-10-pve-signed_6.8.12-10_amd64.deb ...
Unpacking proxmox-kernel-6.8.12-10-pve-signed (6.8.12-10) ...
dpkg: error processing archive /var/cache/apt/archives/proxmox-kernel-6.8.12-10-pve-signed_6.8.12-10_amd64.deb (--unpack):
cannot copy extracted data for './lib/modules/6.8.12-10-pve/kernel/net/tipc/tipc.ko' to '/lib/modules/6.8.12-10-pve/kernel/net/tipc/tipc.ko.dpkg-new': failed to write (No space left on device)
Examining /etc/kernel/postrm.d.
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 6.8.12-10-pve /boot/vmlinuz-6.8.12-10-pve
update-initramfs: Deleting /boot/initrd.img-6.8.12-10-pve
run-parts: executing /etc/kernel/postrm.d/proxmox-auto-removal 6.8.12-10-pve /boot/vmlinuz-6.8.12-10-pve
run-parts: executing /etc/kernel/postrm.d/zz-proxmox-boot 6.8.12-10-pve /boot/vmlinuz-6.8.12-10-pve
Re-executing '/etc/kernel/postrm.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/A6C4-952B
Copying kernel 6.5.13-6-pve
Copying kernel 6.8.12-8-pve
Copying kernel 6.8.12-9-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-9-pve
Found initrd image: /boot/initrd.img-6.8.12-9-pve
Found linux image: /boot/vmlinuz-6.8.12-8-pve
Found initrd image: /boot/initrd.img-6.8.12-8-pve
Found linux image: /boot/vmlinuz-6.5.13-6-pve
Found initrd image: /boot/initrd.img-6.5.13-6-pve
done
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 6.8.12-10-pve /boot/vmlinuz-6.8.12-10-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-9-pve
Found initrd image: /boot/initrd.img-6.8.12-9-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Found linux image: /boot/vmlinuz-6.8.12-8-pve
Found initrd image: /boot/initrd.img-6.8.12-8-pve
Found linux image: /boot/vmlinuz-6.5.13-6-pve
Found initrd image: /boot/initrd.img-6.5.13-6-pve
Found linux image: /boot/vmlinuz-6.5.11-4-pve
Found initrd image: /boot/initrd.img-6.5.11-4-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Found memtest86+x64 image: /ROOT/pve-1@/boot/memtest86+x64.bin
done
Errors were encountered while processing:
/var/cache/apt/archives/proxmox-kernel-6.8.12-10-pve-signed_6.8.12-10_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@pve:~#
 
This is the main problem I think:

Code: 
cannot copy extracted data for './lib/modules/6.8.12-10-pve/kernel/net/tipc/tipc.ko' to '/lib/modules/6.8.12-10-pve/kernel/net/tipc/tipc.ko.dpkg-new': failed to write (No space left on device)

You need to clean up something to make space. This will also lead to many other fun problems if not taken care of.
 
I don't know why I encountered same issue, but different case

Bash: 
root@pve-home:~# apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up proxmox-kernel-6.8.12-10-pve-signed (6.8.12-10) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.8.12-10-pve /boot/vmlinuz-6.8.12-10-pve
update-initramfs: Generating /boot/initrd.img-6.8.12-10-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
run-parts: /etc/initramfs/post-update.d//proxmox-boot-sync exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.8.12-10-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.8.12-10-pve-signed (--configure):
 installed proxmox-kernel-6.8.12-10-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.8:
 proxmox-kernel-6.8 depends on proxmox-kernel-6.8.12-10-pve-signed | proxmox-kernel-6.8.12-10-pve; however:
  Package proxmox-kernel-6.8.12-10-pve-signed is not configured yet.
  Package proxmox-kernel-6.8.12-10-pve is not installed.
  Package proxmox-kernel-6.8.12-10-pve-signed which provides proxmox-kernel-6.8.12-10-pve is not configured yet.

dpkg: error processing package proxmox-kernel-6.8 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-6.8.12-10-pve-signed
 proxmox-kernel-6.8
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@pve-home:~#

Bash: 
root@pve-home:~# pveversion -v
proxmox-ve: 8.4.0 (running kernel: 6.11.11-2-pve)
pve-manager: 8.4.1 (running version: 8.4.1/2a5fa54a8503f96d)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.11.11-2-pve-signed: 6.11.11-2
proxmox-kernel-6.11: 6.11.11-2
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.8.12-7-pve-signed: 6.8.12-7
ceph-fuse: 17.2.7-pve3
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
intel-microcode: 3.20250211.1~deb12u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.0
libpve-cluster-perl: 8.1.0
libpve-common-perl: 8.3.1
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.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.6.0-2
proxmox-backup-client: 3.4.1-1
proxmox-backup-file-restore: 3.4.1-1
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.2
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.10
pve-cluster: 8.1.0
pve-container: 5.2.6
pve-docs: 8.4.0
pve-edk2-firmware: 4.2025.02-3
pve-esxi-import-tools: 0.7.3
pve-firewall: 5.1.1
pve-firmware: 3.15-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.2
pve-qemu-kvm: 9.2.0-5
pve-xtermjs: 5.5.0-2
qemu-server: 8.3.12
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve2
root@pve-home:~#
 
You must log in or register to reply here.
Top Bottom