openmediavault-virtualbox problem

    • OMV 0.5

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

    • openmediavault-virtualbox problem

      Hello,

      I am running openmediavault sardaukar 0.5.60 Up to a couple of days ago everithing worked perfect. I installed by accident an old cups addon with the result that I could not use the webinterface anymore.
      I used the cleanupscript and I was able to login again.
      no I have a problem to install virtualbox, someting went wrong and I am stuck now.

      dpkg -l | grep virtualbox gives me:
      rH openmediavault-virtualbox 1.0.14 VirtualBox plugin for OpenMediaVault.
      rc virtualbox-4.2 4.2.18-88780~Debian~squeeze Oracle VM VirtualBox

      I tried to remove them trough apt-get with following result:
      apt-get purge virtualbox-4.3 openmediavault-virtualbox
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      Virtual packages like 'virtualbox-4.3' can't be removed
      The following packages will be REMOVED:
      openmediavault-virtualbox
      0 upgraded, 0 newly installed, 1 to remove and 24 not upgraded.
      1 not fully installed or removed.
      After this operation, 158 kB disk space will be freed.
      Do you want to continue [Y/n]? y
      (Reading database ... 33818 files and directories currently installed.)
      Removing openmediavault-virtualbox ...
      invoke-rc.d: unknown initscript, /etc/init.d/nginx not found.
      dpkg: error processing openmediavault-virtualbox (--remove):
      subprocess installed post-removal script returned error exit status 100
      configured to not write apport reports
      Processing triggers for openmediavault ...
      Restarting engine daemon ...
      Errors were encountered while processing:
      openmediavault-virtualbox
      E: Sub-process /usr/bin/dpkg returned an error code (1)

      anything I do (install or upgrade or uninstall) openmediavault-virtualbox makes it impossible to do so...

      apt-get upgrade
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      The following packages will be REMOVED:
      openmediavault-virtualbox
      The following packages will be upgraded:
      apache2 apache2-mpm-worker apache2-suexec apache2-utils apache2.2-bin apache2.2-common base-files dpkg file gnupg libcups2 libcurl3-gnutls libgnutls26 libmagic1
      libpixman-1-0 linux-base linux-image-2.6.32-5-amd64 openssh-client openssh-server php5-cgi php5-cli php5-common samba-common-bin tzdata
      24 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
      1 not fully installed or removed.
      Need to get 0 B/55.0 MB of archives.
      After this operation, 3,897 kB of additional disk space will be used.
      Do you want to continue [Y/n]? y
      Preconfiguring packages ...
      (Reading database ... 33818 files and directories currently installed.)
      Removing openmediavault-virtualbox ...
      invoke-rc.d: unknown initscript, /etc/init.d/nginx not found.
      dpkg: error processing openmediavault-virtualbox (--remove):
      subprocess installed post-removal script returned error exit status 100
      configured to not write apport reports
      Processing triggers for openmediavault ...
      Restarting engine daemon ...
      Errors were encountered while processing:
      openmediavault-virtualbox
      E: Sub-process /usr/bin/dpkg returned an error code (1)

      or

      Preconfiguring packages ...
      Fetched 55.0 MB in 11s (4913 kB/s)
      (Reading database ... 33827 files and directories currently installed.)
      Removing openmediavault-virtualbox ...
      invoke-rc.d: unknown initscript, /etc/init.d/nginx not found.
      dpkg: error processing openmediavault-virtualbox (--remove):
      subprocess installed post-removal script returned error exit status 100
      configured to not write apport reports
      Removing lsb-release ...
      Processing triggers for openmediavault ...

      Can anyone help me out?
      I have 2 virtual I need running again...

      thx a lot
      A.
    • You tried manually installing the omv 1.x plugin which does not work on omv 0.5.

      apt-get purge openmediavault-virtualbox phpvirtualbox
      apt-get clean
      apt-get install openmediavault-virtualbox
      omv 4.1.6 arrakis | 64 bit | 4.16 backports kernel | omvextrasorg 4.1.7
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • apt-get purge openmediavault-virtualbox phpvirtualbox gives me:
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      Virtual packages like 'phpvirtualbox' can't be removed
      The following packages will be REMOVED:
      openmediavault-virtualbox
      0 upgraded, 0 newly installed, 1 to remove and 24 not upgraded.
      1 not fully installed or removed.
      After this operation, 158 kB disk space will be freed.
      Do you want to continue [Y/n]? y
      (Reading database ... 33818 files and directories currently installed.)
      Removing openmediavault-virtualbox ...
      invoke-rc.d: unknown initscript, /etc/init.d/nginx not found.
      dpkg: error processing openmediavault-virtualbox (--remove):
      subprocess installed post-removal script returned error exit status 100
      configured to not write apport reports
      Processing triggers for openmediavault ...
      Restarting engine daemon ...
      Errors were encountered while processing:
      openmediavault-virtualbox
      E: Sub-process /usr/bin/dpkg returned an error code (1)

      tried it several times...

      Thx
      Arne
    • This is the problem with trying to install 1.x plugins that need nginx on omv 0.5 that uses apache. The uninstall may not work now. If it doesn't, try:

      rm -f /var/lib/dpkg/info/openmediavault-virtualbox.postrm
      apt-get purge openmediavault-postrm
      omv 4.1.6 arrakis | 64 bit | 4.16 backports kernel | omvextrasorg 4.1.7
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • Thx, that helped a lot!
      I got virtualbox runing now, but I have a corrupt filesystem on one disk now :(
      only device sdc is found bit no partitions or filesystems...
      No idea what happened...

      the filesystem was EXT4 and there is no sdc1 to be found ...

      mke2fs -n sdc
      mke2fs 1.41.12 (17-May-2010)
      sdc is entire device, not just one partition!
      Proceed anyway? (y,n) y
      Filesystem label=
      OS type: Linux
      Block size=4096 (log=2)
      Fragment size=4096 (log=2)
      Stride=0 blocks, Stripe width=0 blocks
      61054976 inodes, 244190646 blocks
      12209532 blocks (5.00%) reserved for the super user
      First data block=0
      Maximum filesystem blocks=4294967296
      7453 block groups
      32768 blocks per group, 32768 fragments per group
      8192 inodes per group
      Superblock backups stored on blocks:
      32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
      4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
      102400000, 214990848

      fsck.ext4 -n /dev/sdc
      e2fsck 1.41.12 (17-May-2010)
      fsck.ext4: Superblock invalid, trying backup blocks...
      fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc

      The superblock could not be read or does not describe a correct ext2
      filesystem. If the device is valid and it really contains an ext2
      filesystem (and not swap or ufs or something else), then the superblock
      is corrupt, and you might try running e2fsck with an alternate superblock:
      e2fsck -b 8193 <device>

      I kow that this an other problem so if I need to start a new thread let me know...

      Thx a lot
      A.
    • Oh, and fdisk can't find a partition table...

      fdisk -l /dev/sdc

      Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
      255 heads, 63 sectors/track, 121601 cylinders
      Units = cylinders of 16065 * 512 = 8225280 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disk identifier: 0x00000000

      Disk /dev/sdc doesn't contain a valid partition table

      Anyone know if this even can be fixed?
      Thx in advance and a Happy Christmas...
      A.
    • OMV uses partitions on individual disks. How was the filesystem on sdc created?
      omv 4.1.6 arrakis | 64 bit | 4.16 backports kernel | omvextrasorg 4.1.7
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • OMV always creates a partition on individual disks. If the partition is gone, the drive must be failing.
      omv 4.1.6 arrakis | 64 bit | 4.16 backports kernel | omvextrasorg 4.1.7
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • Beginning to think this is going to be a hopeless case...
      The Virtualbox addon is installed but won't start...

      when applying the configuration I get:
      Error
      #4000:
      exception 'OMVException' with message 'Failed to execute command 'sudo
      omv-mkconf virtualbox 2>&1': VBoxManage: error: Failed to create
      the VirtualBox object!
      VBoxManage: error: Code NS_BASE_STREAM_WOULD_BLOCK (0x80470007) - Stream
      operation would block (extended info not available)
      VBoxManage: error: Most likely, the VirtualBox COM server is not running
      or failed to start.' in
      /usr/share/openmediavault/engined/module/virtualbox.inc:72
      Stack trace:
      #0 /usr/share/openmediavault/engined/rpc/config.inc(178):
      OMVModuleVirtualBox->applyConfig()
      #1 [internal function]: OMVRpcServiceConfig->applyChanges(Array,
      Array)
      #2 /usr/share/php/openmediavault/rpcservice.inc(125):
      call_user_func_array(Array, Array)
      #3 /usr/share/openmediavault/engined/rpc/config.inc(253):
      OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
      #4 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array,
      Array)
      #5 /usr/share/php/openmediavault/rpcservice.inc(125):
      call_user_func_array(Array, Array)
      #6 /usr/share/php/openmediavault/rpc.inc(62):
      OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array)
      #7 /usr/sbin/omv-engined(495): OMVRpc::exec('Config', 'applyChangesBg',
      Array, Array, 1)
      #8 {main}

      The kernel headers are installed.
      When I open the virtual machines tab I get Could not connect to host (127.0.0.1:18083/)

      Stack trace:
      #0 /usr/share/openmediavault/engined/rpc/virtualbox.inc(162): vboxconnector->connect()
      #1 [internal function]: OMVRpcServiceVirtualBox->getMachines(Array, Array)
      #2 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      #3 /usr/share/php/openmediavault/rpc.inc(62): OMVRpcServiceAbstract->callMethod('getMachines', Array, Array)
      #4 /usr/sbin/omv-engined(495): OMVRpc::exec('VirtualBox', 'getMachines', Array, Array, 1)
      #5 {main}

      none of the vbox services seem to be running
      starting the vboxweb-service manually results in ...fail!

      I'm at an end...
    • Patience...

      Did you click the Fix Modules button in the settings page of the virtualbox plugin? Reboot after you do.
      omv 4.1.6 arrakis | 64 bit | 4.16 backports kernel | omvextrasorg 4.1.7
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • Yes, and tried it again to be sure.
      but this time I got an error at the end:
      Install build-essential
      Reading package lists...
      Building dependency tree...
      Reading state information...
      build-essential is already the newest version.
      0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      Recompile kernel module
      Stopping VirtualBox kernel modules ...done.
      Removing old VirtualBox pci kernel module ...done.
      Removing old VirtualBox netadp kernel module ...done.
      Removing old VirtualBox netflt kernel module ...done.
      Removing old VirtualBox kernel module ...done.
      Recompiling VirtualBox kernel modules ...done.
      Starting VirtualBox kernel modules ...done.
      Load module
      Restart vboxweb-service
      Starting VirtualBox web service ...fail!

      Rebooted to be sure but still the same...
    • ok, I started again:
      cleaned up:
      apt-get purge virtualbox-4.3 openmediavault-virtualbox
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      The following packages will be REMOVED:
      openmediavault-virtualbox* virtualbox-4.3*
      0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
      After this operation, 171 MB disk space will be freed.
      Do you want to continue [Y/n]? y
      (Reading database ... 59527 files and directories currently installed.)
      Removing openmediavault-virtualbox ...
      VBoxManage: error: Failed to create the VirtualBox object!
      VBoxManage: error: Code NS_BASE_STREAM_WOULD_BLOCK (0x80470007) - Stream operation would block (extended info not available)
      VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
      Purging configuration files for openmediavault-virtualbox ...
      dpkg: warning: while removing openmediavault-virtualbox, directory '/usr/local' not empty so not removed.
      Removing virtualbox-4.3 ...
      Stopping VirtualBox kernel modules ...done.
      Purging configuration files for virtualbox-4.3 ...
      Processing triggers for openmediavault ...
      Restarting engine daemon ...
      Updating file permissions ...
      Updating locale files ...

      rm /etc/default/openmediavault-virtualbox /etc/default/virtualbox
      userdel vbox
      groupdel vboxusers

      and reinstalled:

      apt-get install build-essential openmediavault-virtualbox
      Reading package lists... Done
      Building dependency tree
      Reading state information... Done
      build-essential is already the newest version.
      Recommended packages:
      libpulse0 libsdl-ttf2.0-0 dkms pdf-viewer
      The following NEW packages will be installed:
      openmediavault-virtualbox virtualbox-4.3
      0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
      Need to get 0 B/69.1 MB of archives.
      After this operation, 171 MB of additional disk space will be used.
      Preconfiguring packages ...
      Selecting previously deselected package virtualbox-4.3.
      (Reading database ... 58144 files and directories currently installed.)
      Unpacking virtualbox-4.3 (from .../virtualbox-4.3_4.3.20-96996~Debian~squeeze_amd64.deb) ...
      Selecting previously deselected package openmediavault-virtualbox.
      Unpacking openmediavault-virtualbox (from .../openmediavault-virtualbox_0.5.16_all.deb) ...
      Processing triggers for openmediavault ...
      Restarting engine daemon ...
      Updating file permissions ...
      Updating locale files ...
      Setting up virtualbox-4.3 (4.3.20-96996~Debian~squeeze) ...
      Adding group `vboxusers' (GID 114) ...
      Done.
      Stopping VirtualBox kernel modules ...done.
      Removing old VirtualBox pci kernel module ...done.
      Recompiling VirtualBox kernel modules ...done.
      Starting VirtualBox kernel modules ...done.
      Setting up openmediavault-virtualbox (0.5.16) ...
      Initial configuration.
      useradd: warning: the home directory already exists.
      Not copying any file from skel directory into it.
      Reloading web server config: apache2.
      --2014-12-24 02:08:04-- download.virtualbox.org/virtua…_Pack-4.3.20.vbox-extpack
      Resolving download.virtualbox.org... 137.254.120.26
      Connecting to download.virtualbox.org|137.254.120.26|:80... connected.
      HTTP request sent, awaiting response... 302 Moved Temporarily
      Location: dlc-cdn.sun.com/virtualbox/4.3…_Pack-4.3.20.vbox-extpack [following]
      --2014-12-24 02:08:04-- dlc-cdn.sun.com/virtualbox/4.3…_Pack-4.3.20.vbox-extpack
      Resolving dlc-cdn.sun.com... 62.4.254.115, 62.4.254.88
      Connecting to dlc-cdn.sun.com|62.4.254.115|:80... connected.
      HTTP request sent, awaiting response... 200 OK
      Length: 15945984 (15M) [application/x-virtualbox-vbox-extpack]
      Saving to: “/tmp/Oracle_VM_VirtualBox_Extension_Pack-4.3.20.vbox-extpack”

      100%[=================================================================>] 15,945,984 4.16M/s in 3.9s

      2014-12-24 02:08:08 (3.90 MB/s) - “/tmp/Oracle_VM_VirtualBox_Extension_Pack-4.3.20.vbox-extpack” saved [15945984/15945984]

      0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
      Successfully installed "Oracle VM VirtualBox Extension Pack".
      update-rc.d: using dependency based boot sequencing
      insserv: warning: current start runlevel(s) (empty) of script `openmediavault-virtualbox' overwrites defaults (2 3 4 5).
      insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `openmediavault-virtualbox' overwrites defaults (0 1 6).
      Processing triggers for openmediavault ...
      Restarting engine daemon ...
      Updating file permissions ...
      Updating locale files ...

      Did the fixmodule and restarted
      Still the same...

      more info:
      uname -a
      Linux ragnar-anchorage 3.2.0-0.bpo.4-amd64 #1 SMP Debian 3.2.63-2+deb7u2~bpo60+1 x86_64 GNU/Linux

      cat /etc/default/virtualbox
      # defaults for virtualbox
      # sourced by vboxweb-service on startup

      VBOXWEB_USER=vbox
      VBOXWEB_HOST=127.0.0.1
    • You cannot change the owner:group of the folder. The chown of the folder used for you virtual machines must be:

      vbox:vboxusers

      Chow the folder to fix it:

      chown -R vbox:vboxusers /pathtothefodler

      **Edit, I left off the s on vboxusers by accident. If you chowned alreadfy without the s you need to do it again,**

      Nothing openemediavault needs anything on this. You mess to much you break things worse.

      The post was edited 3 times, last by tekkb ().

    • Those are in fact the owners...
      Reinstalled again trough the webinterface but no difference...

      Error
      #4000:
      exception 'OMVException' with message 'Failed to execute command 'sudo
      omv-mkconf virtualbox 2>&1': VBoxManage: error: Failed to create
      the VirtualBox object!
      VBoxManage: error: Code NS_BASE_STREAM_WOULD_BLOCK (0x80470007) - Stream
      operation would block (extended info not available)
      VBoxManage: error: Most likely, the VirtualBox COM server is not running
      or failed to start.' in
      /usr/share/openmediavault/engined/module/virtualbox.inc:72
      Stack trace:
      #0 /usr/share/openmediavault/engined/rpc/config.inc(178):
      OMVModuleVirtualBox->applyConfig()
      #1 [internal function]: OMVRpcServiceConfig->applyChanges(Array,
      Array)
      #2 /usr/share/php/openmediavault/rpcservice.inc(125):
      call_user_func_array(Array, Array)
      #3 /usr/share/openmediavault/engined/rpc/config.inc(253):
      OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
      #4 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array,
      Array)
      #5 /usr/share/php/openmediavault/rpcservice.inc(125):
      call_user_func_array(Array, Array)
      #6 /usr/share/php/openmediavault/rpc.inc(62):
      OMVRpcServiceAbstract->callMethod('applyChangesBg', Array, Array)
      #7 /usr/sbin/omv-engined(495): OMVRpc::exec('Config', 'applyChangesBg',
      Array, Array, 1)
      #8 {main}
    • give output of this command:

      dpkg -l | grep openmediavault


      Also, what kernel are you using??? Did you upgrade to the backports kernel? It looks like you did above.
      In the plugin did you click on the button to fix(or update) modules for the backport kernel. Do this if you have not done it. It takes a bit to upgrade them. Then try uninstalling the plugin and reinstalling it again.

      The post was edited 3 times, last by tekkb ().