Comment 13 for bug 1462632

Bingo! I tried zeroing out the first 64 sectors of the existing (ext4) partition before running the installer so it wouldn't recognize it, and it reports the partition as unrecognized. Changing its type to crypto still does not change the contents of the disk, and if I quit the installer and restore the first 64k, it works fine. HOWEVER, if I start with an existing crypto install, the installer also reports that it does not recognize the partition type ( possibly a separate bug ) and now if I change its type to crypto, it indeed does immediately commit the the changes to disk, destroying the previous luks container.