As atualizações do kernel não serão instaladas - partição de inicialização cheia

As atualizações do kernel não serão instaladas - partição de inicialização cheia

Estou executando o 14.04 LTS.

As atualizações do kernel não serão instaladas ou desinstaladas. O espaço de inicialização (aproximadamente 240 MB) agora está cheio e usar sudo apt-get autoremove, autocleanou não funcionará.cleanremove

Tudo isso começou com a atualização do kernel 3.13.0-47.

Nenhum espaço é liberado e surge o seguinte.....

sudo apt-get autoremove
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 to upgrade, 0 to newly install, 0 to remove and 60 not to upgrade.
7 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-image-3.13.0-47-generic (3.13.0-47.78) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-3.13.0-48-generic
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-47-generic /boot/vmlinuz-3.13.0-47-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-47-generic /boot/vmlinuz-3.13.0-47-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-47-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.13.0-47-generic 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/linux-image-3.13.0-47-generic.postinst line 1025.
dpkg: error processing package linux-image-3.13.0-47-generic (--configure):
 subprocess installed post-installation script returned error exit status 2
Setting up linux-image-3.13.0-48-generic (3.13.0-48.80) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-3.13.0-47-generic
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-48-generic /boot/vmlinuz-3.13.0-48-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-48-generic /boot/vmlinuz-3.13.0-48-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-48-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.13.0-48-generic 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/linux-image-3.13.0-48-generic.postinst line 1025.
dpkg: error processing package linux-image-3.13.0-48-generic (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of linux-image-extra-3.13.0-48-generic:
 linux-image-extra-3.13.0-48-generic depends on linux-image-3.13.0-48-generic; however:
  Package linux-image-3.13.0-48-generic is not configured yet.

dpkg: error processing package linux-image-extra-3.13.0-48-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-image-3.13.0-48-generic; however:
  Package linux-image-3.13.0-48-generic is not configured yet.
 linux-image-generic depends on linux-image-extra-3.13.0-48-generic; however:
  Package linux-image-extra-3.13.0-48-generic is not configured yet.

dpkg: error processing package linux-image-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-image-generic (= 3.13.0.48.55); however:
  Package linux-image-generic is not cNo apport report written because the error message indicates it's a follow-up error from a previous failure.
                                                                  No apport report written because MaxReports has already been reached
                                                      No apport report written because MaxReports has already been reached
                                          onfigured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
Setting up linux-image-extra-3.13.0-46-generic (3.13.0-46.79) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-46-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.13.0-46-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-extra-3.13.0-46-generic (--configure):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports has already been reached
                                                                    dpkg: dependency problems prevent configuration of linux-image-extra-3.13.0-47-generic:
 linux-image-extra-3.13.0-47-generic depends on linux-image-3.13.0-47-generic; however:
  Package linux-image-3.13.0-47-generic is not configured yet.

> dpkg: error processing package linux-image-extra-3.13.0-47-generic (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports has already been reached
                                                                    E: Sub-process /usr/bin/dpkg returned an error code (1)

Como isso pode ser corrigido sem reinstalar? Tentei redimensionar a área de boot e o GParted não deixou.

Responder1

Eu tive o mesmo problema. Depois de fazer df -h vi que o meu /bootestava quase cheio. Eu atravesseieste guiapara desinstalar versões antigas do Ubuntu. Agora a atualização funciona bem. É um pouco estranho, porque normalmente recebo um erro informando que /bootestá quase cheio, em vez de uma mensagem de falha não descritiva.

informação relacionada