| Summary: | "Erase disk" option fails to delete partitions when there's RAID/LVM | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thierry Vignaud <thierry.vignaud> |
| Component: | Installer | Assignee: | Mageia tools maintainers <mageiatools> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | alejandro.anv, marja11, pterjan |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-installer-stage2 | CVE: | |
| Status comment: | |||
| Attachments: | try harder to erase disk with RAID/LVM | ||
|
Description
Thierry Vignaud
2015-04-09 14:49:25 CEST
Thierry Vignaud
2015-04-09 14:49:35 CEST
CC:
(none) =>
pterjan Created attachment 6250 [details]
try harder to erase disk with RAID/LVM
still fails with "Remove the logical volumes first" because RemoveFromLVM()
calls lvm::vg_destroy() w/o removing the LVs first
If one manually run lvremove, one can go on.
Likewise for RAIDs, it fails to remove partitions belonging to RAID (busty) despite raid::removeDisk() having called mdadm --stop
Running mdadm --zero-superblock on each member is needed...
Running mdadm --remove on the whole array could maybe do the trick too. We should maybe display warnings asking for confirmation before killing everything though As note in bug #15705, that also happen when one manually delete a RAID. We should probably run "mdadm --remove" after "mdadm --stop". I think you should remove the raid when you remove the last disk on it...
Samuel Verschelde
2015-05-31 22:42:21 CEST
Whiteboard:
(none) =>
FOR_ERRATA
Marja Van Waes
2016-10-09 11:26:45 CEST
CC:
(none) =>
marja11
Samuel Verschelde
2016-10-18 13:11:36 CEST
Whiteboard:
FOR_ERRATA =>
(none) |