[dm-crypt] /sbin/cryptsetup: not found on boot after Grub repair - manual mounting works
hughbragg at dodo.com.au
Sat May 21 20:58:48 CEST 2016
It sounds like you need to update-grub
Assuming your grub configurations haven't changed since the original
build, you're probably looking for something like this:
On 22/05/16 00:14, Aaron wrote:
> 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.
> 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
> Command failed
> cryptsetup: WARNING: failed to determine cipher modules to load for
> I asked for help here:
> but nobody has had any ideas so far.
> Any ideas would be greatly, greatly appreciated.
> Kind regards,
> dm-crypt mailing list
> dm-crypt at saout.de
More information about the dm-crypt