Steve: I must be missing something here.. how do we know which UUIDs is the correct one? Especially with removable media?
And yes, you could use the uuid parameter from root boot option and patch blkid to force read the uuid's from every type of signature it founds and then guess the right type by matching the uuid's and... Blkid is doing the right thing. It clearly indicates that there are multiple signatures and refuses to do any guess work. The fact that we are in this situation because of buggy cryptosetup is unfortunate (same will happen with any mkfs which does not clear the superblock). Now we just have to deal with the defected superblocks out there and in my opinion patching and changing working software that's doing what it suppose to do just to deal with buggy legacy is not the way to go. There are situations where that most probably goes wrong as we guess wrong and trash users data (how about activating a "new" swap partition which in fact is encrypted luks partition). We can clearly detect the situation and we can inform the users about it and we can help them fix it for good. Users know which signature is the correct one. Let's leave the decision to the user, but give all the information and help we can to make it a correct one. -- luks encrypted partition not detected or mounted automatically https://bugs.launchpad.net/bugs/428435 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
