similar to: Anaconda Partial Freeze...

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

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

On 18/04/2017 15:54, Frank Thommen wrote: > Hi, > > I am currently struggling with the right way to configure a bonding > device via kickstart (via PXE). > > I am installing servers which have "eno" network interfaces. Instead of > the expected bonding device with two active slaves (bonding mode is > balance-alb), I get a bonding device with only one active slave

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

Good afternoon Support Team, I have discovered a disturbing error inside?anaconda-ks.cfg under the /root directory. Examination found the config file devoid of the string "buns". It's distressing, because I don't understand how my Anaconda can get anything done if it doesn't happen to have any buns. Please advise I need to know how to continue. Please feel free to contact me

I've recently been dealing with various CentOS images on AWS, and am being forcibly reminded that the "/root/anaconda-ks.cfg" has only a passing resemblance to whatever the kickstart configuration file actually contained. But getting a copy of the actual "ks.cfg" is invaluable for updating and testing variations of the kickstart setup, especially when manipulating disk

I think that should be: %post --nochroot -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Nico Kadel-Garcia" <nkadel at gmail.com> > To: "Discussion about the virtualization on CentOS" <centos-virt at centos.org> > Sent: Saturday, 25 April, 2015 15:38:49 > Subject: [CentOS-virt] Can we get a

Anthony Ray wrote: > Good afternoon Support Team, > I have discovered a disturbing error inside?anaconda-ks.cfg under the > /root directory. Examination found the config file devoid of the string > "buns". It's distressing, because I don't understand how my Anaconda can > get anything done if it doesn't happen to have any buns. > Please advise I need to know

--- sysprep/sysprep_operation_logfiles.ml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sysprep/sysprep_operation_logfiles.ml b/sysprep/sysprep_operation_logfiles.ml index 8994af9..3055ca4 100644 --- a/sysprep/sysprep_operation_logfiles.ml +++ b/sysprep/sysprep_operation_logfiles.ml @@ -41,6 +41,7 @@ let globs = List.sort compare [ "/var/log/apache2/*_log";

Hi, I am currently struggling with the right way to configure a bonding device via kickstart (via PXE). I am installing servers which have "eno" network interfaces. Instead of the expected bonding device with two active slaves (bonding mode is balance-alb), I get a bonding device with only one active slave and an independent, non-bonded network device. Also the bonding device

Hello, In EL6 I could well remove /root/anaconda-ks.cfg in %post, but not any more it seems and I like my installs clean. Anyone has any idea how to skip creating this file or deleting during install? I don't want to resort to running scripts upon first boot. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro

I have a kickstart file that I am using to install multiple machines. If I install with no %post script, everything runs great. When I add the following %post section, if fails. I have been working on this for a few days now without luck, Any help would be appreciated. Here is the error, the script follows. Traceback (most recent call first): File

Thanks for that Jason but it didn't solve the problem. The system is still coming up with the interfaces shuffled. It seems to *always* want to use the added ethernet card as eth0. On Wed, Feb 25, 2015 at 1:37 PM, Jason Warr <jason at warr.net> wrote: > Starting back in RHEL/Cent 5 I found that the only way to make sure your > interface enumeration was consistent after install

Hi all, I wonder if the gpgchecks are done while installing a system via anaconda? Any experts here? I was playing with the livemedia-creator and had a 3rd party repo in my ks file. The packages were installed without any problems although having not any key in the rpm db imported. So that leads me to the assumption that the gpgchecks are not done. How to get the integrity check done?

I realize that the @everything packages option is now gone in CentOS 5.0 (ix86 and x86_64), but my experiments to date don't show how to practically simulate the same effect (and I have a good reason for doing so). I want all packages, all languages. If one installs from CD, and selects all packages and options, the resulting anaconda-ks.cfg file does not have a complete package list. For

Hello, I need to automate installation of CentOS 7.0 using PXE and kickstart. My server is diskless, I'm installing CentOS on a 25GB LUN on a FC SAN with 4 paths. This LUN is the only one accessible by the server. Anaconda processes successfully the installation. But on reboot, I get stuck on a prompt after BIOS. I think I have an issue with storage configuration / bootloader

I took my anaconda-ks.cfg file, cp to ks.cfg and copied to a floppy The isos have been copied to an ftp server. So I had the following lines in my ks.cfg intall url ftp://10.1.1.1// (yes the ftp server's directory is the Centos directory) This is along with all the appropriate network command to get the ethernet setup. I issue the linux ks=floppy (also tried linux

hello there, I wonder if you could help me: I am trying to install 50 diskless servers using PXE / kickstart, it all starts well, DHCP server issues a dynamic address, tftp issues the kickstart file, the client starts reading the KS file but at some point anaconda brings up an unhandled exception related to Python when reading Comps.xml?? What is really unsettling is the fact that if I plug

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