If you run into this make sure when you are mounting and repairing in a
chroot via `cryptsetup open /dev/whatever mapper-name` that the `mapper-
name` matches what you have in your `/etc/crypttab`. You can get this by
booting from the LiveCD and manually mounting the encrypted partition.
Or try
for me, hack from comment #4 works only partially.
i indeed got cryptsetup binary included to initramfs, but the damn thing still
does not ask me LUKS password, so everytime i have to do type cryptsetup &
vgchange commands in initramfs shell to be able to resume normal boot.
--
You received
AFAICS this bug is still relevant as the check is still in place and putting
CRYPTSETUP=y in
/etc/initramfs-tools/initramfs.conf is still not enough.
I try to boot a btrfs on a RAID1 (dm) inside an encrypted partition.
For some reason, update-initramfs is not able to determine the
"canonical
I'm not sure why changing the entry in /etc/fstab would resolve the
issue of the missing passphrase query in the first place. /etc/fstab is
only read after successfully decrypting your encrypted file system and
any change in there will not be reflected at boot.
--
You received this bug
Ok I have booting working now. I can almost describe the steps...
I followed http://blog.nguyenvq.com/blog/2014/07/25/upgrading-
ubuntu-12-04-to-14-04-breaks-encrypted-lvm/ and created /etc/initramfs-
tools/conf.d/cryptroot (did not exist before creating). That solved the
issue. However, I
** Attachment added: "diff_21_22+forcecryptsetup"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1256730/+attachment/4661799/+files/diff_21_22+forcecryptsetup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I upgraded from 14.04 LTS to 16.04 LTS, and _after_ installing the next
new kernel (4.4.0-22) the new kernel's initrd.img did not have
cryptsetup anymore. 4.4.0-21 still had so I have continued to boot to it
for a week now.
I tried a lot of things before finding this bug, but it seems comment #4
** Attachment added: "diff_22_22+forcecryptsetup"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1256730/+attachment/4661800/+files/diff_22_22+forcecryptsetup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cryptsetup (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256730
Title:
/usr/share/initramfs-toos/hooks/cryptroot does not honour the
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256730
Title:
/usr/share/initramfs-toos/hooks/cryptroot does not honour the
I can confirm the fix in comment #4 worked for me as well.
I had a 12.04.5 system running with Full Disk Encryption (from initial
install). After upgrading to 14.04.1 and rebooting, the luks encrypted
root file system could not be unlocked. The system would prompt for the
password, but then throw
Indeed we recently found out that putting CRYPTSETUP=y in the /etc
/initramfs-tools/initramfs.conf is not sufficient to include cryptsetup
into the initramfs.
However e.g.:
$ cat ./usr/share/initramfs-tools/conf-hooks.d/forcecryptsetup
export CRYPTSETUP=y
Does include cryptsetup into the
[Expired for cryptsetup (Ubuntu) because there has been no activity for
60 days.]
** Changed in: cryptsetup (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 12/02/2013 04:04 AM, Steve Langasek wrote:
The problem is that update-initramfs does not put /sbin/cryptsetup
into initramfs. My root filesystem is unencrypted but I mount an
encrypted partition during boot, so I need cryptsetup in initramfs.
Why do you think you need cryptsetup in the
The problem is that update-initramfs does not put /sbin/cryptsetup
into initramfs. My root filesystem is unencrypted but I mount an
encrypted partition during boot, so I need cryptsetup in initramfs.
Why do you think you need cryptsetup in the initramfs for mounting an
encrypted filesystem
15 matches
Mail list logo
