In my case BIOS was updated recently, and seems there’s no new firmware releases for this SSD. So, kinda stuck right now.

I’ll have to try…but might be a bit until I get time to go digging into the PC again.

Thanks…I just updated the week prior to receiving the SSD, in order to be sure I didn’t have any compatibility issues…So I guess I’m SOL on that end.

Yes, I understand all this but…If I got the wrong password, I should, A) get some feedback that I have clicked Enter and attempted a login, and B) get feedback that my attempt failed, right? All I get is a frozen screen unresponsive to any input at all.

Nope. Full on original surface keyboard. Works on BIOS, works on Grub…and then on that specific step, no input is reflected on the screen. No keys being typed, no failed login message being shown, nothing reacts.

…I think you have something here. If I create a random password and save it via nano on a brand new file, and use this file as passphrase during the initial creation…it then doesn’t let me open the encrypted device. It says no key available with this passphrase. When you input the cryptsetup open, you’re only allowed to manually type the passphrase (it no longer accepts a file with the passphrase, I think). Curiously, both the file and the passphrase I type manually…are pasted from the clipboard from the same password randomly generated on bitwarden and then copied to the clipboard. And yet, it seems something doesn’t match.

EDIT: Seems when you ‘open’ with a file, the appropiate way is cryptsetup luksOpen /dev/sda encrypted --key-file /home/user/encryptedSD.txt

You have to add the file as a key file. Just adding the password to the file isn’t enough.

cryptsetup luksAddKey /home/user/EncryptedSD.txt /dev/sda

Thanks! I think you’re onto something here. SOrry what’s the purpose of adding the key? Does it get stored in cryptsetup’s internal storage so you never have to input it again?

They never give up. After a bill attempt is buried, a new one is prepared just weeks afterwards.