From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane.org>
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu, 21 Aug 2014 16:41:03 +0200 (CEST)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <glkdd-dm-crypt@m.gmane.org>) id 1XKTJJ-0001Jf-GW
 for dm-crypt@saout.de; Thu, 21 Aug 2014 16:25:53 +0200
Received: from c-24-14-20-249.hsd1.il.comcast.net ([24.14.20.249])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Thu, 21 Aug 2014 16:25:53 +0200
Received: from rnicholsNOSPAM by c-24-14-20-249.hsd1.il.comcast.net with local
 (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Thu, 21 Aug 2014 16:25:53 +0200
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
Date: Thu, 21 Aug 2014 09:25:39 -0500
Message-ID: <lt4vh4$uvc$1@ger.gmane.org>
References: <CADt3ZttcrX5CzzE3oBKS9PqSqS4K=sgYBTvMUX4KvL_S2=rvbQ@mail.gmail.com>
 <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>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In-Reply-To: <CADt3Ztvq7OxX9Tn=k_anKkDXQ+viyXM6b8g+zQEc_yt=M96vSw@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 08/21/2014 09:00 AM, John Wells wrote:
> I will try what you say. To add to the weirdness, I came into work this morning
> with a unresponsive machine. I hard reset, booted Ubuntu, but at that point
> *Ubuntu wouldn't recognize either partition, and both had the same "GNU Parted
> Loopback 0" in the output of "head -c 1024 /volume | hd". Neither partition was
> recognized by luksDump. I panicked.
>
> Rebooted, and guess what? /dev/MORE_VG/MORE_LV was back to normal and I could
> mount it. /dev/FINALFRONTIER_VG/HOME_LV was still corrupted with the "GNU Parted
> Loopback 0" output.
>
> This makes no sense to me. How could the leading bits be different each time I
> booted up? Could datamapper be assigning the wrong device to the logical volume
> in some way? It just makes no sense.

You can run (as root) "dmsetup deps" on each device in /dev/mapper to see
the major and minor device numbers needed for each entry.

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.