Hey,
I've got a setup with one System SSD and two HDD's, one for Data, one for Backup, no RAID. On the SSD I installed Proxmox in which I've created a OpenVZ Container with a template for a minimal debian 8 installation.
Following the instructions here I installed OMV 2.1.1 on top of that by replacing kralizec with stoneburner in the first step described. During the installation/unpackaging of the the omv-installation I am asked something about the configuration of mdadm:
If the system's root file system is located on an MD array (RAID), it needs to be started early during the boot sequence. If it is located on a logical volume (LVM), which is on MD, all constituent arrays need to be started.
If you know exactly which arrays are needed to bring up the root file system, and you want to postpone starting all other arrays to a later point in the boot sequence, enter the arrays to start here. Alternatively, enter 'all' to simply start all available arrays.
If you do not need or want to start any arrays for the root file system, leave the answer blank (or enter 'none'). This may be the case if you are using kernel autostart or do not need any arrays to boot.
As I wrote above, I don't have any RAID, so I left the field blank resulting in the error message:
Choosing "all" results in the same error message.
Actually, I don't really know if this is my main problem, but I just wanna make sure you know of it.
After the installation finishes I am able to connect to the OMV GUI, that's fine. I have created a bind mount according to this, so I should be able to access a folder on my first HDD that is meant for OMV. But in the OMV GUI, if I go to the point filesystems, I get the following error:
Fehler #6000:
exception 'OMVException' with message 'Failed to get filesystems' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:77
Stack trace:
#0 [internal function]: OMVRpcServiceFileSystemMgmt->enumerateFilesystems(NULL, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(317): OMVRpcServiceAbstract->callMethod('enumerateFilesy...', NULL, Array)
#3 [internal function]: OMVRpcServiceFileSystemMgmt->getList(Array, Array)
#4 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#5 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getList', Array, Array)
#6 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'getList', Array, Array, 1)
#7 {main}
Alles anzeigen
There is something written about "Array", so I thought it might be related to the initial error I got during the installation process (that's why i mentioned it).
On the other hand, I also recognized that I don't see any HDD information inside the GUI, which is due to the virtualization, I guess. So I am wondering if there are some key points that I missed or maybe even some restrictions that cannot be overcome in my setup. If not, how can I solve this problem?
I am really thankful for any help. Let me know what else you need.
Best regards