Difference between revisions of "Installing CentOS/RedHat on disks larger than 2Tb"

From Peter Pap's Technowiki
Jump to: navigation, search
(Created page with "So you have a new server that has a lot of disk! The classic example is you have a server with 8 x 1Tb drives or something similar and you do not want to be restricted to using ...")
 
Line 1: Line 1:
So you have a new server that has a lot of disk!  The classic example is you have a server with 8 x 1Tb drives or something similar and you do not want to be restricted to using only 2Tb of disk, as dictated by the default MSDOS disk label.  You may read things about using EFI instead of BIOS, but that can be a massive hassle.  The easier way to get this happening is to use a Guid Partition Table (GPT) disk label.  This will allow you to have partitions greater than 2Tb without having to change from using BIOS to EFI.  The method I describe here is a little fiddly, but it works.  You will need a [http://gparted.sourceforge.net/ GParted Live CD]
+
So you have a new server that has a lot of disk!  The classic example is you have a server with 8 x 1Tb drives or something similar and you do not want to be restricted to using only 2Tb of disk, as dictated by the default MSDOS disk label.  You've set up a RAID-5 or 6 array using these drives and want to use all the available space.  You may read things about using EFI instead of BIOS, but that can be a massive hassle.  The easier way to get this happening is to use a Guid Partition Table (GPT) disk label.  This will allow you to have partitions greater than 2Tb without having to change from using BIOS to EFI.  The method I describe here is a little fiddly, but it works.  You will need a [http://gparted.sourceforge.net/ GParted Live CD] and a Kickstart server. 
 +
 
 +
1. Download the GParted ISO image and boot off it. 
 +
 
 +
NOTE: If you don't want to use the GParted ISO, then use any Live CD that has parted on it.
 +
 
 +
2. If there are no existing partitions go to step 3.  If there are any partitions, delete them using either the GUI or the following commands:
 +
 
 +
a. List the current partitions:
 +
 
 +
  sudo bash
 +
  parted /dev/sda print
 +
 
 +
Output will look something like:
 +
 
 +
  Disk /dev/sda: 6998GB
 +
  Sector size (logocal/physical): 512B/512B
 +
  Partition Table: gpt
 +
 
 +
  Number  Start  End    Size    File system  Name  Flags
 +
  1      1049kB  525MB  524MB  ext4              boot
 +
  2      525MB  6998GB  6997GB                    lvm
 +
 
 +
b. Delete the partitions you saw in the output of the previous command
 +
 
 +
  parted /dev/sda rm 1
 +
  parted /dev/sda rm 2
 +
 
 +
3.

Revision as of 03:28, 1 March 2012

So you have a new server that has a lot of disk! The classic example is you have a server with 8 x 1Tb drives or something similar and you do not want to be restricted to using only 2Tb of disk, as dictated by the default MSDOS disk label. You've set up a RAID-5 or 6 array using these drives and want to use all the available space. You may read things about using EFI instead of BIOS, but that can be a massive hassle. The easier way to get this happening is to use a Guid Partition Table (GPT) disk label. This will allow you to have partitions greater than 2Tb without having to change from using BIOS to EFI. The method I describe here is a little fiddly, but it works. You will need a GParted Live CD and a Kickstart server.

1. Download the GParted ISO image and boot off it.

NOTE: If you don't want to use the GParted ISO, then use any Live CD that has parted on it.

2. If there are no existing partitions go to step 3. If there are any partitions, delete them using either the GUI or the following commands:

a. List the current partitions:

 sudo bash
 parted /dev/sda print

Output will look something like:

 Disk /dev/sda: 6998GB
 Sector size (logocal/physical): 512B/512B
 Partition Table: gpt
 
 Number  Start   End     Size    File system  Name  Flags
  1      1049kB  525MB   524MB   ext4               boot
  2      525MB   6998GB  6997GB                     lvm

b. Delete the partitions you saw in the output of the previous command

 parted /dev/sda rm 1
 parted /dev/sda rm 2

3.