I have a new FritzBox 7530, installed openWRT 23 and openWrt 24. I want ro encrypt my USB Harddrive, but I get this error:
Enter passphrase for /dev/sda1:
device-mapper: reload ioctl on sda1 (253:0) failed: No such file or directory
On my PC or on openWrt 19, there are no Problems. My chiphers are:
--type luks1 --cipher aes-cbc-essiv:sha256 /dev/sdX
That looks like that a cipher is missing?
OpenWrt is not finding the device at "/dev/sda", it probably has a different name here.
No ... when I do an other cipher, there are no errors ...
LUKS sadly includes quite a few host requirements into the encrypted container, so the resulting filesystem images aren't necessary movable between (too-) different systems (things like architecture, 32 bit vs 64 bit, endianess and RAM size).
I dont think so. I can encrypt the volume on i386 and amd64 and mips32 and on my raspberry pi1 with arm cpu.
On my lowest device, mips 32 with 500MHz and 128 MB ram, there are no problems.
We've had cases of that (here) in the past (I think in relation to the RAM size used on the host creating the luks container), but as I'm not using it myself, I've only followed in from the side-lines.
Plz tell me ... Why I can encrypt the device on a very old mips32 ( kernel 2.6 ) and I cant encrypt it on an arm cpu with 4 cores and 256 MB ram ( fritzbox 7530 ). I want to understand it.
Did you try it the other way round (creating the luks container on x86_64 with looots of RAM, opening it on a very resource constrained device)?
I am aware of this and have chosen a weak encryption. i can encrypt it on weak hardware !!!
I can do this:
cryptsetup luksFormat --type luks1 --cipher aes-cbc-essiv:sha256 /dev/sdX
No problem errors !!! But when I try to open it, I get the errors ...
I knew it !!!
This ist the trick !!!
opkg install kmod-crypto-essiv
I knew that a cipher was missing ...
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.