Bug 15774

Summary:	Installation fails: internal error:unknown device md0
Product:	Mageia	Reporter:	Graeme Gemmill <grimble00060>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	critical
Priority:	Normal	CC:	thierry.vignaud
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Graeme Gemmill 2015-04-26 15:01:14 CEST

Installing Mageia 5 beta 3.
After accepting licence conditions, the following error panel is displayed:
INTERNAL ERROR: unknown device md0
MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/devices.pm:130
devices::entry()called from /usr/lib/libDrakX/devices.pm:145
devices::make() called from usr/lib/libDrakX/raid.pm:283
[13 more lines]
Pressing OK button returns to "Configuring IDE" screen, immediately followed by the same error

I don't want to install Mageia on the raid array - I have a separate disk with Mageia 4 installed on which I want to install the Beta to dual boot.


Happens every time I try to install Mageia 5 Beta 3


I've classified it as critical because I can't get passed this block


Reproducible: 

Steps to Reproduce:

Comment 1 Rémi Verschelde 2015-04-26 15:14:50 CEST

This is most likely a duplicate of bug 15400 which was fixed in Mageia 5 RC.
The RC got released yesterday (no blog announcement yet, but the website is already updated: http://www.mageia.org/5 ).

Could you try the RC to confirm that the issue is fixed?

Samuel Verschelde 2015-04-26 22:50:38 CEST

Keywords: (none) => NEEDINFO

Comment 2 Thierry Vignaud 2015-04-27 11:57:19 CEST

A dup indeed

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

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => DUPLICATE

Comment 3 Graeme Gemmill 2015-04-28 11:07:53 CEST

Happy to report that RC installed faultlessly and is now happily downloading the first set of updates.
Congratulations to the delivery team

Resolution: DUPLICATE => FIXED

Comment 4 Thierry Vignaud 2015-04-28 12:25:31 CEST

Please keep it as a duplicate

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

Resolution: FIXED => DUPLICATE