Re: Bug#403426: kernel corrupts LUKS partition header on arm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



At Sat, 30 Dec 2006 14:13:42 +0100,
Martin Michlmayr <tbm@xxxxxxxxxx> wrote:
> 
> * Clemens Fruhwirth <clemens@xxxxxxxxxxxxx> [2006-12-30 11:50]:
> > > Is there anything else I should try?
> > > foobar:~# cryptsetup luksOpen /dev/sda5 x
> > > Enter LUKS passphrase:
> > > device-mapper: table: 254:0: crypt: Device lookup failed
> 
> Strange.  I haven't changed cryptsetup but now I don't get this
> message anymore.  I simply get:
> 
> foobar:~# cryptsetup luksOpen /dev/sdb2 x
> Enter LUKS passphrase:
> Enter LUKS passphrase:
> Enter LUKS passphrase:
> Command failed: No key available with this passphrase.
> 
> But I'm sure I've typed the passphrase correctly, and it works on my
> x86 box (on which I created the LUKS partition).

Does luksDump report the same things on both architecture?
--
Fruhwirth Clemens - http://clemens.endorphin.org 
for robots: sp4mtrap@xxxxxxxxxxxxx

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux