[Bug 1939626] [NEW] Ubiquity formats Luks partition regardless of user choice and results in data loss

[jhansonxi]

Public bug reported:

Xubuntu 20.04.2
ubiquity 20.04.15.10
partman-crypto

Lost an lvm PV because of this.

Steps to reproduce:
1. Create encrypted partition with cryptsetup luksFormat
2. Check crypt partition UUID with cryptsetup luksUUID
3. Close crypt volume with cryptsetup luksClose if necessary.  Launch ubiquity installer.
…
4. no updates
5. Installation type: Something else
6. Select an existing Luks partition and change to "physical volume for encryption".
7. "Edit partition" dialog options for "Format the partition" and "Overwrite empty disk space" are unchecked.  Enter key and confirm.
8. Long pause.  Crypt volume appears on main window.
9. Check crypt partition UUID again.  It has changed due to an unrequested luksFormat.
10. Syslog shows:

xubuntu partman-crypto: WARNING: Device /dev/sda1 already contains a
'crypto_LUKS' superblock signature.

11. Repeat with the crypt volume open to block writes.  Error dialog after step #7 reports "Configuration of encrypted volumes failed" "An error occurred while configuring encrypted volumes.  The configuration has been aborted".
12. Syslog shows: 

xubuntu partman-crypto: Device /dev/sda1 is in use. Can not proceed with format operation.
xubuntu partman-crypto: WARNING: Device /dev/sda1 already contains a 'crypto_LUKS' superblock signature.

Tried ubiquity --debug but didn't find anything pertaining to the
problem in the other logs.

Not sure if the problem is with ubiquity, partman-crypto, or both.  It
needs a "cryptsetup isLuks" check somewhere along with some warnings.

Probable manifestations of the same bug:
bug 1909821
bug 1779548

Possibly related upstream bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451535
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616716

Upstream development of parman-crypto seems very slow.  Mostly just
language updates.

** Affects: ubiquity (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1939626

Title:
  Ubiquity formats Luks partition regardless of user choice and results
  in data loss

Status in ubiquity package in Ubuntu:
  New

Bug description:
  Xubuntu 20.04.2
  ubiquity 20.04.15.10
  partman-crypto

  Lost an lvm PV because of this.

  Steps to reproduce:
  1. Create encrypted partition with cryptsetup luksFormat
  2. Check crypt partition UUID with cryptsetup luksUUID
  3. Close crypt volume with cryptsetup luksClose if necessary.  Launch ubiquity installer.
  …
  4. no updates
  5. Installation type: Something else
  6. Select an existing Luks partition and change to "physical volume for encryption".
  7. "Edit partition" dialog options for "Format the partition" and "Overwrite empty disk space" are unchecked.  Enter key and confirm.
  8. Long pause.  Crypt volume appears on main window.
  9. Check crypt partition UUID again.  It has changed due to an unrequested luksFormat.
  10. Syslog shows:

  xubuntu partman-crypto: WARNING: Device /dev/sda1 already contains a
  'crypto_LUKS' superblock signature.

  11. Repeat with the crypt volume open to block writes.  Error dialog after step #7 reports "Configuration of encrypted volumes failed" "An error occurred while configuring encrypted volumes.  The configuration has been aborted".
  12. Syslog shows: 

  xubuntu partman-crypto: Device /dev/sda1 is in use. Can not proceed with format operation.
  xubuntu partman-crypto: WARNING: Device /dev/sda1 already contains a 'crypto_LUKS' superblock signature.

  Tried ubiquity --debug but didn't find anything pertaining to the
  problem in the other logs.

  Not sure if the problem is with ubiquity, partman-crypto, or both.  It
  needs a "cryptsetup isLuks" check somewhere along with some warnings.

  Probable manifestations of the same bug:
  bug 1909821
  bug 1779548

  Possibly related upstream bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451535
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616716

  Upstream development of parman-crypto seems very slow.  Mostly just
  language updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1939626/+subscriptions