I cannot upgrade Ubuntu or autoclean due to the inability to run “apt-get -f install”












0















I am unable to clean my disk space by running autoclean, nor can I upgrade because I am continually asked to run apt-get -f install however due to a full disk it will not install. autoclean doesn't work purge doesn't work. These are my results when I try to run upgrade:



agiles@agiles-23-1015:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
linux-image-extra-4.4.0-128-generic : Depends: linux-image-4.4.0-128-generic but it is not installed
linux-image-extra-4.4.0-130-generic : Depends: linux-image-4.4.0-130-generic but it is not installed
linux-image-extra-4.4.0-131-generic : Depends: linux-image-4.4.0-131-generic but it is not installed
linux-image-generic : Depends: linux-image-4.4.0-131-generic but it is not installed
E: Unmet dependencies. Try using -f.


When I run -f install:



agiles@agiles-23-1015:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-124 linux-headers-4.4.0-124-generic linux-headers-4.4.0-128 linux-headers-4.4.0-128-generic linux-headers-4.4.0-130
linux-headers-4.4.0-130-generic linux-image-4.4.0-124-generic linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-extra-4.4.0-124-generic
linux-image-extra-4.4.0-128-generic linux-image-extra-4.4.0-130-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-4.4.0-131-generic
Suggested packages:
fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools
The following NEW packages will be installed:
linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-4.4.0-131-generic
0 upgraded, 3 newly installed, 0 to remove and 194 not upgraded.
7 not fully installed or removed.
Need to get 0 B/66.4 MB of archives.
After this operation, 204 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 425417 files and directories currently installed.)
Preparing to unpack .../linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
Done.
Unpacking linux-image-4.4.0-131-generic (4.4.0-131.157) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-131-generic' to '/boot/vmlinuz-4.4.0-131-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
Preparing to unpack .../linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
Done.
Unpacking linux-image-4.4.0-128-generic (4.4.0-128.154) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-128-generic' to '/boot/vmlinuz-4.4.0-128-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
Preparing to unpack .../linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
Done.
Unpacking linux-image-4.4.0-130-generic (4.4.0-130.156) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-130-generic' to '/boot/vmlinuz-4.4.0-130-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb
/var/cache/apt/archives/linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb
/var/cache/apt/archives/linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)









share|improve this question




















  • 1





    Your disk is full. You need to free up some space to clean things up, strange as that may seem.

    – Jos
    Jul 17 '18 at 14:27













  • Try installing BleachBit from the Ubuntu Software Centre to free up some space

    – Graham
    Jul 17 '18 at 14:39






  • 1





    @Graham .. I can't stop laughing. If apt doesn't work because the disk is full, Software Center won't work either.

    – Soren A
    Jul 17 '18 at 16:11











  • @SorenA errr. good point. Hadn't thought of that. Case of fingers working faster than the grey cells methinks embarrassed

    – Graham
    Jul 17 '18 at 16:41
















0















I am unable to clean my disk space by running autoclean, nor can I upgrade because I am continually asked to run apt-get -f install however due to a full disk it will not install. autoclean doesn't work purge doesn't work. These are my results when I try to run upgrade:



agiles@agiles-23-1015:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
linux-image-extra-4.4.0-128-generic : Depends: linux-image-4.4.0-128-generic but it is not installed
linux-image-extra-4.4.0-130-generic : Depends: linux-image-4.4.0-130-generic but it is not installed
linux-image-extra-4.4.0-131-generic : Depends: linux-image-4.4.0-131-generic but it is not installed
linux-image-generic : Depends: linux-image-4.4.0-131-generic but it is not installed
E: Unmet dependencies. Try using -f.


When I run -f install:



