Hello listmates,
Here's I am, trying to install Centos 6.2 64-bit on a server with 24 TB of disk RAIDed as RAID 6. So I get this 18 TB disk (the RAID is recognized as one disk) where I am trying to put my OS. And I can create a couple of partitions - let us say I defiine a 150 GB swap, a 150 GB "/", a 100 GB "/var". So far so good. Then I try to define the next one, say, a 100 GB "/tmp" and get a message stating there is not enough disk space whereas I still have over 18 TB free and the installation interface reflects that accurately!
I am at a loss. Is that something related to the sheer size of the disk? Why would this happen - especially at so basic a stage of the process?
At any rate, any help or advice would be greatly appreciated.
Regards,
Boris.
On 04/12/2012 03:14 PM, Boris Epstein wrote:
Hello listmates,
Here's I am, trying to install Centos 6.2 64-bit on a server with 24 TB of disk RAIDed as RAID 6. So I get this 18 TB disk (the RAID is recognized as one disk) where I am trying to put my OS. And I can create a couple of partitions - let us say I defiine a 150 GB swap, a 150 GB "/", a 100 GB "/var". So far so good. Then I try to define the next one, say, a 100 GB "/tmp" and get a message stating there is not enough disk space whereas I still have over 18 TB free and the installation interface reflects that accurately!
I am at a loss. Is that something related to the sheer size of the disk? Why would this happen - especially at so basic a stage of the process?
At any rate, any help or advice would be greatly appreciated.
Have you also defined a /boot partition and maybe declared all of them to be primary partitions? If so you maybe ran out of partitions rather than actual diskspace. Are you using a GPT partition table?
Regards, Dennis
On Thu, Apr 12, 2012 at 9:27 AM, Dennis Jacobfeuerborn < dennisml@conversis.de> wrote:
On 04/12/2012 03:14 PM, Boris Epstein wrote:
Hello listmates,
Here's I am, trying to install Centos 6.2 64-bit on a server with 24 TB
of
disk RAIDed as RAID 6. So I get this 18 TB disk (the RAID is recognized
as
one disk) where I am trying to put my OS. And I can create a couple of partitions - let us say I defiine a 150 GB swap, a 150 GB "/", a 100 GB "/var". So far so good. Then I try to define the next one, say, a 100 GB "/tmp" and get a message stating there is not enough disk space whereas I still have over 18 TB free and the installation interface reflects that accurately!
I am at a loss. Is that something related to the sheer size of the disk? Why would this happen - especially at so basic a stage of the process?
At any rate, any help or advice would be greatly appreciated.
Have you also defined a /boot partition and maybe declared all of them to be primary partitions? If so you maybe ran out of partitions rather than actual diskspace. Are you using a GPT partition table?
Regards, Dennis _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Dennis,
Thanks for your help.
By all appearances this is not GPT but rather MSDOS table. And this may be bad news overall. See this:
http://richardjh.org/blog/install-centos-onto-large-partitions-using-gpt-dis...
Boris.
On 04/13/2012 06:55 PM, Boris Epstein wrote:
On Thu, Apr 12, 2012 at 9:27 AM, Dennis Jacobfeuerborn< dennisml@conversis.de> wrote:
On 04/12/2012 03:14 PM, Boris Epstein wrote:
Hello listmates,
Here's I am, trying to install Centos 6.2 64-bit on a server with 24 TB
<snip>
By all appearances this is not GPT but rather MSDOS table. And this may be bad news overall. See this:
http://richardjh.org/blog/install-centos-onto-large-partitions-using-gpt-dis...
Boris.
The link you provided is for CentOS 5.0 and GPT, and you are installing CentOS 6.2. I read somewhere that CentOS 6.x creates/supports GPT tables if Disk is larger then 2TB.
- Have you initialized that RAID with MSDOS partition (manually or with older/different distro) or was it by CentOS 6.2 installation DVD? - What happens if you initialize RAID with GPT?
On Thu, Apr 19, 2012 at 3:14 PM, Ljubomir Ljubojevic office@plnet.rswrote:
On 04/13/2012 06:55 PM, Boris Epstein wrote:
On Thu, Apr 12, 2012 at 9:27 AM, Dennis Jacobfeuerborn< dennisml@conversis.de> wrote:
On 04/12/2012 03:14 PM, Boris Epstein wrote:
Hello listmates,
Here's I am, trying to install Centos 6.2 64-bit on a server with 24 TB
<snip> > By all appearances this is not GPT but rather MSDOS table. And this may be > bad news overall. See this: > > http://richardjh.org/blog/install-centos-onto-large-partitions-using-gpt-disk-layout/ > > Boris.
The link you provided is for CentOS 5.0 and GPT, and you are installing CentOS 6.2. I read somewhere that CentOS 6.x creates/supports GPT tables if Disk is larger then 2TB.
- Have you initialized that RAID with MSDOS partition (manually or with
older/different distro) or was it by CentOS 6.2 installation DVD?
- What happens if you initialize RAID with GPT?
--
Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe
Google is the Mother, Google is the Father, and traceroute is your trusty Spiderman... StarOS, Mikrotik and CentOS/RHEL/Linux consultant _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Ljubomir,
The installation program definitely does not seem to prompt you and offer you an opportunity to initialize the disk with any disk table format.
Boris.
On 04/20/2012 11:08 PM, Boris Epstein wrote:
On Thu, Apr 19, 2012 at 3:14 PM, Ljubomir Ljubojevicoffice@plnet.rswrote:
On 04/13/2012 06:55 PM, Boris Epstein wrote:
On Thu, Apr 12, 2012 at 9:27 AM, Dennis Jacobfeuerborn< dennisml@conversis.de> wrote:
On 04/12/2012 03:14 PM, Boris Epstein wrote:
Hello listmates,
Here's I am, trying to install Centos 6.2 64-bit on a server with 24 TB
<snip> > By all appearances this is not GPT but rather MSDOS table. And this may be > bad news overall. See this: > > http://richardjh.org/blog/install-centos-onto-large-partitions-using-gpt-disk-layout/ > > Boris.
The link you provided is for CentOS 5.0 and GPT, and you are installing CentOS 6.2. I read somewhere that CentOS 6.x creates/supports GPT tables if Disk is larger then 2TB.
- Have you initialized that RAID with MSDOS partition (manually or with
older/different distro) or was it by CentOS 6.2 installation DVD?
- What happens if you initialize RAID with GPT?
Ljubomir,
The installation program definitely does not seem to prompt you and offer you an opportunity to initialize the disk with any disk table format.
Boris.
Yeah, I just read a thread about it in this mailing list: On 04/18/2012 10:18 AM, John R Pierce wrote:
do I need to preboot into a shell or something and use parted before I can install ?
I use a bootable CD with gparted to create the GPT partition table and the partitions.
After this, I can boot CentOS and install on the created partitions.
Mogens
Thread is named "3TB system drive partitioning question", from 2 days ago.
Yeah, I just read a thread about it in this mailing list: On 04/18/2012 10:18 AM, John R Pierce wrote:
do I need to preboot into a shell or something and use parted before I can install ?
I use a bootable CD with gparted to create the GPT partition table and the partitions.
After this, I can boot CentOS and install on the created partitions.
Mogens
Thread is named "3TB system drive partitioning question", from 2 days ago.
--
Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe
OK, I just used Gparted Live ( http://gparted.sourceforge.net/livecd.php , a very useful distro, by the way) to create a GPT partitioned disk. Then I booted the netinstall for CentOS 6.2 - and it just fails to see the data on that disk! It wants to wipe it clean - apparently, to create an MS-DOS partition on it!
How do I get around this now? In short - and this is a question for everybody - how do I install CentOS 6.2 on a GPT partitioned drive, or create a GPT partition as I go?
Thanks.
Boris.
On 04/23/12 2:34 PM, Boris Epstein wrote:
OK, I just used Gparted Live (http://gparted.sourceforge.net/livecd.php , a very useful distro, by the way) to create a GPT partitioned disk. Then I booted the netinstall for CentOS 6.2 - and it just fails to see the data on that disk! It wants to wipe it clean - apparently, to create an MS-DOS partition on it!
How do I get around this now? In short - and this is a question for everybody - how do I install CentOS 6.2 on a GPT partitioned drive, or create a GPT partition as I go?
I ended up partitioning the system drive MBR and living with a 2TB limit. the system I'm on doesn't support EFI or whatever the new boot standard is, so it can't boot off a GPT disk anyways. I'm loosing 700GB from that first volume.... but I've got 20 more 3TB drives in this server for data storage, so not a big problem.
On 04/23/2012 11:44 PM, John R Pierce wrote:
On 04/23/12 2:34 PM, Boris Epstein wrote:
OK, I just used Gparted Live (http://gparted.sourceforge.net/livecd.php , a very useful distro, by the way) to create a GPT partitioned disk. Then I booted the netinstall for CentOS 6.2 - and it just fails to see the data on that disk! It wants to wipe it clean - apparently, to create an MS-DOS partition on it!
How do I get around this now? In short - and this is a question for everybody - how do I install CentOS 6.2 on a GPT partitioned drive, or create a GPT partition as I go?
I ended up partitioning the system drive MBR and living with a 2TB limit. the system I'm on doesn't support EFI or whatever the new boot standard is, so it can't boot off a GPT disk anyways. I'm loosing 700GB from that first volume.... but I've got 20 more 3TB drives in this server for data storage, so not a big problem.
You could use LVM. Just create 2TB partitions and use them as physical volumes for a large volume group. Then just create one big logical volume from that volume group.
Regards, Dennis
On Mon, Apr 23, 2012 at 7:56 PM, Dennis Jacobfeuerborn < dennisml@conversis.de> wrote:
On 04/23/2012 11:44 PM, John R Pierce wrote:
On 04/23/12 2:34 PM, Boris Epstein wrote:
OK, I just used Gparted Live (http://gparted.sourceforge.net/livecd.php , a very useful distro, by the way) to create a GPT partitioned disk.
Then I
booted the netinstall for CentOS 6.2 - and it just fails to see the
data on
that disk! It wants to wipe it clean - apparently, to create an MS-DOS partition on it!
How do I get around this now? In short - and this is a question for everybody - how do I install CentOS 6.2 on a GPT partitioned drive, or create a GPT partition as I go?
I ended up partitioning the system drive MBR and living with a 2TB limit. the system I'm on doesn't support EFI or whatever the new boot standard is, so it can't boot off a GPT disk anyways. I'm loosing 700GB from that first volume.... but I've got 20 more 3TB drives in this server for data storage, so not a big problem.
You could use LVM. Just create 2TB partitions and use them as physical volumes for a large volume group. Then just create one big logical volume from that volume group.
Regards, Dennis _______________________________________________
Dennis,
Thanks! The controller I've got (I believe it is a 3Ware 9000 series) - I think that controller does not allow you to create hardware slices on top of a RAID'ed disk (volume). But that is a good idea in general. I used that approach on a couple of HP Proliant servers and that worked.
Boris.
On 04/23/12 5:33 PM, Boris Epstein wrote:
Thanks! The controller I've got (I believe it is a 3Ware 9000 series) - I think that controller does not allow you to create hardware slices on top of a RAID'ed disk (volume). But that is a good idea in general. I used that approach on a couple of HP Proliant servers and that worked.
really? I've never run into ANY sort of hardware raid that had any such restrictions. I've not used the 3ware stuff, but I've used lots of LSI Logic raid (9260-8i, etc), HP SmartArray stuff (p410, etc), Dell PERC stuff, etc etc.
anyways, I'm dealing with a pair of single 3TB (2.78 TiB) drives in a mdraid mirror here as the system disk.
On 04/23/12 4:56 PM, Dennis Jacobfeuerborn wrote:
You could use LVM. Just create 2TB partitions and use them as physical volumes for a large volume group. Then just create one big logical volume from that volume group.
um, LVM can't see over 2TB of the drive either, unless its formatted GPT, whereupon it can't be used as a boot device on a non-EFI system.
On 04/24/2012 03:20 AM, John R Pierce wrote:
On 04/23/12 5:33 PM, Boris Epstein wrote:
Thanks! The controller I've got (I believe it is a 3Ware 9000 series) - I think that controller does not allow you to create hardware slices on top of a RAID'ed disk (volume). But that is a good idea in general. I used that approach on a couple of HP Proliant servers and that worked.
really? I've never run into ANY sort of hardware raid that had any such restrictions. I've not used the 3ware stuff, but I've used lots of LSI Logic raid (9260-8i, etc), HP SmartArray stuff (p410, etc), Dell PERC stuff, etc etc.
anyways, I'm dealing with a pair of single 3TB (2.78 TiB) drives in a mdraid mirror here as the system disk.
On 04/23/12 4:56 PM, Dennis Jacobfeuerborn wrote:
You could use LVM. Just create 2TB partitions and use them as physical volumes for a large volume group. Then just create one big logical volume from that volume group.
um, LVM can't see over 2TB of the drive either, unless its formatted GPT, whereupon it can't be used as a boot device on a non-EFI system.
The idea is to create multiple 2TB partitions.
In one specific case I set up a 4TB System by creating a 1G boot volume and 3.99T system volume. Then I created two 2T partitions on the system volume, formatted them as physical volumes and added them to the main volume group. Then you can create a 4T logical volume if you like.
Regards, Dennis
On 04/23/12 8:31 PM, Dennis Jacobfeuerborn wrote:
um, LVM can't see over 2TB of the drive either, unless its formatted
GPT, whereupon it can't be used as a boot device on a non-EFI system.
The idea is to create multiple 2TB partitions.
In one specific case I set up a 4TB System by creating a 1G boot volume and 3.99T system volume. Then I created two 2T partitions on the system volume, formatted them as physical volumes and added them to the main volume group. Then you can create a 4T logical volume if you like.
how do I create two disks from one 3TB JBOD ?
On 04/24/2012 05:38 AM, John R Pierce wrote:
On 04/23/12 8:31 PM, Dennis Jacobfeuerborn wrote:
um, LVM can't see over 2TB of the drive either, unless its formatted
GPT, whereupon it can't be used as a boot device on a non-EFI system.
The idea is to create multiple 2TB partitions.
In one specific case I set up a 4TB System by creating a 1G boot volume and 3.99T system volume. Then I created two 2T partitions on the system volume, formatted them as physical volumes and added them to the main volume group. Then you can create a 4T logical volume if you like.
how do I create two disks from one 3TB JBOD ?
I used the raid controller for this. On a regular disk you just create two partitions I guess.
Regards, Dennis
On 04/24/12 4:46 AM, Dennis Jacobfeuerborn wrote:
I used the raid controller for this. On a regular disk you just create two partitions I guess.
which part of MBR not supporting disks over 2TB do you not understand? you have to use GPT to put a partition past 2^32 * 512 bytes == 2TiB
On 4/24/2012 1:32 PM, John R Pierce wrote:
On 04/24/12 4:46 AM, Dennis Jacobfeuerborn wrote:
I used the raid controller for this. On a regular disk you just create two partitions I guess.
which part of MBR not supporting disks over 2TB do you not understand? you have to use GPT to put a partition past 2^32 * 512 bytes == 2TiB
I think there's something being lost in translation here.
As I understand it, he is suggesting using the raid controller to create multiple "slices" from the disk (or raid unit). Each of these slices is less than 2TB and is presented to the system as a separate drive. Rather than a single 4TB drive, the OS now sees two 2TB drives and is able to partition each one separately.
Here's the low-tech approach: put /boot on a memory stick, and boot from that (assuming your BIOS can be set to boot of a USD device). /boot usually only get access when you do kernel updates.
Ge,
Thanks! I am afraid that will still not address the issue of how I would partition the drive for the installation.
Boris.
On Tue, Apr 24, 2012 at 4:43 PM, Gé Weijers ge@weijers.org wrote:
Here's the low-tech approach: put /boot on a memory stick, and boot from that (assuming your BIOS can be set to boot of a USD device). /boot usually only get access when you do kernel updates.
-- Gé _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
2012/4/24 Boris Epstein borepstein@gmail.com:
Ge,
Thanks! I am afraid that will still not address the issue of how I would partition the drive for the installation.
Boris.
On Tue, Apr 24, 2012 at 4:43 PM, Gé Weijers ge@weijers.org wrote:
Here's the low-tech approach: put /boot on a memory stick, and boot from that (assuming your BIOS can be set to boot of a USD device). /boot usually only get access when you do kernel updates.
How about creating raid with two slices: one small (30GB) for installation and rest for data partition.
Anyway, with 18TB of raid 6 might cause performance problems .. raid 60 or raid 10 looks much better solution.
-- Eero
On Tue, Apr 24, 2012 at 5:24 PM, Eero Volotinen eero.volotinen@iki.fiwrote:
2012/4/24 Boris Epstein borepstein@gmail.com:
Ge,
Thanks! I am afraid that will still not address the issue of how I would partition the drive for the installation.
Boris.
On Tue, Apr 24, 2012 at 4:43 PM, Gé Weijers ge@weijers.org wrote:
Here's the low-tech approach: put /boot on a memory stick, and boot from that (assuming your BIOS can be set to boot of a USD device). /boot usually only get access when you do kernel updates.
How about creating raid with two slices: one small (30GB) for installation and rest for data partition.
Anyway, with 18TB of raid 6 might cause performance problems .. raid 60 or raid 10 looks much better solution.
-- Eero _______________________________________________
Eero,
I am going to look into how to create those slices; problem is, it may or may not be possible.
Boris.
On 04/24/12 2:24 PM, Eero Volotinen wrote:
Anyway, with 18TB of raid 6 might cause performance problems .. raid 60 or raid 10 looks much better solution.
18TB of raid6 is only 8 3TB drives (6 + 2 parity).... thats not an unreasonable size for a raid6 set.
for the 81TB nearline storage boxes I built for a data archive application, I formatted each box (using a megaraid sas2 9260-8i card and 36 3TB SAS drives) as 3 x 11 x raid60, plus 3 hot spares, and then made one big XFS on that. Its working out quite nicely. I think 10 or 12 disks per raid5 or 6 is a good upper limit. rebuild time from a single failure was 12 hours, and from a double failure in the same raid plex, 18 hours.
On Tue, Apr 24, 2012 at 10:17 PM, John R Pierce pierce@hogranch.com wrote:
On 04/24/12 2:24 PM, Eero Volotinen wrote:
Anyway, with 18TB of raid 6 might cause performance problems .. raid 60 or raid 10 looks much better solution.
18TB of raid6 is only 8 3TB drives (6 + 2 parity).... thats not an unreasonable size for a raid6 set.
for the 81TB nearline storage boxes I built for a data archive application, I formatted each box (using a megaraid sas2 9260-8i card and 36 3TB SAS drives) as 3 x 11 x raid60, plus 3 hot spares, and then made one big XFS on that. Its working out quite nicely. I think 10 or 12 disks per raid5 or 6 is a good upper limit. rebuild time from a single failure was 12 hours, and from a double failure in the same raid plex, 18 hours.
-- john r pierce N 37, W 122 santa cruz ca mid-left coast
Actually in our case we've got 12 2TB drives - but still I think John's point stands.
Boris.
24.4.2012 23:52, Boris Epstein kirjoitti:
Thanks! I am afraid that will still not address the issue of how I would partition the drive for the installation.
Don't partition it at all, assign the whole drive as a LVM physical volume.
On Tue, Apr 24, 2012 at 5:29 PM, Markku Kolkka markku.kolkka@saunalahti.fiwrote:
24.4.2012 23:52, Boris Epstein kirjoitti:
Thanks! I am afraid that will still not address the issue of how I would partition the drive for the installation.
Don't partition it at all, assign the whole drive as a LVM physical volume.
-- Markku Kolkka markku.kolkka@iki.fi _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Yes, that could work provided I have disk slices to work with. Which I don't at the time of installation as the installation utility does not allow me to partition disks under LPT, only under the MSDOS label which imposes the 2TB limit.
Boris.
2012/4/25 Markku Kolkka markku.kolkka@saunalahti.fi:
24.4.2012 23:52, Boris Epstein kirjoitti:
Thanks! I am afraid that will still not address the issue of how I would partition the drive for the installation.
Don't partition it at all, assign the whole drive as a LVM physical volume.
Is it really possible to boot from 18TB lvm partition? with mbr? with grub?
http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-lvm-diskdruid-ma...
well. no?
"The /boot/ partition cannot reside on an LVM volume because the GRUB boot loader cannot read it"
-- Eero
2012/4/25 Eero Volotinen eero.volotinen@iki.fi:
2012/4/25 Markku Kolkka markku.kolkka@saunalahti.fi:
24.4.2012 23:52, Boris Epstein kirjoitti:
Thanks! I am afraid that will still not address the issue of how I would partition the drive for the installation.
Don't partition it at all, assign the whole drive as a LVM physical volume.
Is it really possible to boot from 18TB lvm partition? with mbr? with grub?
http://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-lvm-diskdruid-ma...
well. no?
"The /boot/ partition cannot reside on an LVM volume because the GRUB boot loader cannot read it"
I think best solution is to slice raid into two volumes in raid manager or install delicated boot disk inside the server, if possible?
-- Eero
25.4.2012 0:33, Eero Volotinen kirjoitti:
2012/4/25 Markku Kolkka markku.kolkka@saunalahti.fi:
24.4.2012 23:52, Boris Epstein kirjoitti:
Thanks! I am afraid that will still not address the issue of how I would partition the drive for the installation.
Don't partition it at all, assign the whole drive as a LVM physical volume.
Is it really possible to boot from 18TB lvm partition? with mbr? with grub?
You missed the previous post where it was suggested to put /boot on a memory stick. /boot on a separate device + 18TB unpartitioned device as a PV should work.
On Tue, Apr 24, 2012 at 1:52 PM, Boris Epstein borepstein@gmail.com wrote:
Ge,
Thanks! I am afraid that will still not address the issue of how I would partition the drive for the installation.
Any way you'd like. CentOS can't BOOT from a GPT partitioned device if the BIOS does not support it, but you can certainly use GPT on non-boot devices.
On Tuesday, April 24, 2012 05:40:50 PM Gé Weijers wrote:
Any way you'd like. CentOS can't BOOT from a GPT partitioned device if the BIOS does not support it, but you can certainly use GPT on non-boot devices.
While I can't confirm for a drive larger than 2TB, it is not true that you can't boot a Linux kernel close to the one in CentOS using a GRUB similar to the one in CentOS from a GPT partitioned disk. People are doing this all the time using bootloaders like Chameleon and PCEFI (used typically to build a 'hackintosh'), dual-booting with Mac OS X on semi-generic PC hardware.
Here's what the GPT looks like for such a system, dual-booting Fedora 14 and Mac OS X (using gdisk): [root@localhost ~]# gdisk -l /dev/sda GPT fdisk (gdisk) version 0.8.1
Partition table scan: MBR: protective BSD: not present APM: not present GPT: present
Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): 1BE631E1-4E0C-4D33-9108-9F7E5EBB411A Partition table holds up to 128 entries First usable sector is 34, last usable sector is 976773134 Partitions will be aligned on 8-sector boundaries Total free space is 525717 sectors (256.7 MiB)
Number Start (sector) End (sector) Size Code Name 1 40 409639 200.0 MiB EF00 EFI System Partition 2 409640 386210423 184.0 GiB AF00 Flopdinger 3 386473984 402104319 7.5 GiB 8200 LinuxSwap 4 402104320 484024319 39.1 GiB 0700 F14 5 484024320 861511679 180.0 GiB 0700 LinuxHome 6 861511680 976510983 54.8 GiB AF00 Interchange [root@localhost ~]#
Using parted -l: [root@localhost ~]# parted -l Model: ATA ST9500420AS (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: gpt
Number Start End Size File system Name Flags 1 20.5kB 210MB 210MB fat32 EFI System Partition boot, hidden 2 210MB 198GB 198GB hfs+ Flopdinger hidden 3 198GB 206GB 8003MB linux-swap(v1) LinuxSwap 4 206GB 248GB 41.9GB ext3 F14 5 248GB 441GB 193GB ext3 LinuxHome hidden 6 441GB 500GB 58.9GB hfsx Interchange hidden
[root@localhost ~]#
Installation of the GRUB bootloader is simple; it's installed to /dev/sda4 instead of /dev/sda (since Chameleon is sitting in the MBR and in the EFI system partition): [root@localhost ~]# cat /boot/grub/menu.lst # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, eg. # root (hd0,3) # kernel /boot/vmlinuz-version ro root=/dev/sda4 # initrd /boot/initrd-[generic-]version.img #boot=/dev/sda4 default=0 timeout=9 splashimage=(hd0,3)/boot/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.35.14-106.fc14.x86_64) root (hd0,3) kernel /boot/vmlinuz-2.6.35.14-106.fc14.x86_64 ro root=UUID=8cda63bd-9eed-4a65-a834-138df5dca1a2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet nouveau.modeset=0 rdblacklist=nouveau initrd /boot/initramfs-2.6.35.14-106.fc14.x86_64.img
Booting a generic BIOS PC from GPT is a solved problem, just not in the 'usual' Linux space.
-
Boris Epstein -
Bowie Bailey -
Dennis Jacobfeuerborn -
Eero Volotinen -
Gé Weijers -
John R Pierce -
Lamar Owen -
Ljubomir Ljubojevic -
Markku Kolkka