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 DEBUG anaconda: _is_valid_size(sda1) returning True 06:08:54,867 DEBUG anaconda: _is_valid_location(sda1) returning True 06:08:54,867 DEBUG anaconda: _is_valid_format(sda1) returning False 06:08:54,867 DEBUG anaconda: is_valid_stage1_device(sda1) returning False 06:08:54,867 ERR anaconda: BootLoader setup failed: failed to find a suitable stage1 device 06:08:54,979 INFO anaconda: fs space: 0 B needed: 2861.02 MiB The relevant kickstart section is:- clearpart --all --initlabel --drives=sda,sdb ignoredisk --only-use=sda,sdb # System bootloader configuration part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 autopart --type=lvm So it's failing on the bootloader section. I've tried with the following line too:- bootloader --append=" crashkernel=auto" --location=partition --boot-drive=sda1 Still fails. Thanks On Wed, 24 Aug 2016 at 02:07 Gordon Messmer <gordon.messmer at gmail.com> wrote:> 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 list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >
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=lvmA 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.
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 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. >Just one more thing - I'm sure this was the case with 6, not sure about 7, but I think so - I think the command was autopart that couldn't deal with GPT, if you're using that. And I don't know that it will understand or set the /boot/efi/EFI to partition type BIOSDIR (or whatever the right type is), but it's *not* a normal type. mark
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