agiles@agiles-23-1015:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-124 linux-headers-4.4.0-124-generic linux-headers-4.4.0-128 linux-headers-4.4.0-128-generic linux-headers-4.4.0-130
linux-headers-4.4.0-130-generic linux-image-4.4.0-124-generic linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-extra-4.4.0-124-generic
linux-image-extra-4.4.0-128-generic linux-image-extra-4.4.0-130-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-4.4.0-131-generic
Suggested packages:
fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools
The following NEW packages will be installed:
linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-4.4.0-131-generic
0 upgraded, 3 newly installed, 0 to remove and 194 not upgraded.
7 not fully installed or removed.
Need to get 0 B/66.4 MB of archives.
After this operation, 204 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 425417 files and directories currently installed.)
Preparing to unpack .../linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
Done.
Unpacking linux-image-4.4.0-131-generic (4.4.0-131.157) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-131-generic' to '/boot/vmlinuz-4.4.0-131-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
Preparing to unpack .../linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
Done.
Unpacking linux-image-4.4.0-128-generic (4.4.0-128.154) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-128-generic' to '/boot/vmlinuz-4.4.0-128-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
Preparing to unpack .../linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
Done.
Unpacking linux-image-4.4.0-130-generic (4.4.0-130.156) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-130-generic' to '/boot/vmlinuz-4.4.0-130-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb
/var/cache/apt/archives/linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb
/var/cache/apt/archives/linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)









share|improve this question




















  • 1





    Your disk is full. You need to free up some space to clean things up, strange as that may seem.

    – Jos
    Jul 17 '18 at 14:27













  • Try installing BleachBit from the Ubuntu Software Centre to free up some space

    – Graham
    Jul 17 '18 at 14:39






  • 1





    @Graham .. I can't stop laughing. If apt doesn't work because the disk is full, Software Center won't work either.

    – Soren A
    Jul 17 '18 at 16:11











  • @SorenA errr. good point. Hadn't thought of that. Case of fingers working faster than the grey cells methinks embarrassed

    – Graham
    Jul 17 '18 at 16:41














0












0








0








I am unable to clean my disk space by running autoclean, nor can I upgrade because I am continually asked to run apt-get -f install however due to a full disk it will not install. autoclean doesn't work purge doesn't work. These are my results when I try to run upgrade:



agiles@agiles-23-1015:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
linux-image-extra-4.4.0-128-generic : Depends: linux-image-4.4.0-128-generic but it is not installed
linux-image-extra-4.4.0-130-generic : Depends: linux-image-4.4.0-130-generic but it is not installed
linux-image-extra-4.4.0-131-generic : Depends: linux-image-4.4.0-131-generic but it is not installed
linux-image-generic : Depends: linux-image-4.4.0-131-generic but it is not installed
E: Unmet dependencies. Try using -f.


When I run -f install:



agiles@agiles-23-1015:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-124 linux-headers-4.4.0-124-generic linux-headers-4.4.0-128 linux-headers-4.4.0-128-generic linux-headers-4.4.0-130
linux-headers-4.4.0-130-generic linux-image-4.4.0-124-generic linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-extra-4.4.0-124-generic
linux-image-extra-4.4.0-128-generic linux-image-extra-4.4.0-130-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-4.4.0-131-generic
Suggested packages:
fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools
The following NEW packages will be installed:
linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-4.4.0-131-generic
0 upgraded, 3 newly installed, 0 to remove and 194 not upgraded.
7 not fully installed or removed.
Need to get 0 B/66.4 MB of archives.
After this operation, 204 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 425417 files and directories currently installed.)
Preparing to unpack .../linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
Done.
Unpacking linux-image-4.4.0-131-generic (4.4.0-131.157) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-131-generic' to '/boot/vmlinuz-4.4.0-131-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
Preparing to unpack .../linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
Done.
Unpacking linux-image-4.4.0-128-generic (4.4.0-128.154) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-128-generic' to '/boot/vmlinuz-4.4.0-128-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
Preparing to unpack .../linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
Done.
Unpacking linux-image-4.4.0-130-generic (4.4.0-130.156) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-130-generic' to '/boot/vmlinuz-4.4.0-130-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb
/var/cache/apt/archives/linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb
/var/cache/apt/archives/linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)









share|improve this question
















I am unable to clean my disk space by running autoclean, nor can I upgrade because I am continually asked to run apt-get -f install however due to a full disk it will not install. autoclean doesn't work purge doesn't work. These are my results when I try to run upgrade:



agiles@agiles-23-1015:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
linux-image-extra-4.4.0-128-generic : Depends: linux-image-4.4.0-128-generic but it is not installed
linux-image-extra-4.4.0-130-generic : Depends: linux-image-4.4.0-130-generic but it is not installed
linux-image-extra-4.4.0-131-generic : Depends: linux-image-4.4.0-131-generic but it is not installed
linux-image-generic : Depends: linux-image-4.4.0-131-generic but it is not installed
E: Unmet dependencies. Try using -f.


When I run -f install:



