similar to: kickstart

Hello. A couple of years ago I installed two file-servers using kickstart. The server has two 1TB sata disks with two software raid1 partitions as follows: # cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdb4[1] sda4[0] 933448704 blocks [2/2] [UU] md0 : active raid1 sdb1[1] sda2[2](F) 40957568 blocks [2/1] [_U] Now the drives are starting to be failing and next week

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\" " >

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

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 hda

Hello Group, I am building a company application based on Centos 5.7 OS. The application was working earlier and creating right partitions both for hardware as well as VM. But since we introduced Centos 5.7 OS and start building application with 5.7 anaconda the hardware partitions are duplicate of VM partitions *while creating hardware partition my code looks like.* cat >

Greetings. There must be some minor changes to anaconda. I'm getting the error: "Cannot open repomd.xml file...." the file seems to be located in the repodata directory... I'm using the following .cf taken directly from the CentOS 4.4 install : install url --url ftp://centos.westmancom.com/5.0/os/i386/ #cdrom lang en_US.UTF-8 langsupport --default=en_US.UTF-8 en_US.UTF-8

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

On Thu, August 4, 2016 7:13 pm, Paul Heinlein wrote: > On Thu, 4 Aug 2016, Valeri Galtsev wrote: > >> Dear Experts, >> >> Could somebody point to kicstart HOWTO specific for CentOS 7? >> >> On CentOS 7 I somehow am always given human intervention questions >> about drive which defeats unattended ks install. >> >> At least one snag I hit

I fought with this for a day, and now am crying for help.... The goal is 5 partitions: boot, notebook suspend, / , /home. and swap. So I have to use LVM. Here are my commands: #System bootloader configuration bootloader --location=mbr #Clear the Master Boot Record zerombr yes #Partition clearing information clearpart --all --initlabel --drives=hda #Disk partitioning information part pv.1

I am testing some kickstarts on ESXi virtual machine with pair of 16GB disks. Partitioning is lvm over raid. If i am using "logvol --grow i get "ValueError: not enough free 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

Hi All, This has to be something simple....but it's really busting my chops. We have a PXE boot server that is used for initial installation of a number of operating systems and it works well. However the CentOS 5.1 x86_64 install is seriously broken. We've made the PXE boot images available from "centos/5/os/x86_64/images/pxeboot/" in the tftp boot etc. We've rsynced

I've set up a local webserver to store kickstart files for domUs. All parameters are respected apart from the network settings. DomU always gets DHCP. Can any one help to unwrap this one? Does one add hostname, ip, netmask and gateway values to the /etc/xen/blah.cfg file? # ---- domU kickstart file ----# url --url http://192.168.1.120/centos/5/os/i386 lang en_US.UTF-8 keyboard uk network

When I use my kickstart file (which works on 5.1 x86_64) with 5.2 I get the following error. I put my kickstart file at the end. Do I have something incomaptible in the file? jerry -------------------------------------- Traceback (most recent call first): File "/usr/lib/anaconda/network.py", line 341, in lookupHostname ret = isys.pumpNetDevice(dev.get('device'),

centos-virt, I'm trying to create/install domU guests all in "one" step, following Daniel's wiki page (I've found these pages really helpful, BTW): http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU I have a few questions about this process: (1) How would it be modified (w/respect to defining the disk in the domain configuration file) to use a disk layout where dom0

Hey, Can anyone tell me why option 1 works and option 2 fails ? I know I need swap and such, however in trouble shooting this issue I trimmed down my config. It fails on trying to format my logical volume, because the mount point does not exist (/dev/volgroup/logvol) It seems that with option 2, the partitions are created and LVM is setup correctly. However the volgroup / logvolume was not

Dear All, I'm trying to install Centos 4.2 x86_64 on a new Opteron server, using a software raid 1 boot partition. Here is the appropriate section of my kickstart.cfg #System bootloader configuration bootloader --location=mbr #Clear the Master Boot Record zerombr yes #Partition clearing information clearpart --all --initlabel #Disk partitioning information part raid.01 --size 50000

Hi there, after using Foreman successful on our clusters for more than a year. I'd like to reinstall a 90 node cluster with Centos 7.4. It's now running on Centos 7.3 . I'm not able to just update to 7.4 because of zfsonlinux dependencies and well - some nodes died and had to bare metal install them. So I was able to install these nodes successfully by pxe-booting and using a

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"

I'm testing doing kickstart installations on Xen VMs. This is the first time I'm trying out kickstart at all, so I rather think I'm doing something wrong in the kickstart configuration than it is a Xen issue. I use a modified kickstart file from an earlier manual installation with a very basic filesystem setup. It fails with "SystemError: vgcreate failed for VolGroup00".

HI all, I just did a fresh C7 install using kickstart. fdisk -l /dev/sda shows: # Start End Size Type Name 1 2048 2050047 1000M EFI System EFI System Partition 2 2050048 104450047 48.8G Microsoft basic 3 104450048 112642047 3.9G Linux swap 4 112642048 234440703 58.1G Microsoft basic What extra do I need to