> 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