Created attachment 400623 [details] syslog, dmesg, anaconda.log and a few more details Description of problem: When booting F13-Alpha netinst (Jigdo[0], March 08, verified cdrom) on a MacBook Pro, I answer "create custom layout" in the GUI installer. I choose an existing sda4 as root filesystem (to be formatted as ext4), sda3 as swap - but when clicking on "Next", I get: sda must have a msdos disk label [0] http://mirrors.kernel.org/fedora/releases/test/13-Alpha/Fedora/x86_64/jigdo Version-Release number of selected component (if applicable): Fedora 13 Alpha How reproducible: Steps to Reproduce: 1. Boot netinst into GUI installer on MacBook Pro, with already partitioned disk 2. Choose "create custom layout" when partitioning disk, select partitions on sda (only disk in this laptop) 3. Installer says "sda must have a msdos disk label" Actual results: sda must have a msdos disk label Expected results: "Your disk has a GPT disk label, that's OK for 2010, we can boot here" :-) Additional info: $ parted -l Model: ATA TOSHIBA MK2555GS (scsi) Disk /dev/sda: 250GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 20.5kB 210MB 210MB fat32 EFI System Partition boot 2 210MB 50.2GB 50.0GB hfsx osx 3 50.3GB 54.4GB 4099MB swap 4 54.4GB 84.4GB 30.0GB ext4 linux boot 5 84.4GB 250GB 166GB data
To be more clear on the disk layout here: - there's MacOS installed on sda2, ready & usable - there's currently an Ubuntu installed on sda4, using sda3 as swapdisk, also ready & usable (also bootable, via refit.sf.net->Grub). - I want to install F13 on sda4, using sda3 as swapdisk (wiping out ubuntu, har har) - I don't want sda1,sda2,sda5 to be touched, so I can't just switch to an msdos disklabel (or can I? With MacOS X still booting?)
I'm able to reproduce this in a virtualbox VM: 1) start Fedora-13-Alpha-x86_64-netinst.iso in a new VirtualBox VM, one 4GB disk, 1GB RAM 1a) X11 fails to start in VirtualBox, so Anaconda falls back to textmode. We won't be able to create a "custom layout", apparently. 2) switch to another textconsole and do the following to the pristine disk: $ parted /dev/sda $ mklabel gpt $ q 3) switch back to the textmode installer, choose "entire drive" and "sda" and it will say, again: sda must have a msdos disk label I switched back to the other console, deleted the label and put a "msdos" disklabel on the disk (notice, that there are still NO partitions on the disk), switched back to the installer -> same error messages. However, when I repeat the process a few times, *sometimes* it'd let me "write changes to disk". But only when either "no" or an "msdos" disklabel was on the disk. But as the textmode installer won't let me create a custom layout (I don't want to use the entire disk nor do I want it to create those LVM devices - it's a Laptop!), I hope that somebody will have another look at the installer routines... Thanks.
Created attachment 400666 [details] sda must have a msdos disk label
This is similar to the discussion going on over in bug 572488, so I'm going to dup this bug to that one. *** This bug has been marked as a duplicate of bug 572488 ***