LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   "SDA must have a GPT disk label" error while installing RHEL6 - "IBM x3650 M3" Server (https://www.linuxquestions.org/questions/linux-server-73/sda-must-have-a-gpt-disk-label-error-while-installing-rhel6-ibm-x3650-m3-server-875450/)

garbagegigo@gmail.com 04-17-2011 08:56 AM

"SDA must have a GPT disk label" error while installing RHEL6 - "IBM x3650 M3" Server
 
Hi everyone,

I work at a corporation where we have to install RHEL6 on an "IBM System x3650 M3" server. We have configured RAID-5 on a 5 disk array (each disk is 300 Gb) using the "MegaRaid Config Utility" that comes packaged with the IBM server.

We created a few partitions as per our requirments and put the file-system on these partitions as "ext4". But when we press the next button, the following problems come up:

1.) First it says that /boot/efi partition isn't created.
---- I simply created /boot/efi partition with a file-system type of "EFI System Partition"

2.) After performing the above step and trying to go forward using the next button, it shows an error saying "sda must have a GPT disk label".

Now we are stumped at this point. I tried searching Google, tried reading tutorials for installing RHEL6 but to no avail.

I saw in many places, they use gpart to create a GPT disk label, but in our case, we can't even boot Linux so how can we use gpart? I also checked if there was a text mode for the installer, but the installation CD automatically goes into GUI based mode and doesn't prompt for it or anything.

If anybody knows the answer, please help me.

Thanks in advance.

brian-va 04-17-2011 06:00 PM

you can use the gparted live cd

garbagegigo@gmail.com 04-17-2011 07:53 PM

Hi brian,

thanks for the answer. But could you please explain what is happening to me??

thanks

brian-va 04-17-2011 08:44 PM

Not too sure as I don't use RHEL. The gparted live cd will allow you to boot into a live environment and create the required GPT partitions, then you can try installing again.

garbagegigo@gmail.com 04-18-2011 02:11 AM

Hi everyone,

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 would 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 'custom installation' 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...

neonate 04-18-2011 07:49 AM

Ok thanks buddy for ur good post.
I also had done the same thing the very before, yup it sort-out the problem for instant however i would like to know the
stable and the reliable solution for future.

if u do have any other solution i would like know it.

thanks for your co-operation

erez.rsd 12-14-2012 04:09 PM

Have the same issue
 
I'll go ahead and try your workaround which looks promising and get back to let you know who it went.
Thanks

benjulios 03-31-2013 08:33 AM

A simpler way ?
 
First of all thank you for your thread ! I had the same pb with RHEL6.3 + IBM HS23 blades
To put the GPT label i followed the follwoing procedure ( my disk was /dev/sda ) :

inject "CTRL+ALT+F2" during your installation process to go on command line with 'parted' utility.
Code:

# parted 
parted > # print /dev/sda          => check partition type here , it should be set as something different from 'gpt'       
parted > # mklabel gpt /dev/sda    => modify the label
parted > # print /dev/sda          => Check that label has been taken into account
parted > # quit

then return to installation process with CTRL+ALT+F1

Everything should now be fine with your custom partitionning . Don't forget to create a /boot/efi by selecting it in the dropdown menu . DO NOT TRY to type it yourself as partition type will not be the good one ( EXT4 instead of EFS File system )

I hope this help!

piyush.sh143 09-06-2013 05:03 AM

hello buddy
i have dual boot system and your above solution is change hard disk label to gpt and it will distory my windows also. so give me a solution by which i can solve gpt label problem with out harming my windows version

TB0ne 09-06-2013 08:38 AM

Quote:

Originally Posted by piyush.sh143 (Post 5022937)
hello buddy
i have dual boot system and your above solution is change hard disk label to gpt and it will distory my windows also. so give me a solution by which i can solve gpt label problem with out harming my windows version

This original thread is two years old now, and doesn't involve keeping data on the disk. You need to open your own thread for your own question. Also, you need to provide actual details...things like version/distro of Linux, your system setup, your goals, etc.

narendra42074 11-05-2013 02:44 AM

GPT Disk error in duel boot
 
Hi everyone,

When i installing rhel for duel booting the problem is with GPT disk label error when i click on INSTALL IN FREE SPACE in rhel it is showing that SDA must have a GPT disk label,Please help on this issue.

Thanks

TB0ne 11-05-2013 07:42 AM

Quote:

Originally Posted by narendra42074 (Post 5058589)
Hi everyone,
When i installing rhel for duel booting the problem is with GPT disk label error when i click on INSTALL IN FREE SPACE in rhel it is showing that SDA must have a GPT disk label,Please help on this issue.

As we told piyush.sh143, this original thread was two years old, and to not re-open old threads, nor to post their own question on someone elses. Per the LQ Rules, start a new thread for a new question.

And this has been answered in this thread previously...did you read/understand/try any of the workarounds or suggestions listed? Gparted? Have you contacted Red Hat Support, since you're using RHEL?

RV11 02-25-2014 05:34 PM

Thanks for the info. I have updated user "benjulios" reply to make it correct for my system which did not allow a disk mention in the mklabel command in parted, instead one has to "select" the disk first (this is using centos 6.5);

Quote:

Originally Posted by benjulios (Post 4922106)
UPDATED procedure ( my disk was /dev/sdb - if yours is /dev/sda then change all commands to /dev/sda ) :

inject "CTRL+ALT+F2" during your installation process to go on command line with 'parted' utility.
Code:

# parted 
(parted) print /dev/sdb       
(parted) select /dev/sdb         
(parted) mklabel gpt
(parted) yes
(parted) print /dev/sdb   
(parted) quit

then return to installation process with CTRL+ALT+F6 and either follow user "benjulios" instructions, or use the right selection (from the disk partitioning/"what type of installation would you like" menu screen). I just selected "replace existing linux systems", added the right disk for my case and then edited the partitioning layout to suit.)


Xalorous 06-21-2017 07:03 PM

more details regarding this issue
 
This error still occurs, and I found out why, and I found a slightly easier way to work around the solution.

To boot from (U)EFI, the system must be on a GPT disk. If you need to remain with MBR disk partitioning, then you also need to use legacy (BIOS) boot.

In RHEL/CENTOS/SL/OEL, if you come upon the error, "sdX must have a GPT disk label", go back to the previous page, select a partitioning scheme that involves formatting the system (e.g. use entire disk), ensure 'modify partitioning scheme' is checked, and go forward again. Then modify their scheme to fit what you want to have in the end.

Now when you click next you'll get a warning window, looks just like the error window before, but this warns that you're about to destroy all the data on the disk. Choose to go forward or not. Going forward formats the disk with GPT instead of MBR, and like all such formatting, it does erase the entire disk.


All times are GMT -5. The time now is 08:25 AM.