From mboxrd@z Thu Jan 1 00:00:00 1970 From: Clemens Fruhwirth Subject: Re: Bug#403426: kernel corrupts LUKS partition header on arm Date: Tue, 02 Jan 2007 18:00:07 +0100 Message-ID: <87odph5ppk.wl%clemens@endorphin.org> References: <20061217022906.2434.60658.reportbug@LKG8A754B.example.org> <20061220161529.GA10820@deprecation.cyrius.com> <87lkkrgej4.wl%clemens@endorphin.org> <20061229202434.GD23246@deprecation.cyrius.com> <87vejt64kc.wl%clemens@endorphin.org> <20061230131342.GF4981@deprecation.cyrius.com> Reply-To: device-mapper development Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20061230131342.GF4981@deprecation.cyrius.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Martin Michlmayr Cc: 403426@bugs.debian.org, dm-devel@redhat.com, Brian Brunswick List-Id: dm-devel.ids At Sat, 30 Dec 2006 14:13:42 +0100, Martin Michlmayr wrote: > > * Clemens Fruhwirth [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@endorphin.org