[dm-crypt] "not a valid LUKS device" after distro change
jbwellsiv at gmail.com
Thu Aug 21 17:55:48 CEST 2014
Thanks. How would I use this information to track back to a potential
On Aug 21, 2014 10:41 AM, "Robert Nichols" <rnicholsNOSPAM at comcast.net>
> 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
>> with a unresponsive machine. I hard reset, booted Ubuntu, but at that
>> *Ubuntu wouldn't recognize either partition, and both had the same "GNU
>> 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
>> mount it. /dev/FINALFRONTIER_VG/HOME_LV was still corrupted with the "GNU
>> 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
>> 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.
> dm-crypt mailing list
> dm-crypt at saout.de
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dm-crypt