upgrade fails with unmet dependencies

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

upgrade fails with unmet dependencies

robert rottermann
Hi there,


on one of my live servers I wanted to do an apt upgrade.

It failed with an error, and now every attempt to upgrade fails.

Can somebody give me a pointer how to fix this?


thanks very much

robert


root@salome ~ # apt 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-81-generic : Depends: linux-image-4.4.0-81-generic but
it is not installed
  linux-image-generic : Depends: linux-image-4.4.0-81-generic but it is not
installed
                        Recommends: thermald but it is not installed
E: Unmet dependencies. Try using -f.

--------------------------------------------------------------------------------

root@salome ~ # 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-53 linux-headers-4.4.0-53-generic linux-headers-4.4.0-57
linux-headers-4.4.0-57-generic
   linux-headers-4.4.0-59 linux-headers-4.4.0-59-generic linux-headers-4.4.0-62
linux-headers-4.4.0-62-generic
   linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic linux-headers-4.4.0-66
linux-headers-4.4.0-66-generic
   linux-headers-4.4.0-72 linux-headers-4.4.0-72-generic linux-headers-4.4.0-77
linux-headers-4.4.0-77-generic
   linux-image-4.4.0-53-generic linux-image-4.4.0-57-generic
linux-image-4.4.0-59-generic
   linux-image-4.4.0-62-generic linux-image-4.4.0-64-generic
linux-image-4.4.0-66-generic
   linux-image-4.4.0-72-generic linux-image-4.4.0-77-generic
linux-image-extra-4.4.0-53-generic
   linux-image-extra-4.4.0-57-generic linux-image-extra-4.4.0-59-generic
linux-image-extra-4.4.0-62-generic
   linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-66-generic
linux-image-extra-4.4.0-72-generic
   linux-image-extra-4.4.0-77-generic
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
   linux-image-4.4.0-81-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-81-generic
0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded.
19 not fully installed or removed.
Need to get 0 B/21.9 MB of archives.
After this operation, 66.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up multiarch-support (2.23-0ubuntu9) ...
(Reading database ... 433146 files and directories currently installed.)
Preparing to unpack .../linux-image-4.4.0-81-generic_4.4.0-81.104_amd64.deb ...
Done.
Unpacking linux-image-4.4.0-81-generic (4.4.0-81.104) ...
dpkg: error processing archive
/var/cache/apt/archives/linux-image-4.4.0-81-generic_4.4.0-81.104_amd64.deb
(--unpack):
  cannot copy extracted data for './boot/vmlinuz-4.4.0-81-generic' to
'/boot/vmlinuz-4.4.0-81-generic.dpkg-new': failed to write (No space left on device)
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-81-generic
/boot/vmlinuz-4.4.0-81-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-81-generic
/boot/vmlinuz-4.4.0-81-generic
Errors were encountered while processing:
  /var/cache/apt/archives/linux-image-4.4.0-81-generic_4.4.0-81.104_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: upgrade fails with unmet dependencies

Colin Law
On 24 June 2017 at 14:09, robert rottermann <[hidden email]> wrote:
> Hi there,
>
>
> on one of my live servers I wanted to do an apt upgrade.
>
> It failed with an error, and now every attempt to upgrade fails.

Try
apt full-upgrade
that will install any new packages that need to be installed as part
of the upgrade, apt upgrade only upgrades existing installed packages.

Colin

