On Tue, 23 Aug 2016 at 02:18 Gordon Messmer <gordon.messmer at gmail.com> 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 remember struggling with this as well, but I can't find > my notes from that work at the moment. > > My kickstart files for non-RAID UEFI boots use something like this: > > bootloader --location=mbr --append="net.ifnames=0 biosdevname=0" > part /boot/efi --ondrive=sda --fstype=efi --label EFI > part /boot --fstype=ext4 --ondrive=sda > ... > > > My memory is really fuzzy, but if I remember right, this didn't work > when I didn't specify "--label EFI" or some other really silly thing. I > think I resolved the problem by doing a manual install and then working > with the anaconda.ks file until I was satisfied. >OK So I tried your suggestion no joy. Installed i manually. Took the kickstart file from this install, and tried to use this as the install kickstart. It failed. I deleted all the partitions and tried again no joy, the default ks is as follows:- #version=DEVEL # Use network installation url --url="http://192.168.0.156/CentOS7-x86_64/disc1/" # Use text mode install text ignoredisk --only-use=sda,sdb # Keyboard layouts keyboard --vckeymap=us --xlayouts='us' # System language lang en_US.UTF-8 # Network information network --bootproto=dhcp --device=enp0s31f6 --ipv6=auto --activate network --hostname=localhost.localdomain # Root password rootpw --iscrypted # Do not configure the X Window System skipx # System timezone timezone Australia/Sydney # System bootloader configuration bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda autopart --type=lvm # Partition clearing information clearpart --all --initlabel --drives=sda,sdb %packages @core kexec-tools %end %addon com_redhat_kdump --enable --reserve-mb='auto' %end Should I need to change anything to this ? Thanks
On Tue, 23 Aug 2016, Phil Manuel wrote:> On Tue, 23 Aug 2016 at 02:18 Gordon Messmer <gordon.messmer at gmail.com> > 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 ?... lots of troubleshooting deleted ... If all else fails, you can pull out the sledgehammer: dd. Add a %pre section to your kickstart. %pre --interpreter=/usr/bin/bash # nuke all MBR and partition info. season list of # block devices to taste. for BLKDEV in sda sdb; do dd if=/dev/zero of=/dev/$BLKDEV bs=512 count=4 done %end This will execute prior to anaconda trying to partition the disk. Note that it will erase or obfuscate all data on the disk(s) so it's definitely unsuited for systems on which you want to retain data. -- Paul Heinlein heinlein at madboa.com 45?38' N, 122?6' W
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.
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 >