On Sat, Jun 22, 2013 at 01:24:59PM +0800, Packets wrote: > On Tue, Jun 11, 2013 at 2:21 AM, Milan Broz <gmazyland@xxxxxxxxx> wrote: > > > To properly run locally compiled keyslot checker tool try > > > > cd ~/Downloads/cryptsetup-1.6.1/misc/keyslot_checker > > sudo LD_LIBRARY_PATH="../../lib/.libs;$LD_LIBRARY_PATH" > > ./chk_luks_keyslots /dev/sdb1 > > > > Thanks Milan. Here is the output > > nelson@kazekage:~/Downloads/cryptsetup-1.6.1/misc/keyslot_checker$ sudo > LD_LIBRARY_PATH="../../lib/.libs;$LD_LIBRARY_PATH" ./chk_luks_keyslots > /dev/sdb1 > > parameters (commandline and LUKS header): > sector size: 512 > threshold: 0.900000 > > - processing keyslot 0: start: 0x001000 end: 0x020400 > low entropy at: 0x010000 entropy: 0.593573 Definitely header damage in Key-Slot 0. To find out what the damage is, re-run with -v. > - processing keyslot 1: keyslot not in use > - processing keyslot 2: keyslot not in use > - processing keyslot 3: keyslot not in use > - processing keyslot 4: keyslot not in use > - processing keyslot 5: keyslot not in use > - processing keyslot 6: keyslot not in use > - processing keyslot 7: keyslot not in use > > >From the output above, could you tell if there the header is damage? Is > > my storage still possible to open? In any case, you need a header backup to access your data, this keyslot is permanently broken. 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 ---- There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult. --Tony Hoare _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
