I had a very similar experience this morning when attempting to install a USB stick based on xubuntu-16.04.1-desktop-amd64.iso :
I added /dev/sdb1 for /boot
I added /dev/sdb2 and asked it to become the base of an encrypted volume.
My intention was to use /dev/mapper/sda2_crypt as a physical volume for LVM, and later split that up into root, swap, and a bit of free space for snapshots (which I tend to use for backup).
In my case, the /dev/mapper/sda2_crypt was created, and it was pre-configured as a file system. I had never said anything about wanting a file system on top of that, so that's already a bug.
Worse: When using the UI to change that to "basis for LVM", while several different file system types are offered, "physical volume for LVM" isn't.
So I cannot proceed with my installation as planned.
FWIW: I did run "check" on the USB stick, it found no problems.
I had a very similar experience this morning when attempting to install a USB stick based on xubuntu- 16.04.1- desktop- amd64.iso :
I added /dev/sdb1 for /boot
I added /dev/sdb2 and asked it to become the base of an encrypted volume.
My intention was to use /dev/mapper/ sda2_crypt as a physical volume for LVM, and later split that up into root, swap, and a bit of free space for snapshots (which I tend to use for backup).
In my case, the /dev/mapper/ sda2_crypt was created, and it was pre-configured as a file system. I had never said anything about wanting a file system on top of that, so that's already a bug.
Worse: When using the UI to change that to "basis for LVM", while several different file system types are offered, "physical volume for LVM" isn't.
So I cannot proceed with my installation as planned.
FWIW: I did run "check" on the USB stick, it found no problems.