I think this can be marked as duplicate of bug #428435. I know this bug dates back a lot more and it's not originally util-linux-ng related, but on karmic this will manifest through blkid.
However the underline cause of these bug reports is the fact that older versions of cryptsetup (<1.0.7) did not clear the partition superblock and thus left bogus signatures floating around. It was a bug with cryptsetup and that bug has now been fixed upstream and from karmic onward people should not be affected with new partitions. It's unfortunate that the bug is causing a lot of trouble to some users, I included, but let's face it; there's no way we can sanely come up with patches to vol_id or blkid which would automatically guess which signature is the right one. Therefore this is a WONTFIX for every package affected. It's true that old vol_id did claim a partition as LUKS encrypted even though there were other signatures also. This was "wrong" behaviour, but it just happened to work. I will try to create an encrypted partition with both LUKS and swap signatures under jaunty and then try to add support to my script in bug #428435 (comment 24) to remove the swap signature so that there's at least some way for people to migrate from jaunty to karmic without having to reformat their LUKS partitions. -- blkid fails to identify old LUKS partition volumes https://bugs.launchpad.net/bugs/362315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
