search for: driveord

...o proliant with an array controller handy to check it). in order to just have one kickstart script to maintain I am trying to use the %pre section but getting a bit stuck. This is what I have: %pre if [ -b /dev/sda ] then zerombr clearpart --all bootloader --location=mbr --timeout=0 --driveorder=sda --append="crashkernel=auto rhgb quiet" part /boot --fstype=ext4 --size=500 part pv.008002 --grow --size=1 volgroup vg_host --pesize=4096 pv.008002 logvol / --fstype=ext4 --name=lv_root --vgname=vg_host --grow --size=1024 --maxsize=51200 logvol swap --name=lv_swap...

I am trying to add an efi partition to my working kickstart file. bootloader --driveorder=sda --append="rhgb quiet biosdevname=0 net.ifnames=0" clearpart --all --initlabel part / --ondisk=sda --fstype xfs --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /boot/efi --ondisk=sda --fstype efi --size=1000 --asprimary part /home --...

...specify is correctly " Even after doing a manual install to generate the file lvm configuration I'm getting the same results. I have also deleted the whole virtual machine and started from scratch. Any suggestions on how I can resolve this ? >From ks.cfg bootloader --location=mbr --driveorder=sda clearpart --linux part /boot --size=101 --fstype ext3 part swap --size=2048 --asprimary part pv.22 --size=100 --grow volgroup VolGroup00 --pesize=32768 pv.22 logvol /var/log --fstype ext3 --name=LogVol_var_log --vgname=VolGroup00 --size=2048 logvol /home --fstype ext3 --name=LogVol_home --vgn...

...ain 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 --ini...

Hi, I have a test system that booted fine using "Legacy Bios? mode and using the following Kickstart snippet configured the disks correctly:- # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part raid.01 --fstype="raid" --ondisk=sda --size=500 part raid.02 --fstype="raid" --grow

...#39;t see the relevant bits. I'm using the centOS 6.10 anaconda installer. Somehow I am ending up with my swap partition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1) My kickstart storage config looks like this: bootloader --location=mbr --driveorder=sda,sdb zerombr ignoredisk --only-use=sda,sdb clearpart --all --drives=sda,sdb part raid.boot0 --size 1000 --ondrive=sda part raid.swap0 --size 8192 --ondrive=sda part raid.root0 --size 8000 --grow --ondrive=sda part raid.boot1 --size 1000 --ondrive=sdb part raid.swap1 --size 8192 --ondrive=sdb p...

...depth 8 --startxonboot network --device eth1 --bootproto dhcp nfs --server 192.168.0.0 --dir /export/moonshine/ rootpw --iscrypted $1$71fLV/wH$V4OQNd6WZ32srMY60axN// firewall --disabled authconfig --enableshadow --enablemd5 selinux --disabled timezone --utc Europe/London bootloader --location=mbr --driveorder=hda --append="rhgb quiet" --md5pass=$1$oPmnmKSW$M2RyKA9xPM33Ml7i7o3EL. # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --all --...

...>> keyboard us >> network --device eth0 --bootproto dhcp >> rootpw --iscrypted blahblahblah >> firewall --enabled --port=22:tcp >> authconfig --enableshadow --enablemd5 >> selinux --disabled >> timezone Pacific/Auckland >> bootloader --location=mbr --driveorder=sda >> # The following is the partition information you requested >> # Note that any partitions you deleted are not expressed >> # here so unless you clear all partitions first, this is >> # not guaranteed to work >> clearpart --linux --drives=sda >> part /boot...

...iately, I noticed something strange. I insatlled it using a kickstart file, whose partitioning section is this: zerombr clearpart --all --initlabel reqpart --add-boot part pv.01 --ondisk=/dev/sda --size=1 --grow volgroup vg01 pv.01 logvol / --name=lv_root --vgname=vg01 --size=1 --grow bootloader --driveorder=sda On CentOS 7, this resulted in an XFS-formatted /boot filesystem. In CentOS 8, this created an EXT4-formatted /boot filesystem. I looked through RHEL 8's release notes and other documentation, but could not find any place that mentions this change. Does anyone know if this is deliberate,...

