Hi,
I'm playing around with the ZFS / geli encryption of FreeNAS 8.3.1 BETA1 and discovered a problem with the plugin service.
I have a single ZFS Volume which uses geli to do the full disc encryption and installed the Plugin service as described in the documentation. So far everything works great. The jail comes up and I can install the plugins (e.g. minidlna).
The problem occures after reboot. During the startup process FreeNAS tries to start up the jail, however all required files are on encrypted ZFS Volume, which i have to unlock with my passphrase first. Restarting the plugin service doesn't do anything.
The workaround I found is that I have to disable the plugin service before reboot and manually enable it after startup.
Maybe there are other services which also require files during startup which are located on the encrypted volume. I've got to admit, I haven't checked :)
I'm playing around with the ZFS / geli encryption of FreeNAS 8.3.1 BETA1 and discovered a problem with the plugin service.
I have a single ZFS Volume which uses geli to do the full disc encryption and installed the Plugin service as described in the documentation. So far everything works great. The jail comes up and I can install the plugins (e.g. minidlna).
The problem occures after reboot. During the startup process FreeNAS tries to start up the jail, however all required files are on encrypted ZFS Volume, which i have to unlock with my passphrase first. Restarting the plugin service doesn't do anything.
The workaround I found is that I have to disable the plugin service before reboot and manually enable it after startup.
Maybe there are other services which also require files during startup which are located on the encrypted volume. I've got to admit, I haven't checked :)
