From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <htd+ml@fritha.org>
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Fri, 22 Aug 2014 07:30:33 +0200 (CEST)
Date: Fri, 22 Aug 2014 07:30:32 +0200
From: Heinz Diehl <htd+ml@fritha.org>
Message-ID: <20140822053032.GA8719@fritha.org>
References: <20140819195134.GB18215@tansi.org>
 <CADt3ZtscYzfFb2nhAfz8VYwMFf0jzWx8w5OzycfX2h7oaaPe9A@mail.gmail.com>
 <20140820090956.GA25262@tansi.org>
 <CADt3ZtscbX-rmMt++aXme9Oiu3sxiBW_MD_CGJM_b=t+iMaerQ@mail.gmail.com>
 <20140820211528.GA450@tansi.org>
 <CADt3Ztvq7OxX9Tn=k_anKkDXQ+viyXM6b8g+zQEc_yt=M96vSw@mail.gmail.com>
 <lt4vh4$uvc$1@ger.gmane.org>
 <CADt3Ztv0QKLAET_uo4cn06qi_z90jMVdfomJPbLH_rFN4PoTzw@mail.gmail.com>
 <53F61AA4.70309@freesources.org>
 <CADt3Ztsi2p_nA4h8mDeGanh3zr0RbLmi+qJ+t7NcBjt1QhTR=Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADt3Ztsi2p_nA4h8mDeGanh3zr0RbLmi+qJ+t7NcBjt1QhTR=Q@mail.gmail.com>
Subject: Re: [dm-crypt] "not a valid LUKS device" after distro change
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 21.08.2014, John Wells wrote: 

> The inconsistent behavior is really disconcerting.

Another possibility is that the software relevant to your problem is
patched different. Most of the distributions out there doesn't manage
to keep their fingers off the original sourcecode. This could have
introduced the behaviour you're encountering.