agiles@agiles-23-1015:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-124 linux-headers-4.4.0-124-generic linux-headers-4.4.0-128 linux-headers-4.4.0-128-generic linux-headers-4.4.0-130
linux-headers-4.4.0-130-generic linux-image-4.4.0-124-generic linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-extra-4.4.0-124-generic
linux-image-extra-4.4.0-128-generic linux-image-extra-4.4.0-130-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-4.4.0-131-generic
Suggested packages:
fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools
The following NEW packages will be installed:
linux-image-4.4.0-128-generic linux-image-4.4.0-130-generic linux-image-4.4.0-131-generic
0 upgraded, 3 newly installed, 0 to remove and 194 not upgraded.
7 not fully installed or removed.
Need to get 0 B/66.4 MB of archives.
After this operation, 204 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 425417 files and directories currently installed.)
Preparing to unpack .../linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
Done.
Unpacking linux-image-4.4.0-131-generic (4.4.0-131.157) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-131-generic' to '/boot/vmlinuz-4.4.0-131-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-131-generic /boot/vmlinuz-4.4.0-131-generic
Preparing to unpack .../linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
Done.
Unpacking linux-image-4.4.0-128-generic (4.4.0-128.154) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-128-generic' to '/boot/vmlinuz-4.4.0-128-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-128-generic /boot/vmlinuz-4.4.0-128-generic
Preparing to unpack .../linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
Done.
Unpacking linux-image-4.4.0-130-generic (4.4.0-130.156) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-130-generic' to '/boot/vmlinuz-4.4.0-130-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-130-generic /boot/vmlinuz-4.4.0-130-generic
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-4.4.0-131-generic_4.4.0-131.157_amd64.deb
/var/cache/apt/archives/linux-image-4.4.0-128-generic_4.4.0-128.154_amd64.deb
/var/cache/apt/archives/linux-image-4.4.0-130-generic_4.4.0-130.156_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)






package-management dependencies apport






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 17 '18 at 13:53









N0rbert

24.4k851115




24.4k851115










asked Jul 17 '18 at 13:50









Chester McNallyChester McNally

1




1








  • 1





    Your disk is full. You need to free up some space to clean things up, strange as that may seem.

    – Jos
    Jul 17 '18 at 14:27













  • Try installing BleachBit from the Ubuntu Software Centre to free up some space

    – Graham
    Jul 17 '18 at 14:39






  • 1





    @Graham .. I can't stop laughing. If apt doesn't work because the disk is full, Software Center won't work either.

    – Soren A
    Jul 17 '18 at 16:11











  • @SorenA errr. good point. Hadn't thought of that. Case of fingers working faster than the grey cells methinks embarrassed

    – Graham
    Jul 17 '18 at 16:41














  • 1





    Your disk is full. You need to free up some space to clean things up, strange as that may seem.

    – Jos
    Jul 17 '18 at 14:27













  • Try installing BleachBit from the Ubuntu Software Centre to free up some space

    – Graham
    Jul 17 '18 at 14:39






  • 1





    @Graham .. I can't stop laughing. If apt doesn't work because the disk is full, Software Center won't work either.

    – Soren A
    Jul 17 '18 at 16:11











  • @SorenA errr. good point. Hadn't thought of that. Case of fingers working faster than the grey cells methinks embarrassed

    – Graham
    Jul 17 '18 at 16:41








1




1





Your disk is full. You need to free up some space to clean things up, strange as that may seem.

– Jos
Jul 17 '18 at 14:27







Your disk is full. You need to free up some space to clean things up, strange as that may seem.

– Jos
Jul 17 '18 at 14:27















Try installing BleachBit from the Ubuntu Software Centre to free up some space

– Graham
Jul 17 '18 at 14:39





Try installing BleachBit from the Ubuntu Software Centre to free up some space

– Graham
Jul 17 '18 at 14:39




1




1





@Graham .. I can't stop laughing. If apt doesn't work because the disk is full, Software Center won't work either.

– Soren A
Jul 17 '18 at 16:11





@Graham .. I can't stop laughing. If apt doesn't work because the disk is full, Software Center won't work either.

– Soren A
Jul 17 '18 at 16:11













@SorenA errr. good point. Hadn't thought of that. Case of fingers working faster than the grey cells methinks embarrassed

– Graham
Jul 17 '18 at 16:41





