From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] "not a valid LUKS device" after distro change
Date: Thu, 21 Aug 2014 09:25:39 -0500 [thread overview]
Message-ID: <lt4vh4$uvc$1@ger.gmane.org> (raw)
In-Reply-To: <CADt3Ztvq7OxX9Tn=k_anKkDXQ+viyXM6b8g+zQEc_yt=M96vSw@mail.gmail.com>
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.
next prev parent reply other threads:[~2014-08-21 14:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 20:58 [dm-crypt] "not a valid LUKS device" after distro change John Wells
2014-08-19 19:51 ` Arno Wagner
2014-08-19 22:22 ` John Wells
2014-08-20 9:09 ` Arno Wagner
2014-08-20 16:18 ` John Wells
2014-08-20 21:15 ` Arno Wagner
2014-08-21 14:00 ` John Wells
2014-08-21 14:25 ` Robert Nichols [this message]
2014-08-21 15:55 ` John Wells
2014-08-21 16:13 ` Jonas Meurer
2014-08-21 20:46 ` John Wells
2014-08-21 22:54 ` Arno Wagner
2014-08-22 3:52 ` John Wells
2014-08-22 5:30 ` Heinz Diehl
2014-08-22 11:46 ` Arno Wagner
2014-08-22 9:08 ` Jonas Meurer
2014-08-22 11:55 ` Arno Wagner
2014-08-22 12:55 ` Jonas Meurer
2014-10-28 15:34 ` John Wells
2014-10-28 15:35 ` John Wells
2014-10-28 18:34 ` Arno Wagner
2014-10-28 23:03 ` Jonas Meurer
2014-10-29 0:57 ` Arno Wagner
2014-10-29 23:49 ` Sven Eschenberg
2014-10-30 0:37 ` John Wells
2014-08-21 17:01 ` Robert Nichols
2014-08-21 14:29 ` Arno Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='lt4vh4$uvc$1@ger.gmane.org' \
--to=rnicholsnospam@comcast.net \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.