Solution to "sdamusthaveaGPTdisklabel" appears during RHEL6.2 Installation

After installing the RHEL6.2 operating system, the "sdamusthaveaGPTdisklabel" problem occurs after the partition, and the next step cannot be performed. Solution: 1. Select the default partition settings and perform partitioning. 2. Restart the machine and create a custom partition. For more information, see www. linuxquestions. orgquestionslin.

After installing the RHEL 6.2 operating system, the "sda must have a GPT disk label" error occurs after the partition, and the next step cannot be performed. Solution: 1. Select the default partition settings, then perform partitioning 2. Restart the machine, and then custom partitions for this method reference: http://www.linuxquestions.org/questions/lin

After installing the RHEL 6.2 operating system, the "sda must have a GPT disk label" error occurs after the partition, and the next step cannot be performed.

The solution is as follows:

1. Select the default partition settings and format the partitions.

2. Restart the machine and then customize the partition.

This method reference: http://www.linuxquestions.org/questions/linux-server-73/sda-must-have-a-gpt-disk-label-error-while-installing-rhel6-ibm-x3650-m3-server-875450/

Original article:

Just wanted to let you know that we solved the problem. I have detailed the steps below:

1 .) the need for the "GPT Disk Label" was still there but we worked around the problem by first choosing one of the default setups for RHEL6. We let the default-setup format and prepare the file- system as it pleased and I am guessing that it created a "GPT Disk Label" for our disk.

2 .) once it had created and formatted the partitions, we just canceled the setup and rebooted the server. at this stage, my guess wocould be that the RHEL6 setup did everything that was necessary to prepare the file-system -- including creating a "GPT Disk Label ".

3.) After rebooting, we simply entered setup again and choose the 'custominstallation' and created partitions according to our specifications.

4.) Hitting the next button did the trick and we got to the next stage of installation.

Thanks for everyone for helping out...