So I'm building out a new RHEL6 servers with UEFI so I can take advantage of gdisk.

For some reason one of the servers didn't have gdisk installed on it, so because of a time crunch I had to use fdisk to build out a partition for a rsyslog server.

I later went back and installed gdisk incase I need to create more partitions, as I like working with that more. However I'm not sure if this will cause a conflict in the future if I want to add more partitions with gdisk and started the process with fdisk.


Has anyone run into this before or is this a non-issue?

gdisk manages only GPT partition tables, while fdisk manages only classic MBR partition tables. As fdisk would have made a MBR partition table, gdisk will load but prompt you to convert to GPT.

The main difference between fdisk and gdisk is the former works with MBR, while the later works with GPT - the main choice is do you want to convert to and use GPT on that machine (to use gdisk), or stick with the classic MGR partition table (keep using fdisk). That could be a potentially destructive operation and creating booting hassles - I would just recommend using fdisk unless there's something you really need from GPT.

2 members found this post helpful.

If I'm building a server with UEFI, I want to use gdisk, as I can create 128 partitions and I'm not limited like I am with fdisk.

Its odd that gdisk didn't get installed with default RHEL6 system built on UEFI.

Then, if it is possible for you, try to start over and partition that drive with gdisk so that you have a GPT there. Because, as it is right now, it is MBR and it might limit you in the future.

1 members found this post helpful.

I really hate myself for saying it, but more haste less speed.

A conversion is likely possible: https://zindilis.com/docs/centos-6-c...br-to-gpt.html

Just finish with w after firing up gdisk

Since I'm using LVM as well, I believe that I can use pvmove and vgreduce to move data off of the LVM, delete the partition with fdisk and then re-create it with parted.

Correct?

You can wipe the disk & start again, a bit more slowly.