Description of problem:
This was tested on a DELL E4310 (Laptop)
* The disk has XP installed, there is free (unpartitioned) space in
* XP uses MSDOS/MBR partition scheme :-)
I booted the laptop in UEFI mode, so F18 anaconda is running in UEFI
* When selecting the disk, anaconda detects that there is free space
and displays the dialog that 'there is plenty of space to install
But there are some consequences:
* BOTH the 'AUTOMATIC PARTITIONING' and the 'automatic partition
suggestion' (feature in manual partitioning) will not work.
They will complain (CORRECTLY) the following: "you have not created a
boot-loader stage1 target device sda6 must have one of the following
disk-label types: GPT"
Anaconda should have displayed the 'reclaim disk' dialog scenario
(which would be some form of improved 'reclaim space' dialog, which
can ALSO delete a msdos disk-label and replace it wih a gpt one)
The correct course of action -in this case- is to either:
*1 Reboot in BIOS mode and use such free space.
> anaconda should be able to ask the user to do so (in a clear way).
*2 Delete the current (MSDOS) partition table entirely and replace it with a
GPT one and then either use custom partitionig or manual.
> anaconda should be able to tell the user that the current partition
table, -while having free space- is not usable under the current
FIRMWARE. If one boots anaconda in UEFI it is assumed -correctly-
that future intended boots are going to be in UEFI) (the same would
be for bios).
> anaconda should then be able to request the user to do that manually
and in case of automatic partitioning, a special warning that the
current disk-label will be changed (which might imply a change in
used FIRMWARE on some HW).
I will not propose this as a blocker for F18, mostly because this can be
commented in 'common bugs' or similar documentation somewhere.
However, it believe that some improvement is needed for F19 cycle to be able
to cope with situations like this and be able to resolve everything from
within anaconda itself (and without any reboot, if possible).
When one boots anaconda in UEFI and the target disk (with might contain
data) is MSDOS partitioned, the provided information by anaconda
is -currently- insufficient.
There is a valid error message, but incomplete because an additional
message should inform the user to either boot in BIOS mode or wipe
the partition table (and erase all data).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install the other os xp (disk in in MBR
2. boot F18 anaconda in UEFI mode
3. anaconda will recognize the disk as 'with free space' but it will
not be able to use it.
the user cannot install
anaconda should explain the situation with more detail and (IF POSSIBLE)
do not consider the disk as 'with free space'.
anaconda-18.22-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.22-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-18.23-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.24-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.25-1.fc18 has been submitted as an update for Fedora 18.
anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18.
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.