Bug 962104 - anaconda 'gpt' boot parameter not working, partitioned disk are always formatted to MBR partition scheme (workaround=create gpt partitions before launching anaconda)
Summary: anaconda 'gpt' boot parameter not working, partitioned disk are always format...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-blivet
Version: 19
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-11 20:33 UTC by Reartes Guillermo
Modified: 2013-06-13 06:40 UTC (History)
11 users (show)

Fixed In Version: python-blivet-0.15-1.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-13 06:40:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
F19b TC4 (79.36 KB, image/png)
2013-05-11 20:33 UTC, Reartes Guillermo
no flags Details
F18 Release (70.10 KB, image/png)
2013-05-11 20:34 UTC, Reartes Guillermo
no flags Details

Description Reartes Guillermo 2013-05-11 20:33:50 UTC
Created attachment 746648 [details]
F19b TC4

Description of the problem:

On an new disk (unpartitioned) i could not make F19b TC4 to create a gpt partitioned disk. While the disk is small (less than 2tb) i should be able to manually create a gpt partitioned disk with anaconda in some way. (a boot parameter, an explicit option, etc). 

Anaconda has the 'biosboot' type mount point, but it does not always work as one might think:

#1, The 'biosboot' mount point is usable on MBR partitioned disks (Bug 887560) and does not produce a 'biosboot' partition, since there is not such a thing in the MBR Partition Scheme, it produces just another partition that will sit unused wasting space and a partition entry.

#2, for small disks (less than 2tb, i cannot test bigger disk sizes due to lack of hw), it is currently not possible to force anaconda to generate a gpt partitioned disks from unpartitioned disks.

From: https://fedoraproject.org/wiki/Anaconda_Boot_Options?rd=Anaconda/Options

'nogpt' ->  Do not create GPT disklabels. 

There is no 'gpt' boot parameter listed there.
I tried with 'gpt' anyway and the result is an MBR Partitioned disk with Bug 887560 too.
F18 Release ...

From: http://wwoods.fedorapeople.org/doc/boot-options.html
There is also no 'gpt' boot parameter listed there.

I id a '# git://git.fedorahosted.org/git/anaconda.git'
Found 'anaconda_optparse.py' which poined me to 'flags.py' in which i see:

self.gpt = False

An later this one:

if "gpt" in self.cmdline:
            self.gpt = True

So it there seems to be a 'gpt' parameter for anaconda after all.


Steps to Reproduce:

1. Have a blank unpartitioned disk. (use gdisk x/z to zap/destroy all partition tables). Make sure there
are no gpt or mbr partition tables on the disk.

2. Launch anaconda with the 'gpt' boot parameter and check /proc/cmdline to make sure it is there.

3. Enter Storage: Installation Destination, select the prepared disk, do 'custom partitioning' with partition scheme set to 'standard partition'
4. Create partitions as shown it the screenshot. (biosboot 1mb, /boot 512mb, swap 768mb, / the rest.
5. Perform the installation.
6. The result is a MBR Partitioned disk (This bug-report) with a type 83 partition. (Bug 887560)

Actual

Expected results:
F18 Release does work as expected.
It creates a gpt partioned disk with a biosboot partition when the anaconda boot parameter 'gpt' is used.

Additional info:
2 Screenshots, one for F19b TC4 and the other for F18 Release.

Comment 1 Reartes Guillermo 2013-05-11 20:34:14 UTC
Created attachment 746649 [details]
F18 Release

Comment 2 Reartes Guillermo 2013-05-29 01:57:24 UTC
I tried again with F19b RC4 and the 'gpt' bootparameter is still broken.

Booting with 'gpt' bootparameter and doing custom partitioning, the summary of changes already reveals that it will use a msdos disklabel.

Comment 3 Fedora Update System 2013-06-03 23:55:14 UTC
python-blivet-0.15-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/python-blivet-0.15-1.fc19

Comment 4 Fedora Update System 2013-06-05 02:27:38 UTC
Package python-blivet-0.15-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-blivet-0.15-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9977/python-blivet-0.15-1.fc19
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-06-13 06:40:39 UTC
python-blivet-0.15-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.