On Wed, Aug 20, 2014 at 00:22:29 CEST, John Wells wrote: > Thanks for your response. This is the result of luksDump on the container: > > # cryptsetup luksDump /dev/FINALFRONTIER_VG/HOME_LV > Device /dev/FINALFRONTIER_VG/HOME_LV is not a valid LUKS device. Ah, sorry. Did not see that access completely failed. That means the header was at least partially overwritten. Can you post or send me a hex-dump of the first 1024 bytes of this device and the other one? Command to do so is, e.g. head -c 1024 /dev/FINALFRONTIER_VG/HOME_LV | hd This will not compromise your security. > I will try to find the time to recreate the entire scenario. Do you think > the current container I'm able to open is at risk of corruption as well? Yes. Something seems to be running amok. Another queston: After Fedora 20 told you both were not valid LUKS devices, could you still open the one in Ubuntu that you could open before? Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@xxxxxxxxxxx GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718 ---- A good decision is based on knowledge and not on numbers. - Plato _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
