Description of problem: While upgrading from Mageia 1 to Mageia 2, Beta 2, I attempted to remove an encrypted partition but am unable to do this using the MCC (Mageia Control Center - Manage Local Disks). Version-Release number of selected component (if applicable): Mageia 2, Beta 2 How reproducible: Failure to delete using install disk (during the install process). Failure to delete partition after install (regular install using MCC). Steps to Reproduce: During the install process, you eventually get to the step asking how you want to configure your harddrive.... During a regular install, you can select MCC and then run "Local Disks, Manage disk partitions".... 1. "Please make a backup of your data first" -> select "continue" 2. With the mouse cursor, select the encrypted partition. 3. With the mouse, then choose Unmount. 4. With the mouse, then select Delete. error message is "cryptsetup failed"
Summary: Mageia 2, Beta 2, Unable to delete an encrypted partition from MCC => Mageia 2, Beta 2, Unable to delete an encrypted partition using MCC
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
@joe : Is this bug still valid for Mageia 2 or Cauldron ? Roelof
CC: (none) => r.wobben
valid mga4b2, see also https://bugs.mageia.org/show_bug.cgi?id=9731#c1 Editing an encrypted partition in LVM have never worked error free AFAIK :/
CC: (none) => friHardware: i586 => All
Workaround at (re)install time: I usually end up making a small /boot, then rest of drive one partition encrypted used for LVM, and in that everything except boot. = Higher security but also a unnesessary slowe system, if you only really need to encrypt /home or a part of /home...
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => OLD