>
> Can somebody give me a pointer how to fix this?
>
>
> thanks very much
>
> robert
>
>
> root@salome ~ # apt 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-81-generic : Depends: linux-image-4.4.0-81-generic
> but it is not installed
>  linux-image-generic : Depends: linux-image-4.4.0-81-generic but it is not
> installed
>                        Recommends: thermald but it is not installed
> E: Unmet dependencies. Try using -f.
>
> --------------------------------------------------------------------------------
>
> root@salome ~ # 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-53 linux-headers-4.4.0-53-generic
> linux-headers-4.4.0-57 linux-headers-4.4.0-57-generic
>   linux-headers-4.4.0-59 linux-headers-4.4.0-59-generic
> linux-headers-4.4.0-62 linux-headers-4.4.0-62-generic
>   linux-headers-4.4.0-64 linux-headers-4.4.0-64-generic
> linux-headers-4.4.0-66 linux-headers-4.4.0-66-generic
>   linux-headers-4.4.0-72 linux-headers-4.4.0-72-generic
> linux-headers-4.4.0-77 linux-headers-4.4.0-77-generic
>   linux-image-4.4.0-53-generic linux-image-4.4.0-57-generic
> linux-image-4.4.0-59-generic
>   linux-image-4.4.0-62-generic linux-image-4.4.0-64-generic
> linux-image-4.4.0-66-generic
>   linux-image-4.4.0-72-generic linux-image-4.4.0-77-generic
> linux-image-extra-4.4.0-53-generic
>   linux-image-extra-4.4.0-57-generic linux-image-extra-4.4.0-59-generic
> linux-image-extra-4.4.0-62-generic
>   linux-image-extra-4.4.0-64-generic linux-image-extra-4.4.0-66-generic
> linux-image-extra-4.4.0-72-generic
>   linux-image-extra-4.4.0-77-generic
> Use 'apt autoremove' to remove them.
> The following additional packages will be installed:
>   linux-image-4.4.0-81-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-81-generic
> 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded.
> 19 not fully installed or removed.
> Need to get 0 B/21.9 MB of archives.
> After this operation, 66.9 MB of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Setting up multiarch-support (2.23-0ubuntu9) ...
> (Reading database ... 433146 files and directories currently installed.)
> Preparing to unpack .../linux-image-4.4.0-81-generic_4.4.0-81.104_amd64.deb
> ...
> Done.
> Unpacking linux-image-4.4.0-81-generic (4.4.0-81.104) ...
> dpkg: error processing archive
> /var/cache/apt/archives/linux-image-4.4.0-81-generic_4.4.0-81.104_amd64.deb
> (--unpack):
>  cannot copy extracted data for './boot/vmlinuz-4.4.0-81-generic' to
> '/boot/vmlinuz-4.4.0-81-generic.dpkg-new': failed to write (No space left on
> device)
> 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-81-generic
> /boot/vmlinuz-4.4.0-81-generic
> run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-81-generic
> /boot/vmlinuz-4.4.0-81-generic
> Errors were encountered while processing:
>  /var/cache/apt/archives/linux-image-4.4.0-81-generic_4.4.0-81.104_amd64.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> --
> ubuntu-users mailing list
> [hidden email]
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: upgrade fails with unmet dependencies

Colin Law
In reply to this post by robert rottermann
Looking at it again though, I think the main problem may be (see below) ..

On 24 June 2017 at 14:09, robert rottermann <[hidden email]> wrote:
> ...
> Unpacking linux-image-4.4.0-81-generic (4.4.0-81.104) ...
> dpkg: error processing archive
> /var/cache/apt/archives/linux-image-4.4.0-81-generic_4.4.0-81.104_amd64.deb
> (--unpack):
>  cannot copy extracted data for './boot/vmlinuz-4.4.0-81-generic' to
> '/boot/vmlinuz-4.4.0-81-generic.dpkg-new': failed to write (No space left on
> device)

I think you have run out of disc space

Colin

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: upgrade fails with unmet dependencies

Karl Auer
In reply to this post by robert rottermann
On Sat, 2017-06-24 at 15:09 +0200, robert rottermann wrote:
> on one of my live servers I wanted to do an apt upgrade.
> It failed with an error, and now every attempt to upgrade fails.
> Can somebody give me a pointer how to fix this?

Looking at your logs, this jumps out:

> The following packages were automatically installed and are no longer
> required:
> [...]
> Use 'apt autoremove' to remove them.

So doing that would be a good idea. It might also help with this:

> [...]
> '/boot/vmlinuz-4.4.0-81-generic.dpkg-new': failed to write (No space
> left on device)

Means you have run out of disk space on /boot.

If your /boot is a separate partition, you will have to delete things
from that partition to make more room.

If, as is more likely, /boot is just a directory on a larger partition,
then you can make more room by deleting anything from anywhere off that
partition. well - not anything; obviously dekete only things you can do
without!

When you have made space, try again with -f. With any luck apt-get
should fix everything up for you.

Regards, K.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer ([hidden email])
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: A52E F6B9 708B 51C4 85E6 1634 0571 ADF9 3C1C 6A3A
Old fingerprint: E00D 64ED 9C6A 8605 21E0 0ED0 EE64 2BEE CBCB C38B



--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: upgrade fails with unmet dependencies

Ralf Mardorf-2
>The following packages were automatically installed and are no longer
>required:
>   linux-[snip]

Hi,

this is most likely the well known separated /boot partition issue.

As already pointed out by the messages and by Karl, running

  sudo apt autoremove

will remove those packages, resp.

  sudo apt autoremove --purge

see https://help.ubuntu.com/community/RemoveOldKernels , you perhaps
want to read "Automatic Maintenance".

Btw. if you don't have a very good reason to use a separated /boot
partition, simply move it to / and remove the /boot entry from fstab.

I'm using a separated /boot partition, just to avoid chainloading by my
bootloader of choice, "syslinux". At least to avoid chainloading,
you don't need it when using "grub".

Regards,
Ralf

--
Vote for apulse!
echo $(w3m https://aur.archlinux.org/packages/apulse |grep 'Votes:    ')
Votes: 74                         Updated: Sat Jun 24 18:28:33 CEST 2017


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: upgrade fails with unmet dependencies

robert rottermann
In reply to this post by Karl Auer
Thanks very much Karl, Colin, Ralf


On 24.06.2017 15:30, Karl Auer wrote:

> On Sat, 2017-06-24 at 15:09 +0200, robert rottermann wrote:
>> on one of my live servers I wanted to do an apt upgrade.
>> It failed with an error, and now every attempt to upgrade fails.
>> Can somebody give me a pointer how to fix this?
> Looking at your logs, this jumps out:
>
>> The following packages were automatically installed and are no longer
>> required:
>> [...]
>> Use 'apt autoremove' to remove them.
> So doing that would be a good idea. It might also help with this:
>
>> [...]
>> '/boot/vmlinuz-4.4.0-81-generic.dpkg-new': failed to write (No space
>> left on device)
> Means you have run out of disk space on /boot.
trying to autoremove the kernels produces the same error claiming that
dependencies are not met.
I tried to work trough: https://help.ubuntu.com/community/RemoveOldKernels

uname -r produces:
4.4.0-22-generic

however, when I try to delete one of the kernels that are listed as
autoremovable I get an error:

update-initramfs -d -k linux-image-4.4.0-57-generic
dpkg --purge linux-image-4.4.0-57-generic
dpkg: dependency problems prevent removal of linux-image-4.4.0-57-generic:
  linux-image-extra-4.4.0-57-generic depends on linux-image-4.4.0-57-generic.

dpkg: error processing package linux-image-4.4.0-57-generic (--purge):
  dependency problems - not removing
Errors were encountered while processing:
  linux-image-4.4.0-57-generic



what can I do next?
thanks
robert

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: upgrade fails with unmet dependencies

robert rottermann
In reply to this post by Ralf Mardorf-2
On 24.06.2017 18:28, Ralf Mardorf wrote:
> Btw. if you don't have a very good reason to use a separated /boot
> partition, simply move it to / and remove the /boot entry from fstab.

how do I do that?

can I just move copy its content to /bootX and then move /boot out of the way
and rename /bootX to /boot ?

thanks

robert


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: upgrade fails with unmet dependencies

Tom H-4
In reply to this post by robert rottermann
On Sun, Jun 25, 2017 at 12:49 PM, robert <[hidden email]> wrote:

>
> dpkg --purge linux-image-4.4.0-57-generic
> dpkg: dependency problems prevent removal of linux-image-4.4.0-57-generic:
>  linux-image-extra-4.4.0-57-generic depends on linux-image-4.4.0-57-generic.
> dpkg: error processing package linux-image-4.4.0-57-generic (--purge):
>  dependency problems - not removing
> Errors were encountered while processing:
>  linux-image-4.4.0-57-generic
>
> what can I do next?

dpkg --purge linux-image-4.4.0-57-generic linux-image-extra-4.4.0-57-generic
or
apt-get purge linux-image-4.4.0-57-generic linux-image-extra-4.4.0-57-generic

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: upgrade fails with unmet dependencies

Ralf Mardorf-2
In reply to this post by robert rottermann
On Sun, 25 Jun 2017 18:55:38 +0200, robert wrote:
>On 24.06.2017 18:28, Ralf Mardorf wrote:
>> Btw. if you don't have a very good reason to use a separated /boot
>> partition, simply move it to / and remove the /boot entry from
>> fstab.  
>
>how do I do that?
>
>can I just move copy its content to /bootX and then move /boot out of
>the way and rename /bootX to /boot ?

Once the kernel is loaded, /boot might not be important anymore, but
even if it should be possible to do this from the running install, I
would run a live media or another install, to edit this particular
install.

From a live media or another install you simply could use
"sudo cp -ai /mountpoint/boot /other_mountpoint/" to copy the /boot
partition to the root partition, without renaming.

After that you need to comment out the /boot mount entry in
"/other_mountpoint/etc/fstab".

--
Vote for apulse!
echo $(w3m https://aur.archlinux.org/packages/apulse |grep 'Votes:    ')
Votes: 75                         Updated: Sun Jun 25 23:03:04 CEST 2017


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: upgrade fails with unmet dependencies

Ralf Mardorf-2
PS:

Before you copy or move /boot, consider to post /etc/fstab to rule out
wrong ideas.


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: upgrade fails with unmet dependencies

Ralf Mardorf-2
On Sun, 25 Jun 2017 23:47:27 +0200, robert wrote:
>proc /proc proc defaults 0 0
>/dev/md/0 none swap sw 0 0
>/dev/md/1 /boot ext3 defaults 0 0
>/dev/md/2 / ext4 defaults 0 0

I don't know if there's something to consider regarding the
multiple device driver, but apart from this, the steps I described
should work without issues. Just in case, is there a special reason
why /boot is on ext3 and root is ext4?

--
Vote for apulse!
echo $(w3m https://aur.archlinux.org/packages/apulse |grep 'Votes:    ')
Votes: 75                         Updated: Sun Jun 25 23:59:44 CEST 2017


--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

solved: Re: upgrade fails with unmet dependencies

robert rottermann
On 26.06.2017 00:05, Ralf Mardorf wrote:

> On Sun, 25 Jun 2017 23:47:27 +0200, robert wrote:
>> proc /proc proc defaults 0 0
>> /dev/md/0 none swap sw 0 0
>> /dev/md/1 /boot ext3 defaults 0 0
>> /dev/md/2 / ext4 defaults 0 0
> I don't know if there's something to consider regarding the
> multiple device driver, but apart from this, the steps I described
> should work without issues. Just in case, is there a special reason
> why /boot is on ext3 and root is ext4?
>
finally using toms H's suggestion I could delete some kernels and then had
enough space to do the upgrade
robert



--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: solved: Re: upgrade fails with unmet dependencies

Tom H-4
On Mon, Jun 26, 2017 at 12:44 AM, robert <[hidden email]> wrote:

> On 26.06.2017 00:05, Ralf Mardorf wrote:
>> On Sun, 25 Jun 2017 23:47:27 +0200, robert wrote:
>>>
>>> proc /proc proc defaults 0 0
>>> /dev/md/0 none swap sw 0 0
>>> /dev/md/1 /boot ext3 defaults 0 0
>>> /dev/md/2 / ext4 defaults 0 0
>>
>> I don't know if there's something to consider regarding the multiple
>> device driver, but apart from this, the steps I described should work
>> without issues. Just in case, is there a special reason why /boot is
>> on ext3 and root is ext4?
>
> finally using toms H's suggestion I could delete some kernels and then
> had enough space to do the upgrade

Good!

Moving "/boot" to "/" isn't worth the hassle - and the empty unused partitions.

Also, you don't need "proc /proc proc defaults 0 0" in "etc/fstab",
unless "defaults" for "/proc" is different from "nodev,noexec,nosuid"
and you want to override the latter.

If you're using upstart, it's mounted by mountall (IIRC, using
"/lib/init/fstab").

If you're using systemd, IIRC, pid 1 has a mount_setup that mounts api
filesystems.

--
ubuntu-users mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
Loading...