Upgrade error

ClusterX

Member
Apr 12, 2018
49
3
13
52
I get this "No space left on device" error on latest upgrade, I did not rebooted yet ... what would be the best way to fix that issue?

Code:
gzip: stdout: No space left on device
E: mkinitramfs failure find 141 cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.15.18-10-pve with 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/pve-kernel-4.15.18-10-pve.postinst line 19.
dpkg: error processing package pve-kernel-4.15.18-10-pve (--configure):
 subprocess installed post-installation script returned error exit status 2
Setting up pve-xtermjs (3.10.1-1) ...
Setting up libpve-storage-perl (5.0-36) ...
dpkg: dependency problems prevent configuration of pve-kernel-4.15:
 pve-kernel-4.15 depends on pve-kernel-4.15.18-10-pve; however:
  Package pve-kernel-4.15.18-10-pve is not configured yet.

dpkg: error processing package pve-kernel-4.15 (--configure):
 dependency problems - leaving unconfigured
Setting up libpve-guest-common-perl (2.0-19) ...
Setting up qemu-server (5.0-45) ...
Setting up pve-ha-manager (2.0-6) ...
Setting up pve-container (2.0-33) ...
Setting up pve-manager (5.3-8) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.15.18-9-pve

gzip: stdout: No space left on device
E: mkinitramfs failure find 141 cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.15.18-9-pve with 1.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for pve-ha-manager (2.0-6) ...
Processing triggers for systemd (232-25+deb9u8) ...
Errors were encountered while processing:
 pve-kernel-4.15.18-10-pve
 pve-kernel-4.15
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)



Code:
Filesystem            1K-blocks     Used  Available Use% Mounted on
udev                   16312468        0   16312468   0% /dev
tmpfs                   3266652   294984    2971668  10% /run
/dev/mapper/vg0-root   30832636  5812692   23430696  20% /
tmpfs                  16333244    18720   16314524   1% /dev/shm
tmpfs                      5120        0       5120   0% /run/lock
tmpfs                  16333244        0   16333244   0% /sys/fs/cgroup
/dev/md0                 498980   479380          0 100% /boot
/dev/mapper/vg0-data 1857690664 66815964 1696486476   4% /var/lib/vz
tmpfs                   3266648        0    3266648   0% /run/user/1000
/dev/fuse                 30720       20      30700   1% /etc/pve
 
You have to delete files on this host.
e.g. old no more used Kernels.
 
Probably your boot partition got filled to 100%.

Can you post the outputs of the following commands:

Code:
df -h
lvs -a
dpkg -l | grep pve-kernel
uname -r
 
Hi,
your harddisk is full!!
Which depends on your installation (wher /boot reside on).
do an
Code:
cd /boot
df -h .
Depends on your installation, you can purge old kernel (not the still running one), or remove other stuff (backups/iso...).

Udo
 
thanks!
I have removed a few old kernel images like:
Code:
apt purge pve-kernel-4.13.16-2-pve
...

it seems that the new pve kernel image was compiled during un-installing process but I gues it would be better to re-install it maybe?
is that the correct way w/ pve or did I missed something?
Code:
apt install --reinstall pve-kernel-4.15.18-10-pve
update-initramfs -u
update-grub
 
Last edited:
OK I have re-installed the complete upgrade part:
Code:
apt install --reinstall pve-kernel-4.15.18-10-pve base-files libpve-guest-common-perl libpve-storage-perl librados2-perl lxc-pve pve-cluster pve-container pve-firewall pve-ha-manager pve-kernel-4.15 pve-manager pve-xtermjs qemu-server

so I guess that I can reboot the system now
Code:
Setting up base-files (9.9+deb9u7) ...
(Reading database ... 96953 files and directories currently installed.)
Preparing to unpack .../00-libpve-guest-common-perl_2.0-19_all.deb ...
Unpacking libpve-guest-common-perl (2.0-19) over (2.0-19) ...
Preparing to unpack .../01-librados2-perl_1.0-6_amd64.deb ...
Unpacking librados2-perl (1.0-6) over (1.0-6) ...
Preparing to unpack .../02-lxc-pve_3.1.0-2_amd64.deb ...
Unpacking lxc-pve (3.1.0-2) over (3.1.0-2) ...
Preparing to unpack .../03-pve-cluster_5.0-33_amd64.deb ...
Unpacking pve-cluster (5.0-33) over (5.0-33) ...
Preparing to unpack .../04-pve-container_2.0-33_all.deb ...
Unpacking pve-container (2.0-33) over (2.0-33) ...
Preparing to unpack .../05-pve-ha-manager_2.0-6_amd64.deb ...
Unpacking pve-ha-manager (2.0-6) over (2.0-6) ...
Preparing to unpack .../06-pve-kernel-4.15_5.3-1_all.deb ...
Unpacking pve-kernel-4.15 (5.3-1) over (5.3-1) ...
Preparing to unpack .../07-pve-kernel-4.15.18-10-pve_4.15.18-32_amd64.deb ...
Unpacking pve-kernel-4.15.18-10-pve (4.15.18-32) over (4.15.18-32) ...
Preparing to unpack .../08-libpve-storage-perl_5.0-36_all.deb ...
Unpacking libpve-storage-perl (5.0-36) over (5.0-36) ...
Preparing to unpack .../09-pve-manager_5.3-8_amd64.deb ...
Unpacking pve-manager (5.3-8) over (5.3-8) ...
Preparing to unpack .../10-pve-xtermjs_3.10.1-1_amd64.deb ...
Unpacking pve-xtermjs (3.10.1-1) over (3.10.1-1) ...
Preparing to unpack .../11-qemu-server_5.0-45_amd64.deb ...
Unpacking qemu-server (5.0-45) over (5.0-45) ...
Preparing to unpack .../12-pve-firewall_3.0-17_amd64.deb ...
Unpacking pve-firewall (3.0-17) over (3.0-17) ...
Setting up lxc-pve (3.1.0-2) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for systemd (232-25+deb9u8) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up pve-cluster (5.0-33) ...
Setting up librados2-perl (1.0-6) ...
Setting up pve-firewall (3.0-17) ...
Setting up pve-kernel-4.15.18-10-pve (4.15.18-32) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.15.18-10-pve /boot/vmlinuz-4.15.18-10-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.15.18-10-pve /boot/vmlinuz-4.15.18-10-pve
update-initramfs: Generating /boot/initrd.img-4.15.18-10-pve
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.15.18-10-pve /boot/vmlinuz-4.15.18-10-pve
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.15.18-10-pve /boot/vmlinuz-4.15.18-10-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.18-10-pve
Found initrd image: /boot/initrd.img-4.15.18-10-pve
Found linux image: /boot/vmlinuz-4.15.18-9-pve
Found initrd image: /boot/initrd.img-4.15.18-9-pve
Found linux image: /boot/vmlinuz-4.15.18-8-pve
Found initrd image: /boot/initrd.img-4.15.18-8-pve
Found linux image: /boot/vmlinuz-4.15.18-4-pve
Found initrd image: /boot/initrd.img-4.15.18-4-pve
done
Setting up pve-xtermjs (3.10.1-1) ...
Setting up libpve-storage-perl (5.0-36) ...
Setting up pve-kernel-4.15 (5.3-1) ...
Setting up libpve-guest-common-perl (2.0-19) ...
Setting up qemu-server (5.0-45) ...
Setting up pve-ha-manager (2.0-6) ...
Setting up pve-container (2.0-33) ...
Setting up pve-manager (5.3-8) ...
Processing triggers for pve-ha-manager (2.0-6) ...
Processing triggers for systemd (232-25+deb9u8) ...
 

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!