Bug#662768: [cryptsetup] New cryptsetup version chokes on old LUKS header

2012-03-07 Thread Milan Broz
On 03/06/2012 12:19 PM, Milan Broz wrote: LUKS keyslot 4 is invalid. LUKS keyslot 5 is invalid. So, as expected, there was partition table signature written over LUKS header. I added some code to fix it upstream, not enabled by default.

Bug#662768: [cryptsetup] New cryptsetup version chokes on old LUKS header

2012-03-06 Thread Konrad Zimmermann
Package: cryptsetup Version: 2:1.4.1-2 Severity: normal --- Please enter the report below this line. --- I am running 3 LUKS encrypted disks in a software RAID5. After upgrading to version 2:1.4.1-2 of cryptsetup cryptsetup luksOpen /dev/sdb sdb_crypt on any of these disks failed, returning

Bug#662768: [cryptsetup] New cryptsetup version chokes on old LUKS header

2012-03-06 Thread Milan Broz
On 03/06/2012 10:38 AM, Konrad Zimmermann wrote: Package: cryptsetup Version: 2:1.4.1-2 Severity: normal --- Please enter the report below this line. --- I am running 3 LUKS encrypted disks in a software RAID5. After upgrading to version 2:1.4.1-2 of cryptsetup cryptsetup luksOpen /dev/sdb