On Sun, 21 Aug 2016 at 12:51 Gordon Messmer <gordon.messmer at gmail.com> 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 the original partitions before the new layout will > work ? > > > Yes. If you have pre-existing RAID partitions, they'll automatically > assemble before Anaconda runs, and the installer won't be able to remove > them. It's easiest to handle this interactively, using wipefs to clear > the filesystems, RAID metadata, and disks. Because my systems are > fairly predictable, I have a function in my kickstart file that I run > from the %pre script when I specify a keyword in the boot parameters. > You'll want to do something similar... > > Stop logical volumes if present. Wipe filesystems with wipefs, and then > stop the RAID volumes. Finally, wipe the disk partition table. > > wipedisks() { > vgchange -a n > test -b /dev/md/efi && wipefs -a /dev/md/efi && mdadm --stop > /dev/md/efi > test -b /dev/md/boot && wipefs -a /dev/md/boot && mdadm --stop > /dev/md/boot > test -b /dev/md/primary && wipefs -a /dev/md/primary && mdadm > --stop /dev/md/primary > for x in /dev/md/* > do > mdadm --stop $x > done > for x in ${drives[@]} > do > for p in /dev/${x}[0-9]* > do > wipefs -a $p > done > wipefs -a $x > done > } >Hi Gordon Thanks for your help. unfortunately it is still complaining. Currently, I try to install and it fails, I remove all the partitions from ALT-F3 console using wipefs, check with parted -l that the partitions and labels are wiped and then reboot. It fails again with:- ERR ananconda: Bootloader setup failed: failed to find a suitable stage1 device INFO anaconda: fs space: 0 B needed: 2861.02 MiB If I reboot, select legacy BIOS it works The only differences in the Kickstart files are as follows: legacy KS bootloader --location=mbr --boot-drive=sda --driveorder=sda,sdb --append="console=tty0 console=ttyS1,9600 console=ttyS2,115200" clearpart --all --initlabel --- UEFi Ks below: bootloader --location=partition --boot-drive=sda --driveorder=sda,sdb --append="console=tty0 console=ttyS1,9600 console=ttyS2,115200" clearpart --all --initlabel --drives=sda,sdb 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 ? Thanks
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.
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