Here is how i dig it up.
# efi partionen ???
%pre --interpreter /bin/sh
if [ -d "/sys/firmware/efi" ]; then
echo "part /boot/efi --fstype=efi --grow --maxsize=200
--size=200" >/tmp/efipartition-ks.tmp
else
echo "# no efi system" >/tmp/efipartition-ks.tmp
fi
%end
# System
> On 28 Aug 2016, at 10:04 AM, Chris Murphy wrote:
>
> On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer
> > wrote:
>> On 08/25/2016 11:35 PM, Phil Manuel wrote:
>>>
>>> The relevant kickstart section is:-
>>>
On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer
wrote:
> On 08/25/2016 11:35 PM, Phil Manuel wrote:
>>
>> The relevant kickstart section is:-
>>
>> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda
>> bootloader --append=" crashkernel=auto"
IF you've sorted this out, skip this email, it might be confusing.
Your best bet might be to do this in a VM using custom partitioning
then look at the resulting /root/anaconda-ks.cfg for hints. I find the
nomenclature of anaconda kickstarts to be very confusing and
non-obvious. And I'm willing
Gordon Messmer wrote:
> On 08/25/2016 11:35 PM, Phil Manuel wrote:
>> The relevant kickstart section is:-
>>
>> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda
>> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1
>> autopart --type=lvm
>
> A couple of
On 08/25/2016 11:35 PM, Phil Manuel wrote:
The relevant kickstart section is:-
part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda
bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1
autopart --type=lvm
A couple of things to consider:
* The
Hi all,
This the latest output from anaconda.log:-
06:08:54,828 DEBUG anaconda: new disk order: []
06:08:54,832 DEBUG anaconda: new disk order: []
06:08:54,851 DEBUG anaconda: stage1 device cannot be of type disk
06:08:54,865 DEBUG anaconda: _is_valid_disklabel(sda1) returning True
06:08:54,867
On 08/22/2016 11:31 PM, Phil Manuel wrote:
Should I need to change anything to this ?
As far as I know, you shouldn't. If installation still fails, you'll
probably need to post the logs somewhere to get more useful assistance.
___
CentOS mailing
On Tue, 23 Aug 2016, Phil Manuel wrote:
On Tue, 23 Aug 2016 at 02:18 Gordon Messmer
wrote:
On 08/21/2016 11:56 PM, Phil Manuel wrote:
part /boot/efi --fstype="efi" --size=200 --ondisk=sda
And I have tried the latter with location as mbr still fails
What am I
On Tue, 23 Aug 2016 at 02:18 Gordon Messmer
wrote:
> On 08/21/2016 11:56 PM, Phil Manuel wrote:
> > part /boot/efi --fstype="efi" --size=200 --ondisk=sda
> > And I have tried the latter with location as mbr still fails
> > What am I missing ?
>
>
> I very vaguely
On 08/21/2016 11:56 PM, Phil Manuel wrote:
part /boot/efi --fstype="efi" --size=200 --ondisk=sda
And I have tried the latter with location as mbr still fails
What am I missing ?
I very vaguely remember struggling with this as well, but I can't find
my notes from that work at the moment.
My
On Sun, 21 Aug 2016 at 12:51 Gordon Messmer
wrote:
> On 08/19/2016 11:35 PM, Phil Manuel wrote:
> > The install fails under UEFi due to the fact the partitions are not
> cleared, and it doesn’t have any space to continue. Is there an extra step
> I need to do to remove
On 08/19/2016 11:35 PM, Phil Manuel wrote:
The install fails under UEFi due to the fact the partitions are not cleared,
and it doesn’t have any space to continue. Is there an extra step I need to do
to remove the original partitions before the new layout will work ?
Yes. If you have
Hi,
I have a test system that booted fine using "Legacy Bios” mode and using the
following Kickstart snippet configured the disks correctly:-
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel
# Disk partitioning information
part raid.01
14 matches
Mail list logo