[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
** Branch linked: lp:ubuntu/karmic/cryptsetup -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://bugs.launchpad.net/bugs/91405 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
cryptsetup (2:1.0.4+svn29-1ubuntu2) gutsy; urgency=low * modprobe dm-mod from cryptsetup.functions. (LP: #64625, #91405) -- Reinhard Tartler [EMAIL PROTECTED] Tue, 29 May 2007 13:31:39 +0200 ** Changed in: cryptsetup (Ubuntu) Status: Needs Info = Fix Released -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://bugs.launchpad.net/bugs/91405 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
I was wrong: sha1 didn't solved it really. I now have all modules loaded that i need (new ones loop, cbc and blkcipher) were missing and now it works one day and the other day not. Seems to me like some kind of race condition between loading the modules and crytosetups try to open the device. If i wait long enough before entering the password for the root partition it always works, if i am to fast most of the time it does not. I checked the code in my initrd and there is a call to udevsettle to wait until everything is ready, shouldn't it wait for loaded modules, too? -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://bugs.launchpad.net/bugs/91405 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
I can confirm that modprobe sha1 fixed the problem for me on feisty. However, my problem was that I couldn't *add* a key with luksAddKey - the luksFormat worked fine -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://bugs.launchpad.net/bugs/91405 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
Further to above, creating the device with --hash sha256 works too - a variant on the above problem. Curiously, a luksDump still shows Hash spec: sha1 though I don't know if it's related. -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://bugs.launchpad.net/bugs/91405 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
For me, loading the module sha1 solved the problem completely. Maybe anyone else can confirm that -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://bugs.launchpad.net/bugs/91405 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
OK, this is a usability and lack of documetation problem. You need to run **sudo** cryptsetup luksAddKey /dev/sdc3 and now it works fine... -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://bugs.launchpad.net/bugs/91405 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
Just had to reinstall feisty. Used a herd 5 CD and installed cryptsetup. Had a similar problem directly after installing cryptsetup but now after loading the modules listed above it's gone. But i am pretty sure that i had the modules loaded in edgy as well as i said above. So i'd say different bug from bug #64625 -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://bugs.launchpad.net/bugs/91405 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
Addon: [EMAIL PROTECTED]:/dev$ cryptsetup --version cryptsetup-luks 1.0.5 -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://bugs.launchpad.net/bugs/91405 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
Not sure if that is the same bug. I currently run feisty (kernel 2.6.20-14) and try to setup dm-crypt / LUKS So far I did jitter my harddisk with sudo dd if=/dev/urandom of=/dev/hda Then I did install cryptsetup -- sudo apt-get install cryptsetup hashalot Then I created a 160 GB partition: cfdisk /dev/hda Then I loaded the kernel modules: sudo modprobe aes dm-crypt dm_mod Then I tried to setup LUKS cryptsetup --verbose --verify-passphrase luksFormat /dev/hda1 but I only get this output: [EMAIL PROTECTED]:/dev$ sudo cryptsetup --verbose --verify-passphrase luksFormat /dev/hda1 WARNING! This will overwrite data on /dev/hda1 irrevocably. Are you sure? (Type uppercase yes): YES Enter LUKS passphrase: Verify passphrase: Command failed: Passphrases do not match [EMAIL PROTECTED]:/dev$ sudo cryptsetup --verbose --verify-passphrase luksFormat /dev/hda1 WARNING! This will overwrite data on /dev/hda1 irrevocably. Are you sure? (Type uppercase yes): YES Enter LUKS passphrase: Verify passphrase: Rendezvous with udev timed out for 'temporary-cryptsetup-6024'; stat failed: No such file or directory Failed to setup dm-crypt key mapping. Check kernel for support for the aes-cbc-essiv:sha256 cipher spec and verify that /dev/hda1 contains at least 133 sectors. Failed to write to key storage. Command failed. [EMAIL PROTECTED]:/dev$ I even loaded the ase-i586 module but that didn't change anything... I'm not sure if this belongs in here also. -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://bugs.launchpad.net/bugs/91405 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
I'm having the same problem in feisty. What I did and the error message: cryptsetup luksFormat /dev/sda2 WARNING! Daten auf /dev/sda2 werden unwiderruflich überschrieben. Are you sure? (Type uppercase yes): YES Enter LUKS passphrase: Verify passphrase: Failed to setup dm-crypt key mapping. Check kernel for support for the aes-cbc-essiv:sha256 cipher spec and verify that /dev/sda2 contains at least 133 sectors. Failed to write to key storage. Aufruf fehlgeschlagen. All modules are loaded, like aes, dm_crypt and dm_mod. The funny thing is that yesterday I had the same problem when trying to mount a crypt-formatted USB disk. Yesterday it didn't work, today it did! Now my USB disk is mounted, but I am not able to cryptsetup luksFormat an internal HD partition syslog says: Mar 31 16:01:02 hpsupercompi kernel: [ 8515.14] device-mapper: table: 254:1: crypt: Device lookup failed Mar 31 16:01:02 hpsupercompi kernel: [ 8515.14] device-mapper: ioctl: error adding target to table Mar 31 16:01:02 hpsupercompi kernel: [ 8515.144000] device-mapper: ioctl: device doesn't appear to be in the dev hash table. My version is the same as stated in the title, but without the ~edgy1 at the end. (it's in feisty, universe/admin) This seems to be the only show-stopper for using feisty as productive version. (which is not recommended, I know, but I love some of the new features, that's why I'm trying...) -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://launchpad.net/bugs/91405 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
CORRECTION OF THE ABOVE *blush* My fault. in feisty I don't have any errors anymore, I just thought it was an error, but everything works fine (uhm, I used the wrong partition...) I guess I thought it was an error because actually I _did_ have that external disk error yesterday, but it's really fixed today. (comments can't be edited or removed, can they!?) -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://launchpad.net/bugs/91405 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
I switched to feisty now and the problem is gone. (same crypted drive etc) So it really seems to be edgy + the backport package. -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://launchpad.net/bugs/91405 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
which is pretty surprising, since the feisty package and the one from edgy-backports are built from exactly the same source. (only difference is debian/changelog) -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://launchpad.net/bugs/91405 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
Does anyone know if this problem also affects feisty? Or Debian etch? The backport works fine here. I upgraded because I was unable to enter a passphrase on boot with the version in edgy. This issue was solved with the backport. Anyway... I wonder why people upgrading to a backport when the original package from edgy works fine on their systems... -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://launchpad.net/bugs/91405 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
Maybe that's a stupid question, but which log files am I supposed to have a look on? My crypt partition is mapped and mounted at bootup, but I can't find any detailed information in dmesg, syslog, or /var/log/boot on what happens whatsoever. -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://launchpad.net/bugs/91405 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91405] Re: fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1)
** Summary changed: - can't open crypted device using a keyfile (2:1.0.4+svn26-1ubuntu1~edgy1) + fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) -- fails to setup dm-crypt key mapping. (2:1.0.4+svn26-1ubuntu1~edgy1) https://launchpad.net/bugs/91405 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