@SorenA errr. good point. Hadn't thought of that. Case of fingers working faster than the grey cells methinks embarrassed

– Graham
Jul 17 '18 at 16:41










2 Answers
2






active

oldest

votes


















1














You likely have a separate /boot partition, or a very small root partition. Unfortunately, the Ubuntu upgrade does not automatically remove kernels. As a result, is space is limited, it may fill up, possible to the extent that you cannot anymore use the apt tools to remove old kernels.



If you have a single partition for Ubuntu that contains both system and data (your Home folder) then just temporarily move data away so the apt tools have disk space to work. Otherwise, read on.




  • First attempt to directly delete files related to your oldest kernel from the /boot directory. See the accepted answer in this Askbuntu question. This should free sufficient space on /boot to have the rest of the cleaning done by the apt tools.

  • Then complete your interrupted installation using the command sudo apt-get -f install. This should install your latest kernel and bring your packages again in a consistent state.

  • After that, use sudo apt autoremove to clean out the remaining old kernels automatically, except the one but last kernel.


If all works, remember to regularly issue a 'sudo apt autoremove'. This is not done automatically in Ubuntu, unfortunately.






share|improve this answer































    1














    This is a bit of an old question, however... As @vanadium mentioned, you are likely out of space in the /boot partition. Thus, a cleaning is in order.



    My way of cleaning up boot is like so:



    cd /boot
    sudo find . -maxdepth 1 -not -type d -not -name "*-4.4.0-116-*" -delete


    Replace 4.4.0-116 with the current kernel being used. You can determine that with uname -r. In this case 4.4.0-116 was the current kernel on a server I was cleaning.



    P.S. Do not forgot to update grub.



    sudo update-grub






    share|improve this answer








    New contributor




    Zakky is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.




















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1056914%2fi-cannot-upgrade-ubuntu-or-autoclean-due-to-the-inability-to-run-apt-get-f-ins%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      You likely have a separate /boot partition, or a very small root partition. Unfortunately, the Ubuntu upgrade does not automatically remove kernels. As a result, is space is limited, it may fill up, possible to the extent that you cannot anymore use the apt tools to remove old kernels.



      If you have a single partition for Ubuntu that contains both system and data (your Home folder) then just temporarily move data away so the apt tools have disk space to work. Otherwise, read on.




      • First attempt to directly delete files related to your oldest kernel from the /boot directory. See the accepted answer in this Askbuntu question. This should free sufficient space on /boot to have the rest of the cleaning done by the apt tools.

      • Then complete your interrupted installation using the command sudo apt-get -f install. This should install your latest kernel and bring your packages again in a consistent state.

      • After that, use sudo apt autoremove to clean out the remaining old kernels automatically, except the one but last kernel.


      If all works, remember to regularly issue a 'sudo apt autoremove'. This is not done automatically in Ubuntu, unfortunately.






      share|improve this answer




























        1














        You likely have a separate /boot partition, or a very small root partition. Unfortunately, the Ubuntu upgrade does not automatically remove kernels. As a result, is space is limited, it may fill up, possible to the extent that you cannot anymore use the apt tools to remove old kernels.



        If you have a single partition for Ubuntu that contains both system and data (your Home folder) then just temporarily move data away so the apt tools have disk space to work. Otherwise, read on.




        • First attempt to directly delete files related to your oldest kernel from the /boot directory. See the accepted answer in this Askbuntu question. This should free sufficient space on /boot to have the rest of the cleaning done by the apt tools.

        • Then complete your interrupted installation using the command sudo apt-get -f install. This should install your latest kernel and bring your packages again in a consistent state.

        • After that, use sudo apt autoremove to clean out the remaining old kernels automatically, except the one but last kernel.


        If all works, remember to regularly issue a 'sudo apt autoremove'. This is not done automatically in Ubuntu, unfortunately.






        share|improve this answer


























          1












          1








          1







          You likely have a separate /boot partition, or a very small root partition. Unfortunately, the Ubuntu upgrade does not automatically remove kernels. As a result, is space is limited, it may fill up, possible to the extent that you cannot anymore use the apt tools to remove old kernels.



          If you have a single partition for Ubuntu that contains both system and data (your Home folder) then just temporarily move data away so the apt tools have disk space to work. Otherwise, read on.




          • First attempt to directly delete files related to your oldest kernel from the /boot directory. See the accepted answer in this Askbuntu question. This should free sufficient space on /boot to have the rest of the cleaning done by the apt tools.

          • Then complete your interrupted installation using the command sudo apt-get -f install. This should install your latest kernel and bring your packages again in a consistent state.

          • After that, use sudo apt autoremove to clean out the remaining old kernels automatically, except the one but last kernel.


          If all works, remember to regularly issue a 'sudo apt autoremove'. This is not done automatically in Ubuntu, unfortunately.






          share|improve this answer













          You likely have a separate /boot partition, or a very small root partition. Unfortunately, the Ubuntu upgrade does not automatically remove kernels. As a result, is space is limited, it may fill up, possible to the extent that you cannot anymore use the apt tools to remove old kernels.



          If you have a single partition for Ubuntu that contains both system and data (your Home folder) then just temporarily move data away so the apt tools have disk space to work. Otherwise, read on.




          • First attempt to directly delete files related to your oldest kernel from the /boot directory. See the accepted answer in this Askbuntu question. This should free sufficient space on /boot to have the rest of the cleaning done by the apt tools.

          • Then complete your interrupted installation using the command sudo apt-get -f install. This should install your latest kernel and bring your packages again in a consistent state.

          • After that, use sudo apt autoremove to clean out the remaining old kernels automatically, except the one but last kernel.


          If all works, remember to regularly issue a 'sudo apt autoremove'. This is not done automatically in Ubuntu, unfortunately.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jul 17 '18 at 15:04









          vanadiumvanadium

          6,84911431




          6,84911431

























              1














              This is a bit of an old question, however... As @vanadium mentioned, you are likely out of space in the /boot partition. Thus, a cleaning is in order.



              My way of cleaning up boot is like so:



              cd /boot
              sudo find . -maxdepth 1 -not -type d -not -name "*-4.4.0-116-*" -delete


              Replace 4.4.0-116 with the current kernel being used. You can determine that with uname -r. In this case 4.4.0-116 was the current kernel on a server I was cleaning.



              P.S. Do not forgot to update grub.



              sudo update-grub






              share|improve this answer








              New contributor




              Zakky is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.

























                1














                This is a bit of an old question, however... As @vanadium mentioned, you are likely out of space in the /boot partition. Thus, a cleaning is in order.



                My way of cleaning up boot is like so:



                cd /boot
                sudo find . -maxdepth 1 -not -type d -not -name "*-4.4.0-116-*" -delete


                Replace 4.4.0-116 with the current kernel being used. You can determine that with uname -r. In this case 4.4.0-116 was the current kernel on a server I was cleaning.



                P.S. Do not forgot to update grub.



                sudo update-grub






                share|improve this answer








                New contributor




                Zakky is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.























                  1












                  1








                  1







                  This is a bit of an old question, however... As @vanadium mentioned, you are likely out of space in the /boot partition. Thus, a cleaning is in order.



                  My way of cleaning up boot is like so:



                  cd /boot
                  sudo find . -maxdepth 1 -not -type d -not -name "*-4.4.0-116-*" -delete


                  Replace 4.4.0-116 with the current kernel being used. You can determine that with uname -r. In this case 4.4.0-116 was the current kernel on a server I was cleaning.



                  P.S. Do not forgot to update grub.



                  sudo update-grub






                  share|improve this answer








                  New contributor




                  Zakky is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.










                  This is a bit of an old question, however... As @vanadium mentioned, you are likely out of space in the /boot partition. Thus, a cleaning is in order.



                  My way of cleaning up boot is like so:



                  cd /boot
                  sudo find . -maxdepth 1 -not -type d -not -name "*-4.4.0-116-*" -delete


                  Replace 4.4.0-116 with the current kernel being used. You can determine that with uname -r. In this case 4.4.0-116 was the current kernel on a server I was cleaning.



                  P.S. Do not forgot to update grub.



                  sudo update-grub







                  share|improve this answer








                  New contributor




                  Zakky is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  share|improve this answer



                  share|improve this answer






                  New contributor




                  Zakky is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 2 hours ago









                  ZakkyZakky

                  111




                  111




                  New contributor




                  Zakky is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Zakky is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Zakky is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1056914%2fi-cannot-upgrade-ubuntu-or-autoclean-due-to-the-inability-to-run-apt-get-f-ins%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      GameSpot

                      connect to host localhost port 22: Connection refused

                      Getting a Wifi WPA2 wifi connection