[Lucid] LVM Auto partitioning fails if LVM metadata exists on disks where partitions get created.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| partman-auto-lvm (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: partman-auto-lvm
I see references to this problem in other bugs, but it appears to be believed to be fixed. Perhaps this is a regression. To reproduce:
1. Begin a lucid install with LVM auto partitioning. Let the partitioning step finish.
2. Delete the partition table
3. Start another lucid install and select LVM auto partitioning.
You get an error that the volume group name is already in use. If you continue and try again, then it works. My understanding is that even if you preseed every option available to remove existing LVM data, if LVM data suddenly appears when the disk gets partitioned, partman is incapable of removing it. If you select continue, it restarts the partitioning step and allow the removal of the existing data since the partitions now exist.
We need a way to preseed something that says "no really, erase the disk."
I will test if this is a problem in older releases or if it is new in Lucid.
| tags: | added: glucid |
| Joel Ebel (jbebel) wrote | #1 |
Well, after testing, it looks like this same behavior has existed since at least hardy. In that case its probably just a duplicate of bug 154086. Feel free to mark it as such.