Kindly Help - Upgrade issues

[Guest]

Dear All,
I am using KDE 4.14.2
Whenever I try to upgrade via muon, I am getting "Failed to Apply changes" and the message "An error occurred while applying changes" in muon. The details button shows no info.

When I try to upgrade through console, I am getting the below error.,

Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 308880 files and directories currently installed.)
Removing linux-image-extra-3.13.0-57-generic (3.13.0-57.95) ...
depmod: FATAL: could not load /boot/System.map-3.13.0-57-generic: No such file or directory
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-57-generic /boot/vmlinuz-3.13.0-57-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-57-generic /boot/vmlinuz-3.13.0-57-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-57-generic /boot/vmlinuz-3.13.0-57-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-57-generic
grep: /boot/config-3.13.0-57-generic: No such file or directory
depmod: WARNING: could not open /tmp/mkinitramfs_zIlV4s/lib/modules/3.13.0-57-generic/modules.order: No such file or directory
depmod: WARNING: could not open /tmp/mkinitramfs_zIlV4s/lib/modules/3.13.0-57-generic/modules.builtin: No such file or directory

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.13.0-57-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-57-generic (--remove):
subprocess installed post-removal script returned error exit status 1
Errors were encountered while processing:
linux-image-extra-3.13.0-57-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

I also deleted the cache folder though synaptic, and tried using synaptic.

Please help.,

Thank you
Sri

[NickStone]

It looks like the issue is with the 3.13 kernel. How did you install that? Was it part of the original installation?

Also have you tried the following command?

sudo apt-get update && apt-get dist-upgrade

[claydoh]

gzip: stdout: No space left on device

This is the key, probably. You may not have enough space on your disk to extract and process the packages

What is the output of the following command:

df -h

[Guest]

Thanks for the reply @nickstone, & @claydoh

I tried

sudo apt-get update && apt-get dist-upgrade
I am getting the error:

294 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
Need to get 54.0 MB/508 MB of archives.
After this operation, 48.4 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://in.archive.ubuntu.com/ubuntu/ trusty-proposed/main linux-image-3.13.0-57-generic amd64 3.13.0-57.95 [15.2 MB]
Get:2 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ trusty/main libxnvctrl0 amd64 352.21-0ubuntu0~xedgers14.04.1 [17.1 kB]
Get:3 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ trusty/main nvidia-settings amd64 352.21-0ubuntu0~xedgers14.04.1 [862 kB]
Get:4 http://in.archive.ubuntu.com/ubuntu/ trusty-proposed/main linux-image-extra-3.13.0-57-generic amd64 3.13.0-57.95 [36.7 MB]
Get:5 http://in.archive.ubuntu.com/ubuntu/ trusty/universe libjansson4 amd64 2.5-2 [25.2 kB]
Get:6 http://in.archive.ubuntu.com/ubuntu/ trusty-updates/universe p7zip amd64 9.20.1~dfsg.1-4+deb7u1build0.14.04.1 [297 kB]
Get:7 http://in.archive.ubuntu.com/ubuntu/ trusty-updates/universe p7zip-full amd64 9.20.1~dfsg.1-4+deb7u1build0.14.04.1 [903 kB]
Fetched 54.0 MB in 1min 6s (806 kB/s)
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 308881 files and directories currently installed.)
Preparing to unpack .../linux-image-3.13.0-57-generic_3.13.0-57.95_amd64.deb ...
Done.
Unpacking linux-image-3.13.0-57-generic (3.13.0-57.95) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-57-generic_3.13.0-57.95_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-3.13.0-57-generic' to '/boot/vmlinuz-3.13.0-57-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 3.13.0-57-generic /boot/vmlinuz-3.13.0-57-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-57-generic /boot/vmlinuz-3.13.0-57-generic
Preparing to unpack .../libapt-pkg4.12_1.0.1ubuntu2.8_amd64.deb ...
Unpacking libapt-pkg4.12:amd64 (1.0.1ubuntu2.8) over (1.0.1ubuntu2.6) ...
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-3.13.0-57-generic_3.13.0-57.95_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Also, When tried df -h


Filesystem Size Used Avail Use% Mounted on
/dev/mapper/kubuntu--vg-root 457G 63G 371G 15% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 1.9G 4.0K 1.9G 1% /dev
tmpfs 389M 1.4M 388M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1.9G 22M 1.9G 2% /run/shm
none 100M 20K 100M 1% /run/user
/dev/sda1 236M 228M 0 100% /boot


Thanks again

[Simon]

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

This device is full. Assuming you feel comfortable using the Partition editor, I would just resize the disk. There is a RISK of the process being interrupted due to power failure, you could lose the contents of your drive.

Edit: Quick question why is your boot area so small? I mean that is smaller than most thumb drives. Before you partition I think you might want to post the results of sudo fdisk -l

The return code will give us an idea of how your partitions are setup. For example;

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc7af4430

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63   782076329   391038133+  83  Linux
/dev/sda2       782086142   976771071    97342465    5  Extended
/dev/sda5       782086144   968763391    93338624   83  Linux
/dev/sda6       968765440   976771071     4002816   82  Linux swap / Solaris

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x954338a4

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1       163830870   976768064   406468597+   5  Extended
/dev/sdb2              63   163830869    81915403+  83  Linux
/dev/sdb5       163830933   976768064   406468566   83  Linux

Partition table entries are not in disk order

[claydoh]

You might also make some extra room by running
sudo apt-get autoremove

which will remove some older kernels and related bits, which should free up enough space to allow you to at least complete the update process. One of the updates is a kernel, and as noted by Simon, your /boot is full. Using the autoremove option will uninstall older kernels, leaving your current one and the last one by default, so as you still have a few extra ones around, this will clear up enough space for you.

[xennex81]

It was always said that boot partitions didn't need more than 250 meg. I used to have partitions that small, but kernels are big these days. I think 500M is recommended now? In any case deleting old kernels shouldn't be a problem (particularly if you have more than two).

[xennex81]

I believe in the past 250 meg was a recommended size? This may simply be the result of Kubuntu's default partitioning scheme (use whole disk with LVM). Deleting older kernels should not be a problem and is actually recommended. Perhaps 500 meg is a good default size now for the /boot? Kernels are huge these days.

[oshunluvr]

250MB is enough for about 5-6 generic kernels and all the grub stuff plus memtest.

Do uname -r to list the kernel you're using. Then do ls /boot to see what kernels you have installed. Then do sudo apt-get remove for each kernel you have installed except the one you're booting and the next earlier one.

Then re-try the update.

If you're going to use a /boot partition that small, you'll have to keep on top of the kernels you have. Never more than 3 is a good idea.

[vinnywright]

250MB is enough for about 5-6 generic kernels and all the grub stuff plus memtest.

Do uname -r to list the kernel you're using. Then do ls /boot to see what kernels you have installed. Then do sudo apt-get remove for each kernel you have installed except the one you're booting and the next earlier one.

Then re-try the update.

If you're going to use a /boot partition that small, you'll have to keep on top of the kernels you have. Never more than 3 is a good idea.

"sudo apt-get remove --purge" would be better ,,,,yes/no as --purge will remove the old config's as well.

VINNY