From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ; Thu, 21 Aug 2014 19:01:46 +0200 (CEST) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XKVjz-0004NI-MF for dm-crypt@saout.de; Thu, 21 Aug 2014 19:01:35 +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 ; Thu, 21 Aug 2014 19:01:35 +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 ; Thu, 21 Aug 2014 19:01:35 +0200 From: Robert Nichols Date: Thu, 21 Aug 2014 12:01:17 -0500 Message-ID: References: <20140819195134.GB18215@tansi.org> <20140820090956.GA25262@tansi.org> <20140820211528.GA450@tansi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: Subject: Re: [dm-crypt] "not a valid LUKS device" after distro change List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 08/21/2014 10:55 AM, John Wells wrote: > Thanks. How would I use this information to track back to a potential problem? > > On Aug 21, 2014 10:41 AM, "Robert Nichols" > wrote: > > 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. > You could at least see whether the same device numbers show up for the boots where the volume is working vs. the times when it is not working. If they are different, that would be an important clue. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.