Setup RHEL7 using GPT instead of Fdisk

Latest response

So I deployed our first RHEL7.3 VM in our development environment from an ISO. And while I created a /boot/efi directory because I prefer to build with GPT vs Fdisk, it still created all of the partitions as Fdisk.

I consulted Red Hat's documentation on RHEL7 installation:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-disk-partitioning-setup-x86.html

I guess I'm not understanding where I went wrong with this.

thanks

Responses

I think this is the relevant section from the documentation

BIOS systems, and UEFI systems in BIOS compatibility mode
    If the disk is already formatted, the partitioning scheme is retained.
    If the disk is not formatted, or the user erased all partitions from the disk, Anaconda will use:

        MBR if the disk has less than 232 sectors. Most commonly, disks sectors are 512 bytes in size, in which case this would be equivalent to 2 TiB.
        GPT if the disk has 232 sectors or more. 

And then this note:

Note
Append the inst.gpt option to the boot command line to override the default behavior and use GPT on a disk of less than 232 sectors in size. Note that you cannot manually override Anaconda to use MBR on a disk which is 232 sectors in size or larger. 

Is the UEFI configuration running in BIOS compatability mode? This may be taking you down a different (unexpected) path.
What size are the disks? as this will determine behaviour.
If the disks are are smaller than the limit (2TiB), did you provide inst.gpt to the command line of the installer?

-edit- clarification of UEFI in BIOS mode.

I'm not sure where to append inst.gpt? Upon the first reboot of the brand new VM? I used the GUI to perform the install.

Size of the disks are small and only two disks total which average about 125 GB in size as we are testing an application with Mongdb on the backend.

Ok, so if I'm understanding correctly, when say booting from the ISO, you would have to press "E" key and pass the inst.gpt parameter on the line for the kernel, which I believe is linux16, correct?

Correct.

If that resolves your issue, I would assume your UEFI system is in BIOS compatability mode which is leading to the (unexpected) behaviour you are seeing.

Ah...the smoking gun was that I forgot to select UEFI vs BIOS via Vcenter (right click on VM > settings > Options Tab > Firmware Radio Buttons for EFI).

Ok, so I know what to expect if this comes up next time.

thanks

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.