labula

Little update if anyone should still come across this: The option in the GUI is in fact not from the New Unlock Key for Encrypted Drive App, and instead an official implementation starting with Unraid 7.0

Hello everyone! I seem to have gotten myself into quite the situation. After setting up Vaultwarden a few months ago I decided to change the passwords that I had saved in Bitwarden and move them to my self hosted instance. I hesitated but decided to also change the password that I use to encrypt my drives and save that offline as well (with another backup in my KeePass). To do this I used the "Change encryption key" Option in the Disk Settings which comes with the New Unlock Key for Encrypted Drive App. That is where things went wrong. After entering the new password my system froze for a little while, before giving me a pop up that the process had failed for a few drives. I didn't know how my system would handle only some drives having a new password so I tried again, which had reduced the impacted drives down to one. After the third attempt all drives had successfully set a new password. I decided to stop my array to see if everything worked fine but realized I wasn't prompted to enter my password unless I restart my server. So I did. When I entered the new password all drives were mounted and unlocked except for one, which is my "main" drive. I figured maybe something didn't go through after all and tried the process once more. But nope the drive still did not unlock. I figured it was weird, and tried the old password, which worked for some drives but not the others. At this point I hoped I wasn't totally screwed (I was) and figured I'll just switch back to the old password and be okay with that for now. I tried to switch back and suddenly two drives and my SSDs didn't unlock. Then I realized that I most definitely was screwed at this point. I checked the LUKS headers and they seem to still exist and be intact. Naturally I didn't back those up beforehand after seeing no complaints on the Forum and naively thinking that I wouldn't run into any issues either in that case. Now I am trying to troubleshoot the possible issues that could have caused this. Since I switched only between those two passwords I am clinging onto hope that I am not totally lost just yet. I am hoping that someone with more experience than me has had a similar issue, or that maybe the script that the New Unlock Key for Encrypted Drive App uses simply has issues parsing the password or certain special characters that were interpreted weirdly, or needed escaping/escaped without me knowing. Can anyone save my sorry bum?