One of these days, we are going to get GPT partitioned disks good, bad, or indifferent. In "regular" install mode with automatic configuration, the "bootbios" partition is automatically allocated. In "regular" install mode with custom configuration, you cannot proceed until a 1MB "bootbios" partition have been comfigured. [I am not sure if this has to be the first thing configured or not.]
So, what should be done with kickstart where gpt is specified as the kernel parameter and something like: clearpart --all --initlabel --drives=vda is specified? Alternates:
1. Add option(s) to part for creation of the "bootbios" partitions or (and better) 2. Make allocation of the "bootbios" partition part of "clearpart" processing.
I notice that clearpart --initlabel not does "gpt" for itanium.
Comments?
Gene
On Sun, 2013-10-27 at 12:04 -0400, Gene Czarcinski wrote:
One of these days, we are going to get GPT partitioned disks good, bad, or indifferent. In "regular" install mode with automatic configuration, the "bootbios" partition is automatically allocated. In "regular" install mode with custom configuration, you cannot proceed until a 1MB "bootbios" partition have been comfigured. [I am not sure if this has to be the first thing configured or not.]
So, what should be done with kickstart where gpt is specified as the kernel parameter and something like: clearpart --all --initlabel --drives=vda is specified? Alternates:
- Add option(s) to part for creation of the "bootbios" partitions
or (and better)
If you use autopart, biosboot will be created as necessary. If not, you must add a line like the following:
part biosboot --size=1
On 11/12/2013 08:47 AM, David Lehman wrote:
On Sun, 2013-10-27 at 12:04 -0400, Gene Czarcinski wrote:
One of these days, we are going to get GPT partitioned disks good, bad, or indifferent. In "regular" install mode with automatic configuration, the "bootbios" partition is automatically allocated. In "regular" install mode with custom configuration, you cannot proceed until a 1MB "bootbios" partition have been comfigured. [I am not sure if this has to be the first thing configured or not.]
So, what should be done with kickstart where gpt is specified as the kernel parameter and something like: clearpart --all --initlabel --drives=vda is specified? Alternates:
- Add option(s) to part for creation of the "bootbios" partitions
or (and better)
If you use autopart, biosboot will be created as necessary. If not, you must add a line like the following:
part biosboot --size=1
Yep, got it. Works nicely too. I do not know if you can mix and match but I assume not so I just stuck one on the front of the two SSDs and the two USB drives that I am using for data storage.
However, I do believe that it would be helpful if the kickstart documentation had some of the special types of partitions such as biosboot mentioned under part or partition. Now that I know about them I will know that I should look for them but it could be helpful to others.
Gene
On Tue, 2013-11-12 at 12:44 -0500, Gene Czarcinski wrote:
On 11/12/2013 08:47 AM, David Lehman wrote:
On Sun, 2013-10-27 at 12:04 -0400, Gene Czarcinski wrote:
One of these days, we are going to get GPT partitioned disks good, bad, or indifferent. In "regular" install mode with automatic configuration, the "bootbios" partition is automatically allocated. In "regular" install mode with custom configuration, you cannot proceed until a 1MB "bootbios" partition have been comfigured. [I am not sure if this has to be the first thing configured or not.]
So, what should be done with kickstart where gpt is specified as the kernel parameter and something like: clearpart --all --initlabel --drives=vda is specified? Alternates:
- Add option(s) to part for creation of the "bootbios" partitions
or (and better)
If you use autopart, biosboot will be created as necessary. If not, you must add a line like the following:
part biosboot --size=1
Yep, got it. Works nicely too. I do not know if you can mix and match but I assume not so I just stuck one on the front of the two SSDs and the two USB drives that I am using for data storage.
You only need the partition on the drive that actually contains the bootloader, AIUI.
On Nov 12, 2013, at 12:04 PM, Adam Williamson awilliam@redhat.com wrote:
On Tue, 2013-11-12 at 12:44 -0500, Gene Czarcinski wrote:
On 11/12/2013 08:47 AM, David Lehman wrote:
On Sun, 2013-10-27 at 12:04 -0400, Gene Czarcinski wrote:
One of these days, we are going to get GPT partitioned disks good, bad, or indifferent. In "regular" install mode with automatic configuration, the "bootbios" partition is automatically allocated. In "regular" install mode with custom configuration, you cannot proceed until a 1MB "bootbios" partition have been comfigured. [I am not sure if this has to be the first thing configured or not.]
So, what should be done with kickstart where gpt is specified as the kernel parameter and something like: clearpart --all --initlabel --drives=vda is specified? Alternates:
- Add option(s) to part for creation of the "bootbios" partitions
or (and better)
If you use autopart, biosboot will be created as necessary. If not, you must add a line like the following:
part biosboot --size=1
Yep, got it. Works nicely too. I do not know if you can mix and match but I assume not so I just stuck one on the front of the two SSDs and the two USB drives that I am using for data storage.
You only need the partition on the drive that actually contains the bootloader, AIUI.
In the case of multiple device booting, each physical drive needs biosboot and the 440 bytes of boot code in the MBR. The only practical examples I can think of are raid1 or raid10, even though GRUB2 can boot from /boot on raid0, 5 and 6. Probably need to re-test installing /boot on raid1 and then yanking each drive (separately) to see if the system still boots degraded.
Chris Murphy
anaconda-devel@lists.fedoraproject.org
-
Adam Williamson -
Chris Murphy -
David Lehman -
Gene Czarcinski -
Gene Czarcinski