similar to: CentOS 7.2 Installation - Anaconda Installer Security Policy Configuration

Hi all, We are hitting an error in the centos 7 installation with our kickstart configuration. =============================================================================== An unknown error has occurred =============================================================================== anaconda 21.48.22.56-1 exception report Traceback (most recent call first): File

Kickstart fails for statically built custom booting kernel, although the custom kernel is built form the same version stock kernel source. My anaconda and kernel source are both of stock versions on Centos 5. At the kickstart 'F3' screen, the following error messages appear: Modules to insert tg3 ... ... ERROR: no network devices in choose network device! ERROR: no network drivers

I have a bunch of HP BL465c G5 blades, with additional dual-port network adapters. The onboard interfaces use the bnx2 driver, while the expansion card uses tg3. All 4 interfaces are detected by both Anaconda and the installed system, but Anaconda is reversing the ordering: Anaconda: eth0 Card 2, Port 1 eth1 Card 2, Port 2 eth2 Card 1, Port 1 eth3 Card 1, Port 2 BIOS and Installed Kernel:

I'm having what appears at first glance to be a kickstart+anaconda issue on CentOS 7.4. As near as I can tell in the program.log in the anaconda environment, the partitioning instructions downloaded with the kickstart from cobbler appear to simply not be applied. Then /mnt/sysimage is not mounted, the logs are not copied to /mnt/sysimage/root and the installation stalls due to the anamon

I am building a latest CentOS5 and every newest stuff is ready. All are in directory "/linux/CentOS/5-respin/os/x86_64". My OS is CentOS5 too. I want to add some other pictures during installation process, so anaconda adjustment is needed. When I run command "anaconda --test --method=http://192.168.0.3/linux/CentOS/5-respin/os/x86_64", a error message followed: Traceback (most

Hello, Our environment: CentOS 5.2 (updated over time with "yum update", current "yum update" lists about 7 packages out of date), x86_64. Running Xen, building Xen DomU's with kickstart. We are trying to debug the %post part of the kickstart process for DomU and are hitting difficulties in accessing the output. For a start, the "cmdline" directive in the

I have started playing around with remote installs using vnc and kickstart files. However I cannot seem to find a good listing of anaconda parameters. And where I am running into problems is with the display. Say that I am using a kickstart file and I don't want it to establish a vnc connection or to show progress on the console what can I provide to anaconda to do this? When I add text to

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)

I did a quick search through the archive and couldn't find anything that mapped to my need, so I figured I should ping the community and see if anyone has the requisite knowledge and could point me in the right direction. *Succinct Version* Is there a way to, using updates.img, monkey patching or swapping in a newer Anaconda (>= 16) to force all disks to have gpt labels and not just

Dear all, I have been struggling with my first PXEboot today, using a kickstart with packages served over http on the local network. The details: - Anaconda is using 100% CPU - CentOS 5.5 i386 downloaded yesterday - .iso md5sums checked out good - 0 network errors showing (ifconfig) - console 1 displays: "Installing httpd-..." Done [508/782]" - It appears to be trying to

Has anybody encountered this problem? I have a box that has FC2 installed. I wanted to trash the FC2 installation and install CentOS 4. I have a pxeboot/dhcp/kickstart environment and so I tried automatic disk partitioning (clear all partitions and then create new ones), manual disk partitioning but everything else is automated and finally, zero automation, just a manual installation through

I am asking this here, that although a kickstart question, may have something to do with the Centos install? I took my Anaconda-ks.cfg from my system, turned it into a ks.cfg and did the install. Everything SEEMS ok, but why? First the partitioning information: ks.cfg supplied: clearpart --all --drives=hda part /boot --fstype ext3 --size=100 --ondisk=hda part / --fstype ext3 --start=14

This problem occurred in both CentOS 5.2 and the new (awesome!) 5.3: I'm using a SuperMicro motherboard with a 6 port NVidia SATA controller on the motherboard and an 8 port SuperMicro Marvel controller in a slot. In my kickstart file, I have part raid.01 . --ondisk=sda . part raid.02 . --ondisk=sdb . part raid.03 . --ondisk=sdc . part raid.04 . --ondisk=sdd . . raid /

Hi, I'm trying to install Centos 5.2 on an "old" machine in graphical mode (to use LVM) but anaconda crash. I made several tries with various installation resquest (the last is "Server", "Customize after installation") unfortunately, it's reproductible: Traceback (most recent call first): File

I run Dell M7710 with 32GB, SSDs, and nVidia graphics. It wasn't cheap, but it's blisteringly fast. -- Michael Duvall <michael.duvall at ccur.com> Concurrent Computer Corporation

Hi all, I've created an anaconda update.img file per instructions at https://fedoraproject.org/wiki/Anaconda/Updates for Centos 7.2. The problem is that the update.img file contains references to python3 (say, file /usr/sbin/anaconda), and so the all installation fails immediately. My question is: what are the steps to create an anaconda update image appropriate for a particular centos

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

A Regards, Michael Duvall Systems Analyst Concurrent Computer Corporation 2881 Gateway Drive Pompano Beach, FL 33069 c: 954-531-4538 o: 954-973-5395

I have a kickstart file with the following partitioning directives: part /boot --fstype ext3 --onpart=sda1 part pv.100000 --onpart=sda2 --noformat volgroup vol0 pv.100000 --noformat logvol / --vgname=vol0 --name=lvol1 --useexisting --fstype=ext4 logvol /tmp --vgname=vol0 --name=lvol2 --useexisting --fstype=ext4 logvol swap --vgname=vol0 --name=lvol3 --useexisting logvol /data --vgname=vol0

Hi Does anyone know if its possible to set a search domain within anaconda to use during kickstart? I'd rather not have to set a FQDN for a certain service as its location specific that is dependent on SSL and therefore the certs. I cant see anything in the docs listed but i thought i'd ask cheers