Hi, I have no idea what Ubuntu does in the initramfs, but this sounds like your initramfs was rebuilt without the cryptsetup binary. Just another reason why I do not like the initramfs: Everything gets hard to debug. I have done an LUKS-unlocking initramfs manually though for a server-installation that boots from memory-stick. Maybe reinstaling the package that does booting from encrypted root on Ubuntu will fix this. Alternatively, you may try to add it to your initramfs manually, including all libraries it uses. That may be a bit tricky though. As for diagnostics, there are some explanations on the web how to unpack an initramfs. You could check whether there is an /sbin/cryptestup in there. That is probably the easiest first step. Regards, Arno On Sat, May 21, 2016 at 16:14:04 CEST, Aaron wrote: > Hello, > > I would really appreciate any help to make my system boot properly > again. I can manually mount my encrypted partitions and they unlock > correctly, so I'm pretty sure that I haven't lost my data, but > something that used to work in the Ubuntu 16.04 boot process to > unlock and boot the partitions must have broken, as whenever I boot > now, typing my password no longer unlocks and boots Ubuntu. Instead > it says: > “cryptsetup: cryptsetup failed, bad password or options?” > > If I press escape and get to the console output, it says: > /scripts/local-top/cryptroot: line 1: /sbin/cryptsetup: not found > over and over. > > In case the history is relevant, I recently had to reinstall Windows > on a dual-boot machine. That meant that I had to use boot repair to > get my Grub back. I now have what seems to be a working Grub, but > when I boot into Ubuntu and enter my password into the “Please > unlock disk sda6_crypt”, it fails as described. > http://paste.ubuntu.com/16443425/ > was the output of the boot-repair reconfiguration of Grub. > > I booted in with a live CD and chrooted into my installation. I did > an apt-get update and apt-get upgrade and I see the following in the > output: > Processing triggers for initramfs-tools (0.122ubuntu8) ... > update-initramfs: Generating /boot/initrd.img-4.4.0-22-generic > device-mapper: table ioctl on sda6_crypt failed: No such device or > address > Command failed > cryptsetup: WARNING: failed to determine cipher modules to load for > sda6_crypt > > I asked for help here: https://answers.launchpad.net/ubuntu/+source/cryptsetup/+question/293750 > but nobody has had any ideas so far. > > Any ideas would be greatly, greatly appreciated. > > Kind regards, > > Aaron > _______________________________________________ > dm-crypt mailing list > dm-crypt@xxxxxxxx > http://www.saout.de/mailman/listinfo/dm-crypt -- Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@xxxxxxxxxxx GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718 ---- A good decision is based on knowledge and not on numbers. -- Plato If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
