That's an annoying bug, unfortunately (or fortunately), it seems there was no other report of such a problem.

Do you still have the /root/drakx/report.bug.gz file ? Maybe it contains useful information. If yes, please attach it to this bug report.

Keywords: (none) => NEEDINFO
CC: (none) => stormi

sorry i don't have anymore this file ...
due to so many missing rpm package in mageia  i went back to mandriva.

i will probably have some time to spent in the next few weeks, if i could i will do a test with virtual machine to reproduce the trouble and then will give back news to this ticket.

Reporter, could you please reply to comment 1, to avoid this bug being closed as old?

CC: (none) => marja11, thierry.vignaud

as already answered i don't have this log file anymore.

i have done a very quit test with LVM over linux software Raid 1 and the utility is definitely unusable on this king of configuration there are stack overflow and i can't do nothing ...

the utility seem to be unable to read raid 1 partition under version 1.2
[root@XXX ~]# mdadm --detail /dev/md1
/dev/md1:
        Version : 1.2
  Creation Time : Sat Jun 25 17:57:02 2011
     Raid Level : raid1
     Array Size : 243890456 (232.59 GiB 249.74 GB)
  Used Dev Size : 243890456 (232.59 GiB 249.74 GB)
     [...]

i can't reproduce exactly the same behaviour as describe in the 1rst description because when i try to install mageia on LVM under raid1 partition the utility drakx-installer-stage2 bugs and you must reboot the PC !!

if i found a little time in the next few weeks i will try the same manipulation with raid software version .90 maybe it is the nemesis of this utility ?
have you done some tests yourself on this trouble ?

(In reply to comment #4)

Thanks for your fast reply and thanks for your willingness to help :)

> as already answered i don't have this log file anymore.
> 

Sorry, I should have asked: if you can, please help us to get the /root/drakx/report.bug.gz file of when it went wrong.

> 
> i can't reproduce exactly the same behaviour as describe in the 1rst
> description because when i try to install mageia on LVM under raid1 partition
> the utility drakx-installer-stage2 bugs and you must reboot the PC !!
> 
Please switch to console 2 (by pressing "Ctrl-Alt-F2") during installation, plug in a USB key/stick and type 

bug

then press Enter. It will put report.bug on the USB stick. report.bug contains the same information as the /root/drakx/report.bug.gz file

You can return to the normal install screen by pressing "Ctrl-Alt-F7"

Please attach report.bug to this bug report, if anything goes wrong again and please tell us what went wrong (the same as in the description of this bug or as in comment 4)

> if i found a little time in the next few weeks i will try the same manipulation

Thanks a lot!

> with raid software version .90 maybe it is the nemesis of this utility ?
> have you done some tests yourself on this trouble ?

So far, I haven't heard of anyone with the same trouble. Our maintainer really needs the information from report.bug to find out what goes wrong.

(In reply to comment #4)
> i will try the same manipulation
> with raid software version .90 maybe it is the nemesis of this utility ?
> have you done some tests yourself on this trouble ?

which raid software are you talking about, exactly? 
TBH, I don't have a RAID, and the only software I know about is dmraid, but that has been on version 1.0.0-0.rcxx very long

am talking about dm raid, but when you create a raid aggregate you can create it with 2 versions of meta data

ex

mdadm --detail /dev/md1
/dev/md1:
        Version : 1.2
  Creation Time : Sat Jun 25 17:57:02 2011
     Raid Level : raid1

mdadm --detail /dev/md0
/dev/md0:
        Version : 0.90
  Creation Time : Tue Jul 19 19:54:20 2011
     Raid Level : raid1

my remark is about this version of raid meta data.

Created attachment 1172 [details]
trouble creating RAID1 and VG

this bug repport have been generate with a manipulation like this :
- erase all partition on sda & sdb
- create 2 raid partitions 
- create VG on the 2nd raid aggregate

those manipulations are not the initiale one, but this simple usage bug in loop the drakx interface and the installation can't be done.

will try other scenario as soon as i have time.

@ mnaud mnaud: thx :)

@ Thierry
@ Thomas

Can one of you, from the available information ( https://bugs.mageia.org/attachment.cgi?id=1172 ), already tell which package is to blame?

CC: (none) => tmb
Source RPM: drakx-installer-stage2 => drakx-installer-stage2, dmraid

Is the raid1 setups configured through raid bios, or during install ?

This seems to be the installer not knowing how to handle dmraid/mdadm/lvm2 combo setup correctly...

As for the metadata version 0.9 vs 1.2 our mdadm has no problem handling them.


I'll try to reproduce here but it can take a week or so as my current TODO is _way_ too long.

Source RPM: drakx-installer-stage2, dmraid => drakx-installer-stage2

in all my usage raid is linux soft raid 1 (no specific hardware, only two sata HDD)

regarding the scenario 2 cases will appear:

- the raid is configured during mageia installation (this case generate bug.report attached 2011-12-03 22:11 CET ) 

- raid 1 partition with LVM already exist with data and we try to install mageia creating another raid 1 with LVM for installation (mean / /usr swap , ...)
this second way of use was the original cause of the problem and why i had opened this case.

@ Thierry

I'm waiting for tmb to reproduce this bug before assigning to you, but if you think that isn't needed: feel free to assign to yourself ;)

(In reply to comment #10)
> Is the raid1 setups configured through raid bios, or during install ?
> 
> This seems to be the installer not knowing how to handle dmraid/mdadm/lvm2
> combo setup correctly...
> 
> As for the metadata version 0.9 vs 1.2 our mdadm has no problem handling them.
> 
> 
> I'll try to reproduce here but it can take a week or so as my current TODO is
> _way_ too long.

@ Thomas

Did you find time to try this?

Keywords: NEEDINFO => (none)

setting version to cauldron, because it is an installer bug (and it was reproduced in a Mga2a3 bug that I'll close as a duplicate of this one)

attachment 1389 [details] of that bug will be of interest, and https://bugs.mageia.org/show_bug.cgi?id=4193#c0 :
> Whilst attempting to upgrade an MGA2alpha2 install to alpha3 (using
> Mageia-2-alpha3-i586-DVD), the installer failed to recognize the partition
> table of the dmraid RAID1 array then helpfully volunteers to erase the disk
> completely by repartitioning. The attached log shows the steps leading to the
> failure. Switching to the shell shows that /proc/partitions does, indeed,
> contain all the RAID partitions, and the complaint in the log (missing
> partition mapper/pdc_gchidfedap1) is bogus--device /dev/mapper/pdc_gchidfeda1
> does actually exist.

*** Bug 4193 has been marked as a duplicate of this bug. ***

CC: (none) => dan

Please try a network install with latest boot.iso.
I've fixed somes issues regarding reading back RAID arrays.

Keywords: (none) => NEEDINFO

that's looks better,
all my raid system and lvm are correctly seen and i can access them using the new button "read it".

but i have a trouble reboot the machine after the initial installation
due to error in inirtrd file used to boot the system.

i don't know where to report this behavior so i have "cross post" in bug id 5044
(cf https://bugs.mageia.org/show_bug.cgi?id=5044).

i attach the screenshot in this bug also.

Created attachment 2082 [details]
pb_reboot.jpeg / pb on reboot after fresh install using latest netboot.iso 2_b3

Please open a new bug for that issue

CC: (none) => mageia

(In reply to comment #17)
> that's looks better,
> all my raid system and lvm are correctly seen and i can access them using the
> new button "read it".
> 

I understand this bug has been fixed, so closing.

PLease reopen if I misunderstood

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