Cryptsetup not able to luksOpen

[anonimou]

[BANANA PI PRO - SO running on SD]

 

So, on every system upgrade I do, I end up with something broken. Normally it won't boot because of some kernel misconfiguration or due the encrypted HDD that I use connected to it.

 

On the last upgrade the same occurred. However, normally, I can solve stuff by myself. This time I couldn't fix everything (yet). I think that the only solution would be me compiling the kernel myself.

 

First the system wouldn't boot. After a few kernel replacements, I could make it boot, kind of.

 

If I have my encrypted LUKS HDD connected to it, it will boot to some degree and hang in there forever. If I take it out and put it back on, the boot continues.

If I boot without the HDD, it will boot "normally".

 

So, the setup I'm using is that the HDD would be decrypted on boot time. What I think that is happening is that it is not able to decrypt and hangs in there asking for the password (which shouldn't be asked as I'm using a key). Once the HDD is removed, it won't try to decrypt anymore and proceed.

 

So, I think after messing for a while that the kernel was not compiled with the crypto module:

 

root@bananapipro:~$ sudo cryptsetup luksOpen /dev/sda1 sdX_crypt
Cannot initialize device-mapper. Is dm_mod kernel module loaded?

 

I've tried different kernels: 4.11, 4.14, 4.9, ... All on the 4.x didn't work. Before the upgrade, if I'm not mistaken, I was running 3.10.x . So, my question is if these new kernels (4.x) are not being compiled with it and how can I compile it myself?

 

Thanks

[anonimou]

I could fix this by installing this kernel:

 

https://apt.armbian.com/pool/main/l/linux-4.14.18-sunxi/

 

sudo dpkg -i linux*

 

It complained I didn't have busybox. Installed it and everything is back on business again.

 

Thanks for the great work Armbian!