How to force GPT partitions in kickstart for Oracle Linux 6
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I want to configure OL6 kickstart to install a system that boots from BIOS but uses GPT partitioning instead of MBR, even for disks <2TB.
The relevant part of my kickstart file looks like this ($ROOTDRIVE
has been correctly initialized):
%pre
parted -s $ROOTDRIVE mklabel gpt
bootloader --location=partition --append="elevator=deadline nomodeset inst.gpt" --driveorder=$ROOTDRIVE
part biosboot --fstype biosboot --size=1 --ondisk=$ROOTDRIVE
part /boot --fstype ext3 --size=500 --ondisk=$ROOTDRIVE
part pv.2 --size=1 --grow --ondisk=$ROOTDRIVE`
I have removed clearpart --all --drives=$ROOTDRIVE
and zerombr
as these supposedly wipe my parted
GPT and reinstate MBR.
I believe the following in my conf should result in GPT:
parted mklabel gpt
--location=partition
(not sure if I really need this?)inst.gpt
(may be available in OL7 only?)part biosboot
Yet my resulting system still lists the primary drive as MBR (msdos
label):
[root@localhost ~]$ parted -l
Model: VMware Virtual disk (scsi)
Disk /dev/sda: 172GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
My question: is there any kickstart config I can use to ensure I end up with GPT disks rather than MBR?
linux gpt mbr kickstart
add a comment |
up vote
0
down vote
favorite
I want to configure OL6 kickstart to install a system that boots from BIOS but uses GPT partitioning instead of MBR, even for disks <2TB.
The relevant part of my kickstart file looks like this ($ROOTDRIVE
has been correctly initialized):
%pre
parted -s $ROOTDRIVE mklabel gpt
bootloader --location=partition --append="elevator=deadline nomodeset inst.gpt" --driveorder=$ROOTDRIVE
part biosboot --fstype biosboot --size=1 --ondisk=$ROOTDRIVE
part /boot --fstype ext3 --size=500 --ondisk=$ROOTDRIVE
part pv.2 --size=1 --grow --ondisk=$ROOTDRIVE`
I have removed clearpart --all --drives=$ROOTDRIVE
and zerombr
as these supposedly wipe my parted
GPT and reinstate MBR.
I believe the following in my conf should result in GPT:
parted mklabel gpt
--location=partition
(not sure if I really need this?)inst.gpt
(may be available in OL7 only?)part biosboot
Yet my resulting system still lists the primary drive as MBR (msdos
label):
[root@localhost ~]$ parted -l
Model: VMware Virtual disk (scsi)
Disk /dev/sda: 172GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
My question: is there any kickstart config I can use to ensure I end up with GPT disks rather than MBR?
linux gpt mbr kickstart
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I want to configure OL6 kickstart to install a system that boots from BIOS but uses GPT partitioning instead of MBR, even for disks <2TB.
The relevant part of my kickstart file looks like this ($ROOTDRIVE
has been correctly initialized):
%pre
parted -s $ROOTDRIVE mklabel gpt
bootloader --location=partition --append="elevator=deadline nomodeset inst.gpt" --driveorder=$ROOTDRIVE
part biosboot --fstype biosboot --size=1 --ondisk=$ROOTDRIVE
part /boot --fstype ext3 --size=500 --ondisk=$ROOTDRIVE
part pv.2 --size=1 --grow --ondisk=$ROOTDRIVE`
I have removed clearpart --all --drives=$ROOTDRIVE
and zerombr
as these supposedly wipe my parted
GPT and reinstate MBR.
I believe the following in my conf should result in GPT:
parted mklabel gpt
--location=partition
(not sure if I really need this?)inst.gpt
(may be available in OL7 only?)part biosboot
Yet my resulting system still lists the primary drive as MBR (msdos
label):
[root@localhost ~]$ parted -l
Model: VMware Virtual disk (scsi)
Disk /dev/sda: 172GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
My question: is there any kickstart config I can use to ensure I end up with GPT disks rather than MBR?
linux gpt mbr kickstart
I want to configure OL6 kickstart to install a system that boots from BIOS but uses GPT partitioning instead of MBR, even for disks <2TB.
The relevant part of my kickstart file looks like this ($ROOTDRIVE
has been correctly initialized):
%pre
parted -s $ROOTDRIVE mklabel gpt
bootloader --location=partition --append="elevator=deadline nomodeset inst.gpt" --driveorder=$ROOTDRIVE
part biosboot --fstype biosboot --size=1 --ondisk=$ROOTDRIVE
part /boot --fstype ext3 --size=500 --ondisk=$ROOTDRIVE
part pv.2 --size=1 --grow --ondisk=$ROOTDRIVE`
I have removed clearpart --all --drives=$ROOTDRIVE
and zerombr
as these supposedly wipe my parted
GPT and reinstate MBR.
I believe the following in my conf should result in GPT:
parted mklabel gpt
--location=partition
(not sure if I really need this?)inst.gpt
(may be available in OL7 only?)part biosboot
Yet my resulting system still lists the primary drive as MBR (msdos
label):
[root@localhost ~]$ parted -l
Model: VMware Virtual disk (scsi)
Disk /dev/sda: 172GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
My question: is there any kickstart config I can use to ensure I end up with GPT disks rather than MBR?
linux gpt mbr kickstart
linux gpt mbr kickstart
edited Dec 5 at 17:02
Jeff Schaller
37.9k1053123
37.9k1053123
asked Dec 5 at 16:40
Neal Eastwood
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Newer versions of kickstart have a --disklabel
flag for the clearpart
option that can be set to gpt
. It appears this was added in Fedora21/RHEL7 so I am not sure if it is available in OL6.
There is an older flag to clearpart
, --initlabel
, that mentions it "initializes the disk label to the default for your architecture" and would use gpt
for Itanium architecture.
If no usable options exist in your version of kickstart, you can configure the disks in the kickstart preinstall script. You could use parted
scripting, or whatever tool you use to configure your disks/RAID.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486190%2fhow-to-force-gpt-partitions-in-kickstart-for-oracle-linux-6%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Newer versions of kickstart have a --disklabel
flag for the clearpart
option that can be set to gpt
. It appears this was added in Fedora21/RHEL7 so I am not sure if it is available in OL6.
There is an older flag to clearpart
, --initlabel
, that mentions it "initializes the disk label to the default for your architecture" and would use gpt
for Itanium architecture.
If no usable options exist in your version of kickstart, you can configure the disks in the kickstart preinstall script. You could use parted
scripting, or whatever tool you use to configure your disks/RAID.
add a comment |
up vote
0
down vote
Newer versions of kickstart have a --disklabel
flag for the clearpart
option that can be set to gpt
. It appears this was added in Fedora21/RHEL7 so I am not sure if it is available in OL6.
There is an older flag to clearpart
, --initlabel
, that mentions it "initializes the disk label to the default for your architecture" and would use gpt
for Itanium architecture.
If no usable options exist in your version of kickstart, you can configure the disks in the kickstart preinstall script. You could use parted
scripting, or whatever tool you use to configure your disks/RAID.
add a comment |
up vote
0
down vote
up vote
0
down vote
Newer versions of kickstart have a --disklabel
flag for the clearpart
option that can be set to gpt
. It appears this was added in Fedora21/RHEL7 so I am not sure if it is available in OL6.
There is an older flag to clearpart
, --initlabel
, that mentions it "initializes the disk label to the default for your architecture" and would use gpt
for Itanium architecture.
If no usable options exist in your version of kickstart, you can configure the disks in the kickstart preinstall script. You could use parted
scripting, or whatever tool you use to configure your disks/RAID.
Newer versions of kickstart have a --disklabel
flag for the clearpart
option that can be set to gpt
. It appears this was added in Fedora21/RHEL7 so I am not sure if it is available in OL6.
There is an older flag to clearpart
, --initlabel
, that mentions it "initializes the disk label to the default for your architecture" and would use gpt
for Itanium architecture.
If no usable options exist in your version of kickstart, you can configure the disks in the kickstart preinstall script. You could use parted
scripting, or whatever tool you use to configure your disks/RAID.
answered Dec 5 at 19:05
GracefulRestart
1,08427
1,08427
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486190%2fhow-to-force-gpt-partitions-in-kickstart-for-oracle-linux-6%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown