search

OpenMediaVault-Plugin-Developers / openmediavault-zfs

OpenMediaVault plugin for zfs
74 stars 15 forks source link

Error creating new pool (OMV 3.0.59 on Proxmox 4.3 VM) #20

Closed hillsy closed 7 years ago

hillsy commented 7 years ago

I'm evaluating OMV at work for a ZFS-backed NFS & iSCSI server (I already use it at home in a different configuration).

I've installed it on our Proxmox VE 4.3 cluster and added some data disks. When I try to create a new ZFS pool I get the attached error.

The error seems to be the same whether I use the backports kernel or the PVE kernel. screenshot at 2017-01-04 16 32 46

luxflow commented 7 years ago

try changing device alias other than by Id, as I know virtualized hard disk (vda) have issues that doesn't show in /dev/disk/by-id/

hillsy commented 7 years ago

"By path" fails, "None" appears to succeed (a pool is created at least, I haven't tried doing much with it yet)

ryecoaaron commented 7 years ago

I didn't have any problem creating a 4 drive mirror pool on 3.0.59 running on Proxmox 4.4 using by-id. I used the same settings from your screenshot.

luxflow commented 7 years ago

maybe those drive driver isn't virtio or pci passthrough (SAS HBA), I think

hillsy commented 7 years ago

Here's the VM hardware setup.

We don't have any nodes on PVE 4.4 yet. If/when we do I'll see if the problem remains. screenshot_2017-01-05_14-53-48

ryecoaaron commented 7 years ago

I wouldn't think the pve 4.3 vs 4.4 issue would cause this but not sure. Your setup looks about the same other than you used scsi for the OS drive. Is the VM running the latest OMV 3.x?

luxflow commented 7 years ago

it is due to virtio, I tested it, virtio driver doesn't show in by-disk by-path

luxflow commented 7 years ago

also as I heard, zfs on virtual hard disk file is bad unless it is experimental SAS HBA passthrough or native is only correct way to use zfs