similar to: has anyone a working example for a ks.cfg with two disks?

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

On Monday, 28 November 2016 10:40:51 CET Richard W.M. Jones wrote: > Create a new directory (builder/template). Integrate all of the > scripts into a single program, so that templates are generated more > consistently. > > This also changes how the index file is generated. The script now > generates the index file fragment and saves it under version control, > and then

I'm using the kickstart file we developed for v5 on 6.2 in VM (kvm/qemu running on a CentOS 5.6), but it fails: Error partitioning. Could not allocate requested partitions: not enough free space on disks. There's nothing wrong with the disk. Both fdisk and parted works fine, I can view, partition and write a partition table and the disk is 10.5GB. However, looking through

Hi, I am struggling with kickstart. What I want to achieve is a reinstall, but some data partitions should survive the install, i.e. they should not be formatted. With a single disk this works, here is the relevant part from the kickstart file (I shortened the name of the volume group) ... zerombr clearpart --none --initlabel part /boot --fstype="xfs" --label=boot --onpart=vda1 part

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone have any thoughts on why anaconda might be prompting me to reinitialize the disk during the kickstart of a Centos6.4 install on hyperV when a) the kickstart file contains "zerombr" as referred to in the installation guide[1] b) installation proceeds with no prompt on KVM hypervisors and succeeds? I have read the release notes[2]/tech

Hallo, this version is working here now. Ralf bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda # Partition clearing information clearpart --all --initlabel --drives=sda,sdb # Disk partitioning information part / --fstype="ext4" --ondisk=sda --grow --size=1 part swap --fstype="swap" --ondisk=sda --size=8192 part /mnt/platte02

The immediate issue is with Fedora/ppc64 and /ppc64le which currently use extended partitions, breaking the virt-builder ‘--size’ parameter, eg: $ virt-builder --arch ppc64le fedora-26 --size 20G ... [ 21.6] Resizing (using virt-resize) to expand the disk to 20.0G virt-resize: error: /dev/sda5: partition not found in the source disk image (this error came from '--expand' option

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

Hi, I'm trying to install the centos netboot install on ppc64le platform but automation installation(kickstart) fails with the following error: Starting installer, one moment... find_file: stat /proc/device-tree/chosen/bootpath, No such file or directory anaconda 21.48.22.56-1 for CentOS AltArch 7 started. * installation log files are stored in /tmp during the installation

Hello, I?m using virt-install to build a guest system with CentOS. The system boots up, times out with dracut-initqueue timeout and drops me into an emergency shell. If I exit the shell the install continues and I get a working machine. Any ideas? virt-install \ -n TEST \ -r 8192 \ --os-type=linux \ --disk=/vm-images/test.img,device=disk,bus=virtio,size=100,format=raw \

I made a file partition-ks.cfg and put it in our machine 192.168.5.17 under /var/www/html. When I install a new machine I just do a linux ks=http://192.168.5.17/partition-ks.cfg I have a couple questions though: 1) I have the following in it: clearpart --all part /boot --fstype ext3 --size=100 part /var --fstype ext3 --size=10000 part / --fstype ext3 --size=10000

Create a new directory (builder/template). Integrate all of the scripts into a single program, so that templates are generated more consistently. This also changes how the index file is generated. The script now generates the index file fragment and saves it under version control, and then generates the final index file by concatenating these. (Previously the index was written by hand which was

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

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

I've previously used includes in CentOS 4.4 and they worked fine. But in CentOS 5.5, trying to specify a driver disk via an include does not work. If I instead specify it directly, it loads fine. When it fails (because it can't see the disk drive - needs the driver disk to see the hard disk), in Console 2 I can see that /tmp/drvdisk exists and has the line I wrote to it. I see nothing

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

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

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 consistently with CentOS 7 kickstart is: it > drops me into human decision as far as wiping hard