I'm using OMV 3.0.72
I'm trying to learn the basics of proxmox, which is currently running as a VM under qemu/kvm as it supports nested virtualisation.
I created a OMV VM within proxmox with this config:
Code
root@pve:/etc/pve/qemu-server# cat 100.conf
balloon: 0
bootdisk: virtio0
cores: 4
cpu: IvyBridge
ide2: none,media=cdrom
memory: 1024
name: omv
net0: virtio=4A:9C:8B:BF:14:A1,bridge=vmbr0
numa: 0
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=27c942e0-2be8-401b-89e3-cb873a3ead68
sockets: 1
virtio0: local-lvm:vm-100-disk-1,size=5G
virtio2: /dev/disk/by-id/ata-QEMU_HARDDISK_QM00005,size=50G
virtio3: /dev/disk/by-id/ata-QEMU_HARDDISK_QM00007,size=50G
Alles anzeigen
I passed through the two proxmox drives to the OMV VM with the qm set command.
I can see three hdds in the OMV webUI - /dev/vd{a.b.c}
I can create EXT4 filesystems on /dev/vdb1 and /dev/vdc1 and mount them.
But when attempting to create a mirror RAID device, /dev/vdb and /dev/vdc do not appear - the device list is empty. They are mounted in the OMV VM:
Code
/dev/vdb1 on /srv/dev-disk-by-label-data1 type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/vdc1 on /srv/dev-disk-by-label-data2 type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
/dev/vda1 on /var/lib/docker/overlay2 type ext4 (rw,relatime,errors=remount-ro,data=ordered)
Not tried to create RAID at the CLI. Is this a known bug/limitation of OMV?