search for: asprimary

I have 2 questions dealing with 2 different kickstart files. 1) my kickstart sections for RAID disk setup and kickstart reports it cannot find sda. Why is that. sda is there and works. clearpart --all --initlabel part raid.01 --asprimary --bytes-per-inode=4096 --fstype="raid" --onpart=sda1 --size=20000 part swap --asprimary --bytes-per-inode=4096 --fstype="swap" --onpart=sda2 --size=4000 part raid.02 --bytes-per-inode=4096 --fstype="raid" --grow --onpart=sda3 --size=1 part raid.03 --asprimary --byte...

...s made up of sdb1 and sda2. Could anybody help me understand how to make the partitions on the two drives identical still using kickstart? Here's the relevant part from the kickstart file: zerombr yes clearpart --all --initlabel bootloader --location=mbr part /boot --fstype ext3 --size 250 --asprimary --ondisk sda part swap --size 2048 --asprimary --ondisk sda part raid.01 --size 40000 --asprimary --ondisk sda part raid.03 --size 1 --grow --asprimary --ondisk sda part /boot2 --fstype ext3 --size 250 --asprimary --ondisk sdb part swap --size 2048 --asprimary --ondisk sdb part raid.02 --size 40000...

I have a couple lines like: part / --ondisk=sda --fstype ext3 --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /home --ondisk=sda --fstype ext3 --size=1 --asprimary --grow in my kickstart file. Is there a way to have 1 kickstart file that works for hda and sda both??? So I would like to have 1 kickstart file that works for either a h...

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 --ondisk=sda --fstype xfs --size=1 --asprimary --grow the line with /boot/efi is the only new item other then "removing" --location=mbr fro...

As I understand anaconda uses parted to partition (starting from centos 6), using this as example (kickstart configuration file): clearpart --all --drives=sda --initlabel part /boot --asprimary --size=200 --fstype=ext2 --ondisk=sda part swap --asprimary --size=16384 --fstype=swap --ondisk=sda part / --asprimary --size=512000 --fstype=ext4 --ondisk=sda part /scratch --asprimary --size=1 --grow --fstype=ext4 --ondisk=sda I can see no problems in parted: GNU Parted 2.1 Using /dev/sda Welco...

I was just wondering how (or indeed if) people use the %include directive in Kickstart configuration files when building systems via NFS. I've been trying to modularise our Kickstart files a little to make things more readable, having generic defaults and role specific stuff split out into separate configs. I've tried this configuration... [root at archive kickstart]# cat

...-location=mbr --append=\"%s\"\n" > + (kernel_cmdline_of_os os arch); > + bpf "\n"; > + > + (match os with > + | CentOS _ -> > + bpf "\ > +zerombr > +clearpart --all --initlabel > +part /boot --fstype=ext4 --size=512 --asprimary > +part swap --size=1024 --asprimary > +part / --fstype=ext4 --size=1024 --grow --asprimary > +"; > + | RHEL ((3|4), _) -> > + bpf "\ > +zerombr > +clearpart --all --initlabel > +part /boot --fstype=ext2 --size=512 --aspr...

...g `lvm lvchange -a -y pathname` from with in the shell after anaconda failed made the volgroup / logvol active. Which would allow the format command to complete. Option 1: zerombr yes clearpart --all --initlabel part /boot --fstype ext3 --size=100 part pv.os --size=10000 --grow --maxsize=10000 --asprimary volgroup os_volgroup01 pv.os logvol swap --fstype swap --name=os_swap_logvol --vgname=os_volgroup01 --recommended logvol / --fstype ext3 --name=os_root --vgname=os_volgroup01 --size=1024 --grow Option 2: zerombr yes clearpart --all --initlabel part /boot --fstype ext3 --size=100 part pv.os --siz...

...;rhgb quiet\" " > /tmp/partition-information echo "clearpart --all --initlabel " >> /tmp/partition-information echo "part --ondisk=$HD1SHORT raid.01 --asprimary --bytes-per-inode=4096 --fstype="raid" --size=20000 " >> /tmp/partition-information echo "part --ondisk=$HD1SHORT swap --asprimary --bytes-per-inode=4096 --fstype="swap" --size=4000 " >> /tmp/partition-information echo "p...

...space in volume group" Only workaround i can find is to add --maxsize=XXX where XXX is at least 640MB less than available. (10 extents or 320Mb per created logical volume) Following snippet is failing with "DEBUG blivet: failed to set size: 640MB short" part raid.01 --size 512 --asprimary --ondrive=sda part raid.02 --size 1 --asprimary --ondrive=sda --grow part raid.11 --size 512 --asprimary --ondrive=sdb part raid.12 --size 1 --asprimary --ondrive=sdb --grow raid /boot --fstype="xfs" --device="md0" --level=RAID1 raid.01 raid.11 raid pv.01 --fstype...

Hello, I'm trying to do a kickstart install of centos5. I'm pulling it off a network server and i'm getting an error, in the parsing of the file. It refers to line 31, i'm not going to show the complete file, but here is the indicated line: raid swap --fstype swap --level=RAID1 raid.4 raid.7 and the raid lines: part raid.7 --size=512 --ondisk=hdb part raid.4 --size=512

...tcp --port=21:tcp --port=25:tcp --port=443:tcp selinux --disabled authconfig --enableshadow --enablemd5 timezone America/Vancouver zerombr yes bootloader --location=mbr clearpart --all --initlabel part /boot --fstype ext3 --size=1000 --ondisk=sda part /var --fstype ext3 --size=12000 --ondisk=sda --asprimary part /usr --fstype ext3 --size=3000 --ondisk=sdb part / --fstype ext3 --size=3000 --ondisk=sda part /tmp --fstype ext3 --size=5000 --ondisk=sdb part /downloads --fstype ext3 --size=10000 --ondisk=sdb part /d1 --fstype ext3 --size=45000 --ondisk=sdb --grow --asprimary part /backup --fstype ext3 --si...

I am trying to install Centos 7 on a couple 4TB drives with software raid. In the Supermicro bios I set UEFI/BIOS boot mode to legacy. I am using the Centos 7 minimal install ISO flashed to a USB thumb drive. So I do custom drive layout something like this using sda and sdb. Create /boot as 512 MB XFS raid1 array. Create SWAP as 32 GB SWAP raid1 array. Create / on 3.xxx TB XFS raid1 array.

...d5pass=$1$F/BHluSk$YticIZvEKa6Ckmw6GYTno. bootloader --location=mbr --boot-drive=sda --append="crashkernel=no rhgb quiet" # Partition clearing information clearpart --all --initlabel --drives=sda # Disk partitioning information part /boot --fstype="xfs" --ondisk=sda --size=500 --asprimary part / --fstype="xfs" --ondisk=sda --size=5000 --asprimary part /usr --fstype="xfs" --ondisk=sda --size=30000 --asprimary part swap --fstype="swap" --ondisk=sda --size=4000 part /var --fstype="xfs" --ondisk=sda --size=3000 part /tmp --fstype="xfs" -...

Hi All, I have a new system with 2 Seagate 1TB SATA Enterprise level drives in it. I want to RAID1 (mirror) these drives. This machine will be a web-server in my apartment hosting an HTML video fan site I am creating. Apache, MySQL, PHP etc. This site will easily be 300+ gigs with all the versions of each video, the MySQL won't be huge, but will grow as data for each video is added (i.e

Has anyone gotten this to work ? I can define a raid device but cant put a VG on it. I then tried 'autopartition' and it created an 'LVM' of sorts, when I tried to edit it I wasnt able to as a message appeared saying, LVM editing was not allowed in text mode. Any help ? Cheers, Brian. PS - PIII-500mhz 128mb RAM, 4mb AGP.

If you use a kickstart file to build unattended servers (eg virt-install) then new disks or virtual volumes will cause problems unless you have "zerombr true" in the kickstart file eg zerombr yes clearpart --all --initlabel part /boot --fstype=ext4 --asprimary --size=100 part swap --asprimary --size=512 part / --fstype=ext4 --asprimary --grow --size=1 (CentOS 6.2 didn't need zerombr). Also FWIW, lines such as repo --name="CentOS" --baseurl=http://repo/CentOS/DVD/CentOS-6 repo --name="Updates" --baseurl=http://repo/CentO...

...lahblah 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 /etc/xen/dns1.cfg ramdisk = "/home/jayeola/virt/images/centos_domU/initrd.img" kernel = "/home/jayeola/virt/images/centos_domU/vmlin...

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

...f "\n"; + + bpf "bootloader --location=mbr --append=\"%s\"\n" + (kernel_cmdline_of_os os arch); + bpf "\n"; + + (match os with + | CentOS _ -> + bpf "\ +zerombr +clearpart --all --initlabel +part /boot --fstype=ext4 --size=512 --asprimary +part swap --size=1024 --asprimary +part / --fstype=ext4 --size=1024 --grow --asprimary +"; + | RHEL ((3|4), _) -> + bpf "\ +zerombr +clearpart --all --initlabel +part /boot --fstype=ext2 --size=512 --asprimary +part swap --size=1...