OMV in KVM (proxmox) - passthrough disk not visible for shared folders

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

    • OMV in KVM (proxmox) - passthrough disk not visible for shared folders

      Hi All,

      I'm planning to move my OMV server into a VM on a larger server, under KVM/QEMU/Proxmox. I have several ext4 disks on the physical OMV serer, full of data, and I'd like to use them directly with the OMV VM for performance and recoverability reasons (if all else fails, pull the disk out, read it in another PC!)

      I've set up a VM to test it and edited the qemu vm conf file to add the host path for an ext4 disk:

      Source Code

      1. virtio2: /dev/disk/by-id/ata-WDC_WD15EADS-00R6B0_WD-WCAVY0822713,size=1465138584K
      When I start OMV in that vm, it shows the disk - /dev/vda - and the filesystem - /dev/vda1. However, when I try to define a shared folder, there are no devices in the list to select from.

      I've tried defining the disk by various forms of its path, as a partition and as a whole disk, and as vm device virtio2, scsi1, ide1. None of the combinations has made OMV show the disk for shared folder creation. Looking at the OMV VM from the shell, I don't see any entry in /etc/fstab or any mount point under /media for the passthrough disk.
      I've tried running "omv-mkconf fstab" but that didn't change the fstab file. Something in OMV's config database doesn't seem to know that the disk exists, although parts of the UI do know.

      What's gone wrong here? How can I get that disk to be properly available in OMV?

      Thanks!

      Jeff
    • Did you have mounted the filesystem?
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • I don't pass threw disks to proxmox so I can't speak to performance. I manage the disks in proxmox because it gives more options. It's easy to increase the size and zfs is far more stable in proxmox if you want to use that. I am sure there are other advantages too.
      If you make it idiot proof, somebody will build a better idiot.
    • @votdev - Do you mean mount the disk in the VM, or in proxmox? OMV in the VM sees the filesystem and OMV manages the contents of fstab... I didn't expect to have to mount things manually and if I did, surely omv-mkconf would undo my changes next time the config is updated?

      donh - thanks, but I have specific reasons for not wanting all my data in a virtual disk file.
    • D'oh! Why did I not notice that button wasn't greyed?! Not one of my smarter days! Thank you!

      However... mounting it is throwing up an error when I apply the new config:

      Source Code

      1. Error #0:
      2. OMV\Exception: Failed to read file '/tmp/bgstatuscrW8da' (size=0). in /usr/share/php/openmediavault/json/file.inc:199
      3. Stack trace:
      4. #0 /usr/share/php/openmediavault/json/file.inc(214): OMV\Json\File->getContents()
      5. #1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(314): OMV\Json\File->read()
      6. #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(544): OMV\Rpc\ServiceAbstract->finalizeBgProcStatus('/tmp/bgstatuscr...', '', Object(OMV\Exception))
      7. #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
      8. #4 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(440): OMV\Rpc\ServiceAbstract->callMethodBg('getList', Array, Array)
      9. #5 [internal function]: OMVRpcServiceFileSystemMgmt->getListBg(Array, Array)
      10. #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      11. #7 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getListBg', Array, Array)
      12. #8 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('FileSystemMgmt', 'getListBg', Array, Array, 1)
      13. #9 {main}
      Display All
      Looks like it mounted, though; it's now there in the device list for shared folder creation.
    • Are you on 4.1.22? The mentioned error should be fixed since many versions.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • votdev wrote:

      Are you on 4.1.22? The mentioned error should be fixed since many versions.
      According the line numbers in the error strack trace it is NOT 4.1.22 (or at least one of the versions that fixes the size=0 error).
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit