Virtualbox installation fails - missing dependencies

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Virtualbox installation fails - missing dependencies

      Hey people!

      After I managed to get my OMV 2.x installation to grind to a stop I upgraded to OMV 3. Things have been quite smooth since, the only problem I have is I can't install virtualbox.
      Below, the error. I thought dependencies were automatically installed?

      Thanks for any advice.

      J.

      Source Code

      1. Reading package lists... Done
      2. Building dependency tree
      3. Reading state information... Done
      4. Some packages could not be installed. This may mean that you have
      5. requested an impossible situation or if you are using the unstable
      6. distribution that some required packages have not yet been created
      7. or been moved out of Incoming.
      8. The following information may help to resolve the situation:
      9. The following packages have unmet dependencies:
      10. openmediavault-virtualbox : Depends: phpvirtualbox but it is not going to be installed
      11. Depends: virtualbox-ext-pack but it is not installable or
      12. virtualbox-ext-pack-installer but it is not going to be installed
      13. E: Unable to correct problems, you have held broken packages.
      Display All
    • You need to either install the backports kernel (button to do that in omv-extras) or manually enable the backports repo. I recommend using the backports kernel.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Hi,

      I have a similar problem, I'm using BPO 4.9.0-0 witg OMVExtras installed, i get the following during the VirtualBOX plugin installation:

      Source Code

      1. Reading package lists...
      2. Building dependency tree...
      3. Reading state information...
      4. Some packages could not be installed. This may mean that you have
      5. requested an impossible situation or if you are using the unstable
      6. distribution that some required packages have not yet been created
      7. or been moved out of Incoming.
      8. The following information may help to resolve the situation:
      9. The following packages have unmet dependencies:
      10. openmediavault-virtualbox : Depends: linux-headers-686-pae but it is not installable or
      11. linux-headers-amd64 but it is not going to be installed
      12. >>> *************** Error ***************
      13. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; export DEBIAN_FRONTEND=noninteractive; apt-get --yes --force-yes --fix-missing --allow-unauthenticated --reinstall install openmediavault-virtualbox 2>&1': Reading package lists...
      Display All
      I have tried manually installing the packages but it's not able to install them
    • There seems to be something going on with some Debian repos. I didn't have a problem but others are.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • danieliod wrote:

      anything I can try?
      If you are a Debian developer, you could fix the repos :)
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I know that the 4.8 backport's kernel having issues with dependencies, at least on the ftp.debian mirror.

      I had the same issue as the OP on a new PowerEdge T330 build. Trying to recreate my current OMV setup on a new/larger hard drive.


      Source Code

      1. root@Radar:~# apt-get install linux-headers-4.8*
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. Note, selecting 'linux-headers-4.9.0-0.bpo.1-amd64' for regex 'linux-headers-4.8*'
      6. Note, selecting 'linux-headers-4.9.0-0.bpo.2-all' for regex 'linux-headers-4.8*'
      7. Note, selecting 'linux-headers-4.9.0-0.bpo.2-amd64' for regex 'linux-headers-4.8*'
      8. Note, selecting 'linux-headers-4.9.0-0.bpo.2-all-amd64' for regex 'linux-headers-4.8*'
      9. Note, selecting 'linux-headers-4.9.0-0.bpo.1-rt-amd64' for regex 'linux-headers-4.8*'
      10. Note, selecting 'linux-headers-4.8.0-2-common-grsec' for regex 'linux-headers-4.8*'
      11. Note, selecting 'linux-headers-4.9.0-0.bpo.2-common-rt' for regex 'linux-headers-4.8*'
      12. Note, selecting 'linux-headers-4.8.0-2-grsec-amd64' for regex 'linux-headers-4.8*'
      13. Note, selecting 'linux-headers-4.9.0-0.bpo.2-rt-amd64' for regex 'linux-headers-4.8*'
      14. Note, selecting 'linux-headers-4.9.0-0.bpo.2-common' for regex 'linux-headers-4.8*'
      15. Note, selecting 'linux-headers-4.8.0-0.bpo.2-all' for regex 'linux-headers-4.8*'
      16. Some packages could not be installed. This may mean that you have
      17. requested an impossible situation or if you are using the unstable
      18. distribution that some required packages have not yet been created
      19. or been moved out of Incoming.
      20. The following information may help to resolve the situation:
      21. The following packages have unmet dependencies:
      22. linux-headers-4.8.0-2-grsec-amd64 : Depends: linux-kbuild-4.8 but it is not installable
      23. E: Unable to correct problems, you have held broken packages.
      Display All

      ryecoaaron wrote:

      There seems to be something going on with some Debian repos. I didn't have a problem but others are.
      Which repo are you using?

      The post was edited 1 time, last by tx.canyon ().

    • tx.canyon wrote:

      Which repo are you using?
      My repos are having the same problem. I wasn't replicating the problem properly the first time.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!