Open janfreddy opened 4 years ago
Also running raspberry pi 4b I am having the same issue. Happens right after I am prompted to enter the first passphrase. After I enter a passphrase and hit enter I get directed back to the Disk Selection Screen with an error (Error Formatting data partition (ext4)). Attempting to try it again I can see the terminal log with the following text.
[ 2531.566322] device-mapper: table: 254:0: crypt: error allocating crypto tfm device-mapper: reload ioctl on failed: No such file or directory Failed to setup dm-crypt key mapping for device /dev/mmcblk0p2. Check that kernel supports aes-xts-plain64 cipher (check system log for more info). Device /dev/mmcblk0p2 is not a valid LUKS device.
Thank you for any help!
I noticed that when doing an encryption on an older pi it prompts the formatting warning and asks you to respond with "yes". When I try the encryption on the pi 4 it goes straight to asking me to enter first passphrase. Going to try and find more information on missing files/ directory.
Has anyone solved this? I used to use berryboot on my PI3's to get encrypted sd cards, but I get the above error on the PI4....
I have not been able to get it to work through Berryboot. I was able to manually encrypt an sd card running on the PI4 using the walk-through on this link. https://github.com/johnshearing/PrivateKeyVault#setup-luks-full-disk-encryption
I am still trying to get the Berryboot to work becuase it's a lot more convenient.
Has anyone solved this? I used to use berryboot on my PI3's to get encrypted sd cards, but I get the above error on the PI4....
The kernel needs to be recompiled with support for the aes-xts-plain64 cipher. So I guess there is no easy solution, at least via berryboot. But the link from the previous poster provided a link for a solution without berryboot.
@maxnet i am also having this same issue on pi4
I'm also having the same issue. I'm also on raspberry pi 4.
I had the same problem when I used the downloaded zip file. However, it worked when I cloned the repo and build it myself. I believe the encryption was broken in the pi kernel when the package was build but it is fixed now.
@marcrossinyol , thanks for the tip. I'll try this.
I confirm, it works when building berryboot manually.
If I try to create a new encrypted drive or use my old encrypted drive I get the following error:
device mapper: table: 254:0 crypt: Error allocating crypto tfm device mapper: reload ioctl on failed: No such file or directory Failed to setup dm-crypt key mapping for device /dev/sda2. Check that kernel supports aes-xts-plain64 cipher (check syslog for more info).
Seems like the kernel does not support the required cipher. Can this be fixed or can I fix this myself? This does only affect my raspberry pi 4b with the newest berryboot version for raspberry pi 4 My raspberry pi 3b works fine with the newest berryboot version for raspberry pi 3.