Thanks. How would I use this information to track back to a potential problem?
On Aug 21, 2014 10:41 AM, "Robert Nichols" <rnicholsNOSPAM@xxxxxxxxxxx> wrote:
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.
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
