How can I get the name that was automatically assigned to the volume (as in
'sda5_crypt') ?
I've lost my cryptsetup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237556
Title:
cryptsetup removed
I too ran in to a problem after upgrading a luks full disk encrypted
12.04.5 system to 14.04.1. After successfully upgrading, upon reboot I
was asked for the luks password for the root system. After entering the
password, I see sever errors including /sbin/cryptsetup not found.
After doing
It actually is a bug in Ubuntu because:
1. The /etc/crypttab was autogenerated during the installation. I never touched
it before. The warning was always there.
2. A WARNING, in a file that actually has 1 valid cryptsetup line shouldn't
lead to NOT including the cryptsetup tool in the initrd
On Sun, Mar 16, 2014 at 11:52:11PM -, Andres Gomez wrote:
It actually is a bug in Ubuntu because:
1. The /etc/crypttab was autogenerated during the installation. I never
touched it before. The warning was always there.
In that case, it would be a bug in whatever method you used to
Just upgraded from 13.04 to 13.10.
Exactly the same problem with linux-image-3.11.0-19-generic
# lsinitramfs /boot/initrd.img-3.11.0-19-generic | grep cryptsetup
gives no results
However, I can boot with the older images:
# lsinitramfs /boot/initrd.img-3.8.0-35-generic | grep cryptsetup
OK, I've been able to solve this manually.
I had to add a new line in /etc/crypttab for the LUKS encrypted
partition that had my root system. I have another LUKS encrypted
partition for my SWAP and /tmp that was already present in
/etc/crypttab
In my case, to get the UUID
root@pomeron:~# blkid
If your /etc/crypttab did not include a line for the device that your
root filesystem is on, then this is a local configuration error, not a
bug in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Problem solved.
To install Ubuntu on encrypted partitions, the usual steps are: 1) boot
liveDVD and try Ubuntu. 2) manually mount encrypted partitions with a
cryptsetup command. 3) Launch the installer.
I've always typed something like this:
cryptsetup luksOpen $my_partition WHATEVER
It turns
Ok, marking as invalid then. Thanks!
** Changed in: cryptsetup (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237556
Title:
cryptsetup removed from
From term.log:
update-initramfs: Generating /boot/initrd.img-3.11.0-11-generic
cryptsetup: WARNING: invalid line in /etc/crypttab for red-dwarf -
cryptsetup: WARNING: invalid line in /etc/crypttab for red-dwarf -
Can you please paste your /etc/crypttab? Mine looks like this:
sda5_crypt
The contents of /etc/crypttab is:
lvm_crypt UUID=0c3f710d-9844-4145-a8f8-465c6d6be4f8 none luks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237556
Title:
cryptsetup removed from initrd.img on
What's red-dwarf then? Does generating initramfs now, include cryptsetup
it in? Are you booted off mounted cryptpartitions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237556
Title:
cryptsetup
red-dwarf is a previous LVM PV name. It looks like I have some cruft
left over from a previous installation in the file: /etc/initramfs-
tools/conf.d/cryptroot. I just deleted it.
I am booted into a backup installation (12.04) on a different hard disk.
I am unable / don't_know_how to boot into
** Changed in: cryptsetup (Ubuntu)
Assignee: (unassigned) = Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237556
Title:
cryptsetup removed from initrd.img on upgrade
** Tags added: raring2saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237556
Title:
cryptsetup removed from initrd.img on upgrade to 13.10
To manage notifications about this bug go to:
/var/log/dist-upgrade/main.log
** Attachment added: main.log
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1237556/+attachment/3869617/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: apt.log
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1237556/+attachment/3869621/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237556
Title:
** Attachment added: term.log
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1237556/+attachment/3869622/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237556
Title:
18 matches
Mail list logo