I successfully created an install media on a USB flash drive, but now I have a minor problem installing from it. Whenever I run the installer, it insists on installing grub on /dev/sdb (the flash drive) rather than /dev/sda (the hard drive where I'm installing everything). Is there a way to convince the installer to put grub in the right place? Should I just tell it not to install grub and

...logging --level=info ? #ignoredisk --only-use=sda ? part /boot? --onpart sda1 --noformat ? part /????? --onpart sda2 --noformat ? part swap ? --onpart sda3 --noformat ? part /usr?? --onpart sda5 --noformat ? part /var?? --onpart sda6 --noformat ? part /home? --onpart sda7 --noformat ? bootloader --driveorder=sda,sdb --location=mbr ? ... Thx, JD

...o stay in this list to ensure that time on the +# appliance is correct prior to the ovirt-server-installer being run. Otherwise you +# get Kerberos errors +services --disabled=libvirtd,postgresql --enabled=network,iptables,ntpdate,acpid,sshd +timezone --utc UTC +text + +bootloader --location=mbr --driveorder=sda --append="console=tty0" +zerombr +clearpart --all --drives=sda +part /boot --ondisk=sda --fstype=ext3 --size=100 +part / --ondisk=sda --fstype=ext3 --size=5000 +part swap --ondisk=sda --fstype=swap --size=512 +reboot + +repo --name=f10 --mirrorlist=http://mirrors.fedoraproje...

I'd like to automate the upgrade from CentOS 4.6 to 5.1 as much as possible. Since upgrades per se are not really recommended, I'm planning to do a kickstart installation. However, I want to leave one of the existing partitions (/scratch) untouched during the installation. Here is my current layout (LogVol00 is swap so not shown in the df output below): # df -hl

..._US.UTF-8 network --device eth0 --bootproto static --ip=a.b.c.e --netmask=255.255.255.0 --gateway=a.b.c.f --nameserver=a.b.c.g --hostname domu-hostname rootpw --iscrypted $1$password authconfig --enableshadow --enablemd5 selinux --disabled timezone --utc Australia/Sydney bootloader --location=mbr --driveorder=xvda --append="console=xvc0" poweroff cmdline # Partitioning zerombr clearpart --all --initlabel --drives=xvda part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup xxx --pesize=32768 pv.2 logvol / --fstype ext3 --name=root --vgname=xxx --siz...

Is there a reason why after a software raid install (from kickstart) that md1 is always unclean. md0 seems fine. boot screen says md1 is dirty and cat /proc/mdstat show md1 as being rebuilt. Any ideas? Jerry --------------- my kickstart -------------- echo "bootloader --location=mbr --driveorder=$HD1SHORT --append=\"rhgb quiet\" " > /tmp/partition-information echo "clearpart --all --initlabel " >> /tmp/partition-information echo "part -...

So I took the anaconda cfg, commented out the partition/disk pieces and ran it off my repo server and it almost worked. Little things like not including things I had done on network setup. No first boot.... :) So now I am reading up on building a kickstart cfg http://wiki.centos.org/TipsAndTricks/KickStart http://www.centos.org/docs/5/html/5.2/Installation_Guide/s1-kickstart2-howuse.html

...tproto=static --netmask=255.255.255.0 --ip=192.168.1.115 --gateway=192.168.1.1 --nameserver=192.168.1.1 --hostname=dns1 --onboot=yes rootpw blahblahblah firewall --enabled --port=22:tcp authconfig --enableshadow --enablemd5 selinux --disabled timezone --utc Europe/London bootloader --location=mbr --driveorder=xvda --append="console=xvc0" clearpart --all --initlabel --drives=xvda part /boot --fstype ext3 --size=100 --ondisk=xvda --asprimary part / --fstype ext3 --size=10240 --grow --ondisk=xvda --asprimary part swap --size=1024 --ondisk=xvda --asprimary %packages @base @core # sudo cat /e...

...y <our gateway> --noipv6 --nameserver 8.8.8.8 --hostname newserver rootpw --iscrypted <root password> # Reboot after installation reboot firewall --service=ssh authconfig --enableshadow --passalgo=sha512 selinux --enforcing timezone --utc Europe/Bratislava bootloader --location=mbr --driveorder=ddf1_Default --append="crashkernel=auto rhgb quiet" # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work #clearpart --none #volgroup VolGroup...

I am trying to install on a kvm virtual machine (host is C5). At some point it stops with install error about cyrus-sasl. I goto the /root/install.log in I have a number of errors about: Installing libstdc++ warning %post scriplet failed. exit status 127 Install zlib warning %post scriptlet failed. exit status 127 Install libxml2 warning %post scriplet failed. exit status 127 this continues for

...lang en_US.UTF-8 | keyboard us | network --device eth0 --bootproto dhcp | rootpw --iscrypted $1$iMuKLiWQA$kljIOj097NBAD8SDlkjnmk | firewall --disabled | authconfig --enableshadow --enablemd5 --enablenis --nisdomain=localdomain | selinux --disabled | timezone --utc Eire | bootloader --location=mbr --driveorder=xvda | # Clear all partitions and create a single partition for / | # Note that no swap partition is created! VMs should *never* swap. | clearpart --all --initlabel | part / --fstype ext3 --size=100 --grow Apologies for the lengthy posting :)