Created attachment 2405 [details]
Screenshot of bogus error message

Created attachment 2406 [details]
Truncated bug log at time of issue

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Pascal, it may be due to:
 error: bad dmraid (missing partition mapper/nvidia_gcdebahfp1), you may try rebooting install with option "nodmraid" at /usr/lib/libDrakX/fsedit.pm line 226.
Maybe a timing issue?

CC: (none) => thierry.vignaud

I just spotted something that may be the key. I just tried installing from the Mageia 2 final install DVD and while the device names are slightly different, the message on the screen says "missing partition mapper/pdc_gcdebahfp1", while the node on disk is actually called mapper/pdc_gcdebahf1 (note the missing "p" before the 1). So, it seems that somehow the installer is confused about what the nodes are actually supposed to be called, or the nodes are given names that are not what they are supposed to be.

What about Mageia 3 alpha 1?

I should be able to try it as soon as it's released.

Same results on Mageia 3 alpha 1. Of the two options in comment #5, I'm leaning towards the second, i.e. the nodes in /dev/mapper/ have been given the wrong names, especially since the names on a an installed Mageia 1 system include the "p" before the partition number.

Humm, Colin, Pascal, could it be that we lack some udev rules?

CC: (none) => mageia

dmraid when run from the command-line seemed to want to create names without the 'p'. It looks like adding "--partchar p" ought to fix that, but dmraid complained about that option and wouldn't run when it was used.

Anyway, I manually created the names with 'p' from the terminal and installation continued fine.

Humm, Thomas you added 24_drop_p_for_partition_conditional.patch in dmraid-1.0.0-0.rc16.8.mga2:
"fix conditional adding of 'p' if partition name"
(http://svnweb.mageia.org/packages/cauldron/dmraid/current/SOURCES/24_drop_p_for_partition_conditional.patch?view=markup)
I wonder if that could be the issue...

CC: (none) => tmb

The other issue I think about is that we don't include /etc/udev/rules.d/kpartx.rules
However thomas you made dmraid requires kpartx.
Maybe do we miss those rules

Thomas that patch doesn't exist in Fedora, only in Ubuntu and I think it's the ussye

Source RPM: drakx-installer-stage2 => dmraid

(In reply to comment #10)
> Anyway, I manually created the names with 'p' from the terminal and
> installation continued fine.

Hey Dan, can you please tell me how to change the names and continue the installation?

CC: (none) => CJ-Zelda-Link

I don't remember exactly which way I did it, but any of mknod, mv or ln -s should work. Switch to the debug terminal and fix the file names in /dev/mapper/. I believe they are available to be fixed at the last screen in the installer before it gives the error message.

Thank you very much. ln -s was a great idea. works fine.
but after the installation finished, i must use it again to install grub manually.

Maybe a missing udev rule.
Can you attach your /root/drakx/report.bug.xz?

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

Created attachment 3434 [details]
Requested report.bug.gz

Here is the requested report.bug.gz
I hope it helps.

I had the same problem on official Mageia 3 DVD (x86_64) and Nvidia NForce 790 Ultra SLI raid controller. The solution above (ln -s) works well.

After MCP55 driver installation and before activating the raid driver, I switched to the debug console via [Alt]+[F2]. A listing of /dev/mapper gave me this :
   - nvidia_iibadebh
   - nvidia_iibadebh1
   - nvidia_iibadebh2
   - nvidia_iibadebh3
   - nvidia_iibadebh5
As the raid driver asks a "p" before the partition number (I knew it with a previous failed installation), I created symbolic links like this :
   - nvidia_iibadebhp -> nvidia_iibadebh
   - nvidia_iibadebhp1 -> nvidia_iibadebh1
   - nvidia_iibadebhp2 -> nvidia_iibadebh2
   - nvidia_iibadebhp3 -> nvidia_iibadebh3
   - nvidia_iibadebhp5 -> nvidia_iibadebh5

With this modification, the activation of the raid driver works well: it finds all the partitions.

CC: (none) => emmanuel.dieul

Dear,

I make à fresh install, I have a same problem with asus A7N8X-sli.

Stéphane.

CC: (none) => megastorage

I confirm too with symbolic links that work and I can continu the installation.

But failed at the mkinitrd...

Stéphane.

I had a problem with the initrd as well. I don't recall exactly what I did to fix it, but I think it was as simple as rebooting after the initial installation, then manually generating it.

After reboot, grub start, start the system.

The system stop on: 
dracut Warning: Could not boot
dracut Warning: "/dev/mapper/sil_******PX"does not exit.

in /dev/mapper/ I have : sil_******X without "P".

I don't know how to solve it.

Changing version to cauldron since we can't fix installer for released versions (that's what alphas and betas are for)

Version: 3 => Cauldron

Same problem with mag4_a3

Stéphane.

Dear,


I testing today, it's solve for me.

With my configuration with dmraid.

No error from the installation.

I send from cauldron.

Thanks.

Stephane.

Fixed by dmraid-1.0.0-0.rc16.15.mga4
Closing

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