On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer <gordon.messmer at gmail.com> 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 things to consider: > * The documentation for "autopart" states that "The autopart command can't > be used with the logvol, part/partition, raid, reqpart, or volgroup in the > same kickstart file," so your use of autopart and "part /boot/efi" appear to > be incompatible. Maybe drop the "part" line. > * I specify partitions for kickstart, but my bootloader line is: > bootloader --location=mbr --append="net.ifnames=0 biosdevname=0" > No location is specified, the installer works it out. Given the error you > posted, I think sda1 might not be where anaconda is putting the EFI > partition.That appears to be basically correct. It'll put it on sda1 but it doesn't want you to tell it to put it on sda1 when using autopart. Pretty much autopart wants to be told very little, and Phil's kickstart is being too explicit for autopart. -- Chris Murphy
> On 28 Aug 2016, at 10:04 AM, Chris Murphy <lists at colorremedies.com> wrote: > > On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer > <gordon.messmer at gmail.com <mailto:gordon.messmer at gmail.com>> 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 things to consider: >> * The documentation for "autopart" states that "The autopart command can't >> be used with the logvol, part/partition, raid, reqpart, or volgroup in the >> same kickstart file," so your use of autopart and "part /boot/efi" appear to >> be incompatible. Maybe drop the "part" line. >> * I specify partitions for kickstart, but my bootloader line is: >> bootloader --location=mbr --append="net.ifnames=0 biosdevname=0" >> No location is specified, the installer works it out. Given the error you >> posted, I think sda1 might not be where anaconda is putting the EFI >> partition. > > That appears to be basically correct. It'll put it on sda1 but it > doesn't want you to tell it to put it on sda1 when using autopart. > Pretty much autopart wants to be told very little, and Phil's > kickstart is being too explicit for autopart. > >Thanks for all the comments to date, so I should try:- clearpart --all --initlabel --drives=sda,sdb ignoredisk --only-use=sda,sdb # System bootloader configuration bootloader --append=" crashkernel=auto" --location=mbr autopart --type=lvm There is also a nvme drive in the system too, hence the use of "ignoredisk --only-use=sda,sdb?. Phil
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 bootloader configuration
bootloader --location=mbr
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel
# Disk partitioning information
%include /tmp/efipartition-ks.tmp
part /boot --fstype="ext4" --size=250
# make the physical partition for the LVM to sit on "pv.01" is
"partition volume number 01" alternatively something like
"pv.02393"
would be fine.
# this partition should "grow" to fill the entire disk, the initial
size
is 1mb (don't use 0 here)
Sincerly
Andy
Am Sonntag, den 28.08.2016, 21:36 +1000 schrieb Phil
Manuel:> > On 28 Aug 2016, at 10:04 AM, Chris Murphy <lists at
colorremedies.com> wrote:
> >
> > On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer
> > <gordon.messmer at gmail.com <mailto:gordon.messmer at
gmail.com>> 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 things to consider:
> >> * The documentation for "autopart" states that "The
autopart command can't
> >> be used with the logvol, part/partition, raid, reqpart, or
volgroup in the
> >> same kickstart file," so your use of autopart and "part
/boot/efi" appear to
> >> be incompatible. Maybe drop the "part" line.
> >> * I specify partitions for kickstart, but my bootloader line is:
> >> bootloader --location=mbr --append="net.ifnames=0
biosdevname=0"
> >> No location is specified, the installer works it out. Given the
error you
> >> posted, I think sda1 might not be where anaconda is putting the
EFI
> >> partition.
> >
> > That appears to be basically correct. It'll put it on sda1 but it
> > doesn't want you to tell it to put it on sda1 when using autopart.
> > Pretty much autopart wants to be told very little, and Phil's
> > kickstart is being too explicit for autopart.
> >
> >
>
> Thanks for all the comments to date, so I should try:-
>
> clearpart --all --initlabel --drives=sda,sdb
> ignoredisk --only-use=sda,sdb
> # System bootloader configuration
> bootloader --append=" crashkernel=auto" --location=mbr
> autopart --type=lvm
>
> There is also a nvme drive in the system too, hence the use of
"ignoredisk --only-use=sda,sdb?.
>
> Phil
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos