I've got a 4 disk encrypted zpool where two disks are redundant. Recently I started getting errors on my /dev/ada1 drive. I removed the drive in the second slot of the iXSystem's freenas mini, only to discover that it was /dev/ada6. :(
Storage -> Volumes -> trunk -> Volume Status showed that drive as removed even when I plugged the drive back in again. The only choice given to me from the web gui is "Replace" when I click on the drive - no option to just bring the drive back online, so I went ahead and "replaced" the drive with itself.
Now, according to the documentation, when dealing with encryption, I have to essentially re-do the encryption steps: Assign a passphrase, download the key, and create a recovery key.
When I attempted to assign a passphrase however, I got this message:
Of course, during all of this, the original drive I was getting errors from (/dev/ada1) decided to detach during the resilvering process.
So today, when looking at the Volume Status, the drive I had incorrectly removed shows "online" and the "bad" drive shows "removed."
My questions:
1. How can I determine if the passphrase I changed "stuck" and I'll be able to access this volume after a reboot?
2. If I do pull the wrong drive again, is there a way to bring the drive back to an online status without "replacing" it through the long resilvering process + passphrase + rekey process?
Storage -> Volumes -> trunk -> Volume Status showed that drive as removed even when I plugged the drive back in again. The only choice given to me from the web gui is "Replace" when I click on the drive - no option to just bring the drive back online, so I went ahead and "replaced" the drive with itself.
Now, according to the documentation, when dealing with encryption, I have to essentially re-do the encryption steps: Assign a passphrase, download the key, and create a recovery key.
When I attempted to assign a passphrase however, I got this message:
Code:
Feb 3 11:26:35 freenas manage.py: [middleware.exceptions:37] [MiddlewareError: Unable to set passphrase on gptid/52093a8a-3484-11e5-80f0-d050991b6355: geli: Cannot open gptid/52093a8a-3484-11e5-80f0-d050991b6355: No such file or directory.
Of course, during all of this, the original drive I was getting errors from (/dev/ada1) decided to detach during the resilvering process.
So today, when looking at the Volume Status, the drive I had incorrectly removed shows "online" and the "bad" drive shows "removed."
My questions:
1. How can I determine if the passphrase I changed "stuck" and I'll be able to access this volume after a reboot?
2. If I do pull the wrong drive again, is there a way to bring the drive back to an online status without "replacing" it through the long resilvering process + passphrase + rekey process?
Last edited: