I've been doing some disaster tests and ran into what I think is an issue.
I've got two identical freenas servers.
On Machine1 I created an encrypted ZFS Z2 Volume and set up the server for real-world use (Samba shares, joined AD, snapshots, etc). Works fine. If I reboot, it automatically re-mounts the volume even though its encrypted.
From the web gui on Machine1, I chose, System -> General -> Save Config
I then shut down Machine1.
On Machine2, I chose System -> General -> Upload Config and uploaded the config I saved from Machine1.
After reboot, I shut down Machine2. I then moved all the storage drives from Machine1 to Machine2 and booted it up.
It did not mount the volume, showing it in a "lock" state. Clicking the icon to unlock prompts to unlock. I select "ok", and it goes right back to the web gui with a status of "LOCKED". Is this by design?
I've got two identical freenas servers.
On Machine1 I created an encrypted ZFS Z2 Volume and set up the server for real-world use (Samba shares, joined AD, snapshots, etc). Works fine. If I reboot, it automatically re-mounts the volume even though its encrypted.
From the web gui on Machine1, I chose, System -> General -> Save Config
I then shut down Machine1.
On Machine2, I chose System -> General -> Upload Config and uploaded the config I saved from Machine1.
After reboot, I shut down Machine2. I then moved all the storage drives from Machine1 to Machine2 and booted it up.
It did not mount the volume, showing it in a "lock" state. Clicking the icon to unlock prompts to unlock. I select "ok", and it goes right back to the web gui with a status of "LOCKED". Is this by design?
Last edited: