Bug 15705

Summary: Unable to re-format a previous RAID 1 disk (at least at the installer)
Product: Mageia Reporter: Alejandro Vargas <alejandro.anv>
Component: RPM PackagesAssignee: Thierry Vignaud <thierry.vignaud>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal CC: ennael1, tmb
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: drakxtools CVE:
Status comment:
Attachments: report.bug

Description Alejandro Vargas 2015-04-15 15:18:58 CEST
This days I was making tests of the installer in RAID disks. I installed mga5 in a virtual machine with 2 disks in RAID1. 

Then, I tried to install (not update) over this disks but destroying the RAID and formatting in BTRFS. 

The problem: diskdrake reports it can't format the partition. I think may be it is not stopping the RAID and not writting the changes before trying to format, because if I reboot, the previous RAID stills there.

Reproducible: 

Steps to Reproduce:
David Walser 2015-04-15 15:30:33 CEST

CC: (none) => ennael1, tmb
Assignee: bugsquad => thierry.vignaud

Comment 1 Thierry Vignaud 2015-04-15 16:29:49 CEST
What did you try? beta3 or RC?

Keywords: (none) => NEEDINFO

Comment 2 Thierry Vignaud 2015-04-15 16:30:42 CEST
Also please try again and when you see the error:
1) plug an USB key
2) go to tty2
3) run the "bug" command
4) attach to this bug report the "report.bug" file you'll found
   on this USB key
Thierry Vignaud 2015-04-15 20:00:44 CEST

Summary: Inable to re-format a previous RAID 1 disk (at least at the installer) => Unable to re-format a previous RAID 1 disk (at least at the installer)
Source RPM: drakxtools (Diskdrake) => drakxtools

Comment 3 Alejandro Vargas 2015-04-16 14:04:51 CEST
Created attachment 6293 [details]
report.bug

I'm attaching the file report.bug as requested.
Comment 4 Alejandro Vargas 2015-04-16 14:20:26 CEST
I am using the lastest version because I am booting with boot.iso and installing through network. I selected mirrors.kernel.org for instalation.
Comment 5 Thierry Vignaud 2015-04-16 14:45:56 CEST
OK, that's the (more generic) bug #15664 I've opened (though I should have maybe split it between LVM & RAID).
We should probably run mdadm --remove when stopping a RAID.

*** This bug has been marked as a duplicate of bug 15664 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE