[pkg-cryptsetup-devel] Bug#585934: [udev] UUID discrepancy between cryptsetup luksUUID and udevadm info
Guy Heatley
guy at member.fsf.org
Wed Jun 16 11:25:26 UTC 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 16/06/2010 12:19, Milan Broz wrote:
> On 06/16/2010 12:57 PM, Guy Heatley wrote:
>> On 16/06/2010 11:39, Milan Broz wrote:
>> I'm not sure this is true - this device had not been opened by
>> cryptsetup at this point: There was no entry in /dev/mapper , it was not
>> an active Luks device.
>
> If that device was LUKS formatted long ago, maybe you are seeing the old bug,
> when some sectors were not properly wiped and there are both signatures of ext3 and LUKS
> on the device.
>
> You can easily fix that, simply run luksHeaderBackup and luksHeaderRestore
> with cryptsetup 1.1.x (this will wipe that problematic area).
>
> If it is problem, please try
> crypsetup luksHeaderBackup --header-backup-file <file> <device>
> crypsetup luksHeaderRestore --header-backup-file <file> <device>
>
> Milan
Yes - its is possible this partition was made with a long-gone version
of cryptseup.
I will try your suggestion! Thanks!
- --
Guy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkwYtKIACgkQtVeealbDyDUTOwCeKdrqC+6lfnz0ANVBEu30DOvO
HIMAnjq/jfHKMc947B3flVKwSjABMLDv
=tARG
-----END PGP SIGNATURE-----
More information about the pkg-cryptsetup-devel
mailing list