cesman

Operator head space and timing...

I switch to encryption at the end of last year. Worked fine for a few weeks. But after a reboot, my passphase will no longer work. I've yet to find a solution. I wouldn't recommend encryption. I'd stick with XFS. Should I be able to resolve my issue, I'll send the time to copy all my data to XFS and get rid of encryption completely.

Well, I came across this post that indicated this issue was resolved with a workaround of using the keyfile. Unfortunately, the keyfile doesn't work for me. Here is log output: If I attempt to run one of the commands manually, I get: Any help would be appreciated.

Hello, So, after ending last year on an unRaid high (Converted all drives to encrypted XFS and added a second parity drive!), I seem to be starting off the year on a low. Last night, one of my fans started to make a loud noise. I decided to shut the system down and take a look at which fan was problematic later. I powered the system back up and found the faulty fan. I then log into web interface and enter my passphase to start the array. I didn't quite pay attention, looked at something else for a few minutes, came back to unRaid and I saw the array had not started. Odd! I'm sure I entered the passphase. and hit "Start". Did I enter the right one?! After multiple attempts and reboots, no go!?! No problem I thought. Let me pull out a drive from the array and see if I can mount it on my workstation (Arch Linux w/ Plasma Desktop). I did that and the drive is shown as encrypted in Dolphin. I clicked on it and entered the passphrase. Unfortunately, it errored with "Incorrect passphrase". While I'm not new to Linux, I'm new to using LUKS. Did some googling and attempted to use cryptsetup to see if I could get any more information. luksDump works and outputs relevant information but unfortunately, any attempt to manually mount the partition, results in "No key available with this passphrase.". Prior to posting, I search and some a few similar threads but they either had no solution or the thread couldn't be open. Has anyone come across this issue? Any known solution? Thanks and Happy New Year, cesman