similar to: FYI, minor change in anaconda behaviour between 6.2 and 6.3

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

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

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

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

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

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

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

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

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

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

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'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

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

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'),

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

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

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

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn'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)

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

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 >