If you cannot afford to lose the data, then surely you have a backup (see FAQ) and a header backup (see FAQ)? Having a single copy of vital data on an unreliable storage medium is not a good idea, encrypted or not. Now, if you really did luksFormat a device with LUKS data on it, then all that data is permanently gone (rather obvious, also see FAQ). If not, then maybe describe what happened so that it is possible for us to reconstruct it? Arno On Fri, Apr 20, 2012 at 04:58:46PM +0100, Simon Bing wrote: > I used cryptsetup to perform the following function > > cryptsetup -y --cipher aes-xts-plain --key-size 512 luksFormat /dev/sdb1 > > An error occured saying it couldnt be performed which i pretty much ignored > and just thought i won't bother. I did note that it mentioned about kernel > compatability though. The drive appears to be encrypted and wont accept > the passphrase set. This has just under 1.5 tb of information i can't > afford to loose. Do you have any solutions, i have looked online but am > absolutely stuck > > Cheers > > Si > _______________________________________________ > dm-crypt mailing list > dm-crypt@xxxxxxxx > http://www.saout.de/mailman/listinfo/dm-crypt -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@xxxxxxxxxxx GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- One of the painful things about our time is that those who feel certainty are stupid, and those with any imagination and understanding are filled with doubt and indecision. -- Bertrand Russell _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
