Basic ZFS pool creation on LUKS encrypted volume fails

Darkshado · 21. Oktober 2019

Hello,

Using OMV 4.1.26-1 openmediavault-luksencryption 3.0.5 openmediavault-zfs 4.0.4

Created, then decrypted and mounted an LUKS device via the plugin, worked.

Tried creating a "basic" ZFS pool via the plugin, got the following error:

Code

red4zfs
Basic
By Id
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; zpool create "red4zfs" 2>&1' with exit code '2': missing vdev specification usage: create [-fnd] [-o property=value] ... [-O file-system-property=value] ... [-m mountpoint] [-R root] <pool> <vdev> ...
Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; zpool create  "red4zfs"   2>&1' with exit code '2': missing vdev specification
usage:
	create [-fnd] [-o property=value] ...
	    [-O file-system-property=value] ...
	    [-m mountpoint] [-R root] <pool> <vdev> ... in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/omvzfs/Utils.php(432): OMV\System\Process->execute(Array, 2)
#1 /usr/share/omvzfs/Zpool.php(576): OMVModuleZFSUtil::exec('zpool create  "...', Array, 2)
#2 /usr/share/openmediavault/engined/rpc/zfs.inc(149): OMVModuleZFSZpool::create(Object(OMVModuleZFSVdev), '')
#3 [internal function]: OMVRpcServiceZFS->addPool(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#5 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('addPool', Array, Array)
#6 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('ZFS', 'addPool', Array, Array, 1)
#7 {main}

Alles anzeigen

Any ideas?

Thanks,

Darkshado

cabrio_leo · 21. Oktober 2019

I am not absolutely sure, but I think I have heard that Luks encryption with ZFS is not (well) supported with OMV4. In OMV5 It should be supported natively (with a different kernel?).

There are several threads about this topic here at the forum regarding ZFS with Luks.

Maybe someone else may chime in?

subzero79 · 21. Oktober 2019

Is failing to pass the device mapper device to the cmd, have to look into that. You can try and create the pool in terminal as per zfs docs then the pool should be displayed at the zfs node.
Encrypted volumes then zfs mounts, this a recipe for disaster in terms of service usability. Services that depends on zfs data are going to fail at boot. unless you are familiar setting up the crypttab you will need local console access or kvm ipmi to decrypt drives at boot.
the luks plugin doesn’t set the crypttab.

subzero79 · 22. Oktober 2019

The problem is the parsing of the dm-x device type, is not accounted for in the regex that validates the devices and tries to find their id. Path also fails as the device mapper doesn't generate an entry for that. You should be able to create the pool using device alias None or create the pool in terminal

Jetzt mitmachen!