Hi,
If you have partition larger than 2TB you need to use GPT. Why are you avoiding the use of GPT? What is the harm using it? Why is the use of it unacceptable?
Cheers,
K.
Main Topics
Browse All TopicsHello all,
My company is trying to install CentOS 5.3 x64 on to a 3TB RAID6 volume that was configured using a ServeRaid 8k on an IBM x3650. The problem we keep running into is that the anaconda installer see's that the disk is 3TB and then rewrites our msdos partition table as GPT. This is unacceptable as our server is not Itanium nor does it have EFI.
We tried reverting the changes to the partition table made by anaconda using dd to zero out the first 64 and last 9000 sectors on the disk. After that we used fdisk to create a partition structure:
Using /dev/sda
Model: ServeRA SERVER (scsi)
Disk /dev/sda: 3000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 518MB 518MB primary ext3 boot
2 518MB 1469GB 1468GB primary lvm
3 1469GB 3000GB 1532GB primary lvm
Unfortunately, anaconda isn't able to recognize the msdos partition table when the installer is restarted and it only gives us the option to try and clear the partition table, resulting in the disk being partitioned using GPT again.
The only reason I think that I am able to get around using GPT is because another server in our office with the same specs is running CentOS fine using the same partition layout. Any pointers or advice would be appreciated. We would like to avoid having to use GPT for the 3TB volume and then a separate device for /boot.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
GPT can be made bootable on BIOS-based systems by adding a BIOS boot partition, see http://grub.enbug.org/BIOS
Turns out that the CentOS5.3 installer didn't like the size of the RAID6 volume so it kept overwriting the partition table using GPT. We had managed to use a msdos partition table with another server running CentOS5.2. The steps I took get my desired result were:
Creating a msdos partitioning scheme as follows using a gparted boot CD:
/dev/sda1 128MB ext3 (/boot)
/dev/sda2 1.5TB LVM
/dev/sda3 ~1.5TB LVM
I then used a CentOS5.2 install DVD with GUI anaconda. It did not complain about the large disk size. In the anaconda partition manager we added the two 1.5 TB together to make one large 3TB LVM volume. After installation completed, we just ran yum upgrade to get our system up to CentOS5.3.
> Creating a msdos partitioning scheme as follows using a gparted boot CD:
This is simply impossible.
You can create such partitioning tables, but kernel will not use it - I have tried that.
You sure it's msdos partition scheme? Gpartes is creating GPT partition tables... Maybe You only think You have creates msdos partition table?
Uniserveps,
Having an Itanium or EFI system is not a requirement for GPT booting at all; GPT is backwards-compatible with BIOS systems (only the boot loader needs to be GPT-aware, which is true for GRUB2 and a patch for GRUB-Legacy also exists, presumably incorporated into CentOS). In fact, when writing gptgen, I heavily relied on VMware Workstation's ability to boot from GPT for testing on Linux (VMware emulates an Intel 440BX chipset with an AMI-like BIOS, and has absolutely no support for EFI).
As ravenpl said, please post the output of "fdisk -l /dev/sda".
Business Accounts
Answer for Membership
by: ravenplPosted on 2009-07-17 at 13:13:03ID: 24882456
Well this is well known msdos partition format shortcoming - 2TB is the limit.
Verify, if the controlled is capable of creating boot partition on the raid6 volume. This way You can have small boot disk, then large data disk. The large disk of course have to use GPT if larger than 2TB.