Issue occurs every time I try to install

Tried installing on an IDE 120gb HDD whith a 90gb primary NTFS partition and the remaining space formated to ext4.

Thanks for the bug report.
Could you provide the file /root/drakx/report.bug.gz as an attachment ?
If you don't have the file, you can switch to console 2 (by pressing 'Ctrl-Alt-F2') during installation, put a floppy in floppy drive or plug a USB key/stick and type: 'bug' then press Enter. It will put report.bug on the floppy/key.

you can also what happen on the installer with ps or pstree in the same console (if there is a process that take to much time

Keywords: (none) => NEEDINFO
Source RPM: (none) => drakx-installer-stage2

I tried installing again Mageia 2 alpha 3 and I got the message: "I cannot find any room for installing"

I could not copy report.bug.gz on the flash drive, but this is what I see on the consoles:


https://lh5.googleusercontent.com/-nm0uJ-rodHM/T06LsKZ68tI/AAAAAAAAHWs/iD_RBh5ZVR4/s720/20120229_223301.jpg

https://lh6.googleusercontent.com/-LFpfT0HoikA/T06LmxrAEJI/AAAAAAAAHWk/yl4cNCeCJKA/s720/20120229_223252.jpg

https://lh4.googleusercontent.com/-2HeJGO3li8E/T06LhMGNLlI/AAAAAAAAHWc/r0f_FmIX7F8/s720/20120229_223239.jpg

Ok seems you have a floppy drive, right ?

if yes it's a duplicate of bug 4696

(In reply to comment #4)
> https://lh6.googleusercontent.com/-LFpfT0HoikA/T06LmxrAEJI/AAAAAAAAHWk/yl4cNCeCJKA/s720/20120229_223252.jpg

How did you partition the drives?  The above shows it found
a gpt signature, but couldn't find the fake msdos partition
that should exist on a gpt partitioned drive.

CC: (none) => davidwhodgins

(In reply to comment #5)
> Ok seems you have a floppy drive, right ?
> 
> if yes it's a duplicate of bug 4696

I do not have a floppy drive installed..

(In reply to comment #6)
> (In reply to comment #4)
> > https://lh6.googleusercontent.com/-LFpfT0HoikA/T06LmxrAEJI/AAAAAAAAHWk/yl4cNCeCJKA/s720/20120229_223252.jpg
> 
> How did you partition the drives?  The above shows it found
> a gpt signature, but couldn't find the fake msdos partition
> that should exist on a gpt partitioned drive.

Thank you for all your interest and help :)

sda - 120gb IDE hdd with a 95gb nfts partition for data storage and the rest as unallocated space in order to install mageia2

sdb - a 250gb IDE hdd with a single ntfs partition for data storage

sdc - 60gb SATA2 ssd with two ntfs partitions for windows 7 (and now 8) plus "maybe" a boot partition created by windows setup (I am not sure it's there, I have not checked).

I have messed about with OSX in the past but I thought I had cleaned all by drives from any osx related partitions. Windows has no problem with the drives, and from recent experience, neither does Mint 12.

Generally I use GParted from Ubuntu livecd to partition the drives or Acronis from a Falcon bootcd.

How can I remove traces of gpt stuff ?

As Manuel noted in comment 5, the last line in the log is
the running of blkid on /dev/fd0.

As there is no floppy installed, the bios setup should be
used to disable the floppy controller.  This has cleared
up a similar freeze in bug 4696.

That may be enough so that you can then install Mageia.

If not, you'll need to erase the gpt partition table header,
which is in sector 1, the first sector after the mbr.

Using a live cd, as root, run the following commands ...
dd if=/dev/sda of=mbr.bin bs=512 count=1
dd if=/dev/zero of=zero.bin bs=512 count=1
cat mbr.bin zero.bin > mbrzero.bin
dd if=mbrzero.bin of=/dev/sda bs=1024 count=1

I've never used a gpt partitioned disk.  The above is
based on my understanding from reading
http://en.wikipedia.org/wiki/GUID_Partition_Table

As always, when dealing with partitioning, make sure
all important data has accessible backup.

You were right about the floppy controller - I had disabled it in the past, but at some time my bios reset to defaults and I forgot to re-disable it... duh!

I will try again and let you know

Hurray!! I am running Mageia 2 beta 1 !!!

THANK YOU for all your advice and help, I would have given up without it!
I was able to install with no problems after the mageia2 isntaller promted me to clean my sda drive of all the gpt stuff: http://goo.gl/AjuQd

Installing took a while (maybe 30-45min) but now all is well :)
I have to install my nvidia 520 drivers and setup my audigy 2ZS and I am good to go.



BTW, when I try to update I get the message: "udisks-deamon is not running". How do I bring it up?

yep sorry for comment 7 I have misunderstand too fast.

>BTW, when I try to update I get the message: "udisks-deamon is not running".
>How do I bring it up?

you can remove the cdrom media or install udisks, see bug 4645

Seems no, but do we have a new bug in this report ?

(there are some open against gpt https://bugs.mageia.org/buglist.cgi?quicksearch=gpt)

(In reply to comment #11)
> Hurray!! I am running Mageia 2 beta 1 !!!
> 
> THANK YOU for all your advice and help, I would have given up without it!
> I was able to install with no problems after the mageia2 isntaller promted me
> to clean my sda drive of all the gpt stuff: http://goo.gl/AjuQd

Glad it worked.  I'm curious though, did the installer provide a method
for cleaning the gpt partition table header, or did you use the dd
commands to erase it?

(In reply to comment #13)
> Glad it worked.  I'm curious though, did the installer provide a method
> for cleaning the gpt partition table header, or did you use the dd
> commands to erase it?

In this prompt http://goo.gl/AjuQd I just selected "Yes" than "Next" and it did its magic.. I thought I;d first try this and if it dindn't then try your dd commands

(In reply to comment #14)
> In this prompt http://goo.gl/AjuQd I just selected "Yes" than "Next" and it did
> its magic.. I thought I;d first try this and if it dindn't then try your dd
> commands

Thanks for the reply.  As nothing needs to be changed to handle
erasing the gpt partition header, the only real problem here
was having the floppy controller enabled, without having a
floppy drive installed.

I'll close this bug report as a duplicate of bug 4696.

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

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