Jails not starting automatically after reboot/unlocking of encrypted volume

[ovizii]

Just wondering whether someone can test this and confirm the behavior described below with an encrypted volume?

So this is what I do:

- restart freeNAS
- log in via webGui go to storage select my encrypted volume and click unlock
- in the unlock mask I see these options:
Restart services:

• AFP
• CIFS
• FTP
• iSCSI
• NFS
• WebDAV
• Jails/Plugins

and I have ticked all of them.
- after the unlocking is done, I visit my jails sections and all jails are stopped.
- I now have to manually start every single jail which is quite tedious.

I'm on FreeNAS-9.3-STABLE-201509022158

 

[cyberjock]

There used to be a bug in the ticketing system for this issue, but I'm not sure what the number is, the status, etc.

It sounds like its not fixed though.

 

[ovizii]

THX for the pointer, I searched for bugs and found this, sounds like it's the same issue:
https://bugs.freenas.org/issues/7155

I can live with it now that I know its a bug whic happarently (see quote below) won't be fixed any time soon.

just read this gem of a statement: Jordan Hubbard 4 months ago =>
Well, I hope you also understand that all of this is strong edge-case material. 99.99% of FreeNAS users don't actually have any need for encryption because they aren't keeping secrets on their machines worth protecting to that degree, or they protect the contents of their NAS by other (probably more effective) means...