LinuxQuestions.org - Problem with software center

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - Problem with software center (https://www.linuxquestions.org/questions/linux-newbie-8/problem-with-software-center-4175606392/)

Problem with software center

This is the code that it gives when I try and repair the software center:

installArchives() failed: (Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 371606 files and directories currently installed.)
Preparing to unpack .../linux-image-4.4.0-72-generic_4.4.0-72.93~14.04.1_amd64.deb ...
Done.
Unpacking linux-image-4.4.0-72-generic (4.4.0-72.93~14.04.1) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-72-generic_4.4.0-72.93~14.04.1_amd64.deb (--unpack):
cannot copy extracted data for './boot/System.map-4.4.0-72-generic' to '/boot/System.map-4.4.0-72-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-72-generic /boot/vmlinuz-4.4.0-72-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-72-generic /boot/vmlinuz-4.4.0-72-generic
Preparing to unpack .../linux-image-4.4.0-36-generic_4.4.0-36.55~14.04.1_amd64.deb ...
Done.
Unpacking linux-image-4.4.0-36-generic (4.4.0-36.55~14.04.1) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-36-generic_4.4.0-36.55~14.04.1_amd64.deb (--unpack):
cannot copy extracted data for './boot/System.map-4.4.0-36-generic' to '/boot/System.map-4.4.0-36-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-36-generic /boot/vmlinuz-4.4.0-36-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-36-generic /boot/vmlinuz-4.4.0-36-generic
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-4.4.0-72-generic_4.4.0-72.93~14.04.1_amd64.deb
/var/cache/apt/archives/linux-image-4.4.0-36-generic_4.4.0-36.55~14.04.1_amd64.deb
Error in function:
dpkg: dependency problems prevent configuration of linux-image-extra-4.4.0-72-generic:
linux-image-extra-4.4.0-72-generic depends on linux-image-4.4.0-72-generic; however:
Package linux-image-4.4.0-72-generic is not installed.

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

dpkg: error processing package linux-image-generic-lts-xenial (--configure):
dependency problems - leaving unconfigured
Setting up linux-image-extra-4.4.0-34-generic (4.4.0-34.53~14.04.1) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-34-generic /boot/vmlinuz-4.4.0-34-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-34-generic /boot/vmlinuz-4.4.0-34-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-34-generic

gzip: stdout: No space left on device
cpio: write error: Broken pipe
find: `standard output': Broken pipe
find: write error
E: mkinitramfs failure find 1 cpio 1 gzip 1
update-initramfs: failed for /boot/initrd.img-4.4.0-34-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-extra-4.4.0-34-generic (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-generic-lts-xenial:
linux-generic-lts-xenial depends on linux-image-generic-lts-xenial (= 4.4.0.72.59); however:
Package linux-image-generic-lts-xenial is not configured yet.

dpkg: error processing package linux-generic-lts-xenial (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-extra-4.4.0-36-generic:
linux-image-extra-4.4.0-36-generic depends on linux-image-4.4.0-36-generic; however:
Package linux-image-4.4.0-36-generic is not installed.

dpkg: error processing package linux-image-extra-4.4.0-36-generic (--configure):
dependency problems - leaving unconfigured

At first glance, I would say that you have filled up a file system and anything using that space is probably crashing, corrupting, will error out, or a combination of those. You may have to fix the space issue before you can fix anything else.

Quote:

Originally Posted by wpeckham (Post 5713470)

One way that you can clean up some space is remove the old versions of packages that are no longer needed. You can do that by opening a terminal and issuing this command:

sudo apt-get autoclean

------------------------
Steve Stites

I originally had a dual boot system set up with windows 7 and ubuntu 14.04 and eventually had tons of problems with windows so I deleted. But I originally only allocated a small amount of space for ubuntu. Now ubuntu is on the verge of being out of space. Is there anyway to increase space without removing ubuntu and re installing?

Quote:

Originally Posted by jailbait (Post 5713474)

Better to use sudo apt-get clean. Autoclean is pretty selective in what it removes.

However, even in doing this, you will no doubt come up against the space problem again very quickly. You need to give yourself a much larger breathing space.

Quote:

Originally Posted by qth89 (Post 5713476)

Yes there is (by grabbing space from the partition that contained the deleted Windows 7).

Can you please paste the output (in CODE tags) from:

Code:

sudo fdisk -l

That will allow us to determine what partitions you have set up and how big your disk is.

Quote:

Originally Posted by hydrurga (Post 5713480)

Yes there is (by grabbing space from the partition that contained the deleted Windows 7).

Can you please paste the output (in CODE tags) from:

Code:

sudo fdisk -l

That will allow us to determine what partitions you have set up and how big your disk is.

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000c4c19

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 499711 248832 83 Linux
/dev/sda2 501758 1953523711 976510977 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 501760 1953523711 976510976 83 Linux

Disk /dev/mapper/sda5_crypt: 999.9 GB, 999945142272 bytes
255 heads, 63 sectors/track, 121569 cylinders, total 1953017856 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/sda5_crypt doesn't contain a valid partition table

Disk /dev/mapper/ubuntu--vg-root: 991.3 GB, 991311167488 bytes
255 heads, 63 sectors/track, 120520 cylinders, total 1936154624 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/ubuntu--vg-root doesn't contain a valid partition table

Disk /dev/mapper/ubuntu--vg-swap_1: 8585 MB, 8585740288 bytes
255 heads, 63 sectors/track, 1043 cylinders, total 16769024 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/ubuntu--vg-swap_1 doesn't contain a valid partition table

Thanks. You can insert CODE tags easily in the Advanced Editor (highlight the text in question and click on the # symbol) like this:

Code:

Here is some code or output.

Can you also paste the output from the following commands:

Code:

df -h



sudo du -a / | sort -n -r | head -n 10

(the latter will take a while to run - ignore the warnings)

Thanks.

Quote:

Originally Posted by hydrurga (Post 5713492)

Thanks. You can insert CODE tags easily in the Advanced Editor (highlight the text in question and click on the # symbol) like this:

Code:

Here is some code or output.

Can you also paste the output from the following commands:

Code:

df -h



Filesystem                  Size  Used Avail Use% Mounted on

udev                        3.9G  4.0K  3.9G  1% /dev

tmpfs                      799M  1.3M  797M  1% /run

/dev/dm-1                  909G  15G  848G  2% /

none                        4.0K    0  4.0K  0% /sys/fs/cgroup

none                        5.0M    0  5.0M  0% /run/lock

none                        3.9G  545M  3.4G  14% /run/shm

none                        100M  40K  100M  1% /run/user

/dev/sda1                  236M  226M    0 100% /boot

/home/clinttorres/.Private  909G  15G  848G  2% /home/clinttorres



sudo du -a / | sort -n -r | head -n 10

du: cannot access ‘/run/user/1000/gvfs’: Permission denied
du: cannot access ‘/home/.ecryptfs/clinttorres/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWZqgWG97aE6CkQtVTC8O0BVbDqabwpQFhGjR5gdgNDfOOnRyUz2h-ZyYE--/ECRYPTFS_FNEK_ENCRYPTED.FWZqgWG97aE6CkQtVTC8O0BVbDqabwpQFhGjcnR5-P3nYAoFOn9vWWa41---/ECRYPTFS_FNEK_ENCRYPTED.FWZqgWG97aE6CkQtVTC8O0BVbDqabwpQFhGji6us0ji86TlovlDqucZ3Tk--/ECRYPTFS_FNEK_ENCRYPTED.FWZqgWG97aE6CkQtVTC8O0BVbDqabwpQFhGjQ2zrB0RMu9Q3wXDTmzegkE--/ECRYPTFS_FNEK_ENCRYPTED.FXZqgWG97aE6CkQtVTC8O0BVbDqabwpQFhGjdIro3rapw44z1DY72rZM4YJdU.d0s1UH48wI4mvj e.Q-’: No such file or directory
du: cannot access ‘/proc/2598/task/2672/fd/85’: No such file or directory
du: cannot access ‘/proc/2598/task/2858/fdinfo/85’: No such file or directory
du: cannot access ‘/proc/29115/task/29115/fd/4’: No such file or directory
du: cannot access ‘/proc/29115/task/29115/fdinfo/4’: No such file or directory
du: cannot access ‘/proc/29115/fd/3’: No such file or directory
du: cannot access ‘/proc/29115/fdinfo/3’: No such file or directory
24460146 /
17519184 /home
8769076 /home/.ecryptfs
8769072 /home/.ecryptfs/clinttorres
8769052 /home/.ecryptfs/clinttorres/.Private
8750104 /home/clinttorres
4110476 /home/.ecryptfs/clinttorres/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWZqgWG97aE6CkQtVTC8O0BVbDqabwpQFhGjOhbn-JlHED88LT7pb3QJrE--
4110476 /home/clinttorres/Downloads
4061872 /usr
2576216 /home/.ecryptfs/clinttorres/.Private/ECRYPTFS_FNEK_ENCRYPTED.FWZqgWG97aE6CkQtVTC8O0BVbDqabwpQFhGjOhbn-JlHED88LT7pb3QJrE--/ECRYPTFS_FNEK_ENCRYPTED.FYZqgWG97aE6CkQtVTC8O0BVbDqabwpQFhGjEhzgF7vaCk1Ua6fElLBhALo7VnKOYAFvvY3RHNGY Vd1hrszxHvmCcIDzjd7vl2kL

(the latter will take a while to run - ignore the warnings)

Thanks.

ghghghgh

Thanks. As you can see, the chokepoint appears to be your /boot directory in /dev/sda1, which at 236M is too small for the contents (or at least for the additional kernel you're trying to install into it (see post #1)).

Due to the rest of your system being encrypted LVM, probably the best approach would be to purge some of the old kernels from /boot.

So, could you please paste the output from:

Code:

dpkg -l '*linux-image-*'

so that we can see which kernels you have installed.

Also, can you paste the output from:

Code:

uname -a

so we can see which kernel you're currently running.

P.S. You may also want to edit your previous post to remove any references to your real name, if that is indeed it, to assure anonymity.

Quote:

Originally Posted by hydrurga (Post 5713502)

Code:

dpkg -l '*linux-image-*'

Code:

| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)

||/ Name          Version      Architecture Description

+++-==============-============-============-=================================

un  linux-image-3. <none>      <none>      (no description available)

ii  linux-image-4. 4.2.0-27.32~ amd64        Linux kernel image for version 4.

ii  linux-image-4. 4.2.0-36.42~ amd64        Linux kernel image for version 4.

ii  linux-image-4. 4.2.0-38.45~ amd64        Linux kernel image for version 4.

ii  linux-image-4. 4.2.0-42.49~ amd64        Linux kernel image for version 4.

ii  linux-image-4. 4.4.0-34.53~ amd64        Linux kernel image for version 4.

in  linux-image-4. <none>      amd64        (no description available)

in  linux-image-4. <none>      amd64        (no description available)

ii  linux-image-ex 4.2.0-27.32~ amd64        Linux kernel extra modules for ve

ii  linux-image-ex 4.2.0-36.42~ amd64        Linux kernel extra modules for ve

ii  linux-image-ex 4.2.0-38.45~ amd64        Linux kernel extra modules for ve

ii  linux-image-ex 4.2.0-42.49~ amd64        Linux kernel extra modules for ve

iF  linux-image-ex 4.4.0-34.53~ amd64        Linux kernel extra modules for ve

iU  linux-image-ex 4.4.0-36.55~ amd64        Linux kernel extra modules for ve

iU  linux-image-ex 4.4.0-72.93~ amd64        Linux kernel extra modules for ve

ii  linux-image-ge 4.2.0.42.34  amd64        Generic Linux kernel image

iU  linux-image-ge 4.4.0.72.59  amd64        Generic Linux kernel image

so that we can see which kernels you have installed.

Also, can you paste the output from:

Code:

uname -a

Code:

4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27 16:56:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

so we can see which kernel you're currently running.

P.S. You may also want to edit your previous post to remove any references to your real name, if that is indeed it, to assure anonymity.

jhjjjkk

^ simple enough, purge everything but the last.

Thanks. Just a quick note that the output from dpkg -l expands depending on how wide your terminal is, so you would get more (non-truncated) information on each line if you enlarge your terminal window.

Can you please do that and paste the info here so that we can see the full package names.

Quote:

Originally Posted by hydrurga (Post 5713512)

My bad here is the expanded version:

Code:

un  linux-image-3.0                              <none>                      <none>                      (no description available)

ii  linux-image-4.2.0-27-generic                  4.2.0-27.32~14.04.1        amd64                      Linux kernel image for version 4.2.0 on 64 bit x86 SMP

ii  linux-image-4.2.0-36-generic                  4.2.0-36.42~14.04.1        amd64                      Linux kernel image for version 4.2.0 on 64 bit x86 SMP

ii  linux-image-4.2.0-38-generic                  4.2.0-38.45~14.04.1        amd64                      Linux kernel image for version 4.2.0 on 64 bit x86 SMP

ii  linux-image-4.2.0-42-generic                  4.2.0-42.49~14.04.1        amd64                      Linux kernel image for version 4.2.0 on 64 bit x86 SMP

ii  linux-image-4.4.0-34-generic                  4.4.0-34.53~14.04.1        amd64                      Linux kernel image for version 4.4.0 on 64 bit x86 SMP

in  linux-image-4.4.0-36-generic                  <none>                      amd64                      (no description available)

in  linux-image-4.4.0-72-generic                  <none>                      amd64                      (no description available)

ii  linux-image-extra-4.2.0-27-generic            4.2.0-27.32~14.04.1        amd64                      Linux kernel extra modules for version 4.2.0 on 64 bit x86 SMP

ii  linux-image-extra-4.2.0-36-generic            4.2.0-36.42~14.04.1        amd64                      Linux kernel extra modules for version 4.2.0 on 64 bit x86 SMP

ii  linux-image-extra-4.2.0-38-generic            4.2.0-38.45~14.04.1        amd64                      Linux kernel extra modules for version 4.2.0 on 64 bit x86 SMP

ii  linux-image-extra-4.2.0-42-generic            4.2.0-42.49~14.04.1        amd64                      Linux kernel extra modules for version 4.2.0 on 64 bit x86 SMP

iF  linux-image-extra-4.4.0-34-generic            4.4.0-34.53~14.04.1        amd64                      Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP

iU  linux-image-extra-4.4.0-36-generic            4.4.0-36.55~14.04.1        amd64                      Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP

iU  linux-image-extra-4.4.0-72-generic            4.4.0-72.93~14.04.1        amd64                      Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP

ii  linux-image-generic-lts-wily                  4.2.0.42.34                amd64                      Generic Linux kernel image

iU  linux-image-generic-lts-xenial                4.4.0.72.59                amd64                      Generic Linux kernel image

Great, thanks.

You've got some semi-installed kernels in there, no doubt due to this problem. So, we'll get rid of those and previous kernels, leaving your current kernel and the preceding one as a fallback (the latter purely because the extras for your current kernel weren't fully installed):

Code:

sudo apt-get --purge autoremove linux-image-4.2.0-27-generic



sudo apt-get --purge autoremove linux-image-4.2.0-36-generic



sudo apt-get --purge autoremove linux-image-4.2.0-38-generic



sudo apt-get --purge autoremove linux-image-4.4.0-36-generic



sudo apt-get --purge autoremove linux-image-4.4.0-72-generic