similar to: environment variables in kickstart

Dear Friends, I have centos 6.2 64 bit os in my dell server. When I try to install centos or scientific linux using NFS so it is not working and getting me error = "unable to download kickstart file". My kickstart file configuration is : #platform=x86, AMD64, or Intel EM64T #version=DEVEL # Firewall configuration firewall --disabled # Install OS instead of upgrade install # Use NFS

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

I am trying to use kickstart for automated builds from a DVD. Some of the machines have DVD's drives and some have CDRom drives only. With the CDRom only machines I would like to plug in an external DVD drive via USB and use this to kickstart. The DVD only machines work correctly with a isolinux.cfg as label test kernel vmlinuz append initrd=initrd.img ramdisk_size=8192

Here's what I'm currently doing in ks.cfg: %pre #!/bin/sh echo -n "Please enter blah: " read blah echo $blah > /tmp/ks-blah I know that "read blah" works fine, because after that I see the variable in the /tmp file. The problem is, echo doesn't seem to work at this stage. This pretty much kills the idea of an interactive %pre script. I was thinking to

I am trying to add a kickstart file to my automatic installation and make it more automatic. However, when I comment out the append ks=... line in the example below, the computer boots properly. If I uncomment that line, then I get a kernel panic: VFS: Cannot open root device "" or 09:02 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root

Patrick Lists wrote: >>> I fail to see how your repository problem is related to my Kickstart PXE/NFS >>> problem. We can install CentOS 6 (no Kickstart) without problems using PXE. >>> It's the NFS-mounting of the Kickstart-file which fails. What I'd love to learn >>> is how others have made NFS/Kickstart work... >> >> Is CentOS 6 assuming

Hi, I?m trying kickstart on CentOS Below is my ks.cfg *[root at localhost ~]# cat /root/ks.cfg* * * #Generated by Kickstart Configurator #platform=x86, AMD64, or Intel EM64T #System language lang en_US #Language modules to install langsupport en_US #System keyboard keyboard us #System mouse mouse #Sytem timezone timezone Asia/Dili #Root password rootpw --iscrypted

Hey Everyone, I was wondering if anyone has managed to do a network install where the kickstart file is located either on an FTP site (which is also where the packages are stored) or on a USB flash drive. I've tried starting the installer with "linux ks=/dev/sda/ks.cfg" or "linux ks=/dev/sda1/ks.cfg" or "linux ks=ftp://what.ever.Ip.address/pub/ks.cfg" but

Hey, someone just told me yesterday that I can give my machine an initial IP address, gateway, dns server, and netmask via command line like this: linux ks=http://www.mydomain.com/kick.ks ip=192.168.1.5 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.10 Is this true? Is the syntax wrong or right? If so, and I call my kick.ks file and it has install cdrom it'll pull the files

Hi, I have alot of kickstart and scripting going on as I provision lots of machines, and every now and then I run into a pesky machine or three that's still got that Adeptec zero-channel RAID card sitting on the board. Normally I like to rip it our and throw something more robust in, but if it's a cache machine or whatever, I leave it in. It makes my kickstart file useless until I

I have successfully set up a very nice kickstart install with the i386 version of CentOS 4.3 and it works great. I am using a custom kickstart script and the kernel and initrd from disc1/images. But when I try to duplicate this for a 64 bit setup (changing paths in my tftp server, ks.cfg, etc to point to the 64 bit stuff) it successfully tftp's everything just as it should (tethereal

We have CentOS 6 manual installation working by PXE booting from a RHEL5.6 PXE/TFTP server. However, when we add a Kickstart file in the PXE configuration: kernel CentOS-6-i386/vmlinuz append load_ramdisk=1 initrd=CentOS-6-i386/initrd.img network ks=nfs:130.226.86.4:/u/rpm/kickstart/ks-centos-6-clean-i386.cfg then the CentOS 6 client install reports "Unable to download the

Hello list, I try to do an automated network installation of centos 5.2, following the redat documentation at http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/pt-install-info.html However, when installing I get promptet for various things, like which network interface I would like to use for installation, or the location of the install medium. But thats not what I

I am getting the following error on boot on a new install Centos 51: #/bin/sh ro no such file or directory then a kernel panic I have traced it to the call ''switchroot'' in the init script in the initrd. the exact same build without zen has no problems. the boot messages look like: Attaching to iSCSI storage iscsistart: transport class version 2.0-724. iscsid version 2.0-865

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 08:16 PM, Steven Tardy wrote: > >> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner >> <ashley at pcraft.com> wrote: >> >> I have a Dell server that has two built-in ethernet devices. When >> I kickstart the machine, they are correctly identified as eth0 >> and eth1 (correctly meaning they

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

<overly trimmed> On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > Ok, so some of this now works, but I'm still having problems. With the > bootif option, the system now correctly configures and uses the same > interface to get its kickstart file. However, when the system is done and > boots up, the interfaces are still messed up. So this is what I have in the >

I can get the kickstart command line with /proc/cmdline it looks something like xxxxx ks=http://192.168.1.8/ks/ks.cfg xxxxxx in the %pre sections of my ks.cfg I was wanting to extract the IP from the ks= part. I was going to utilize the "tr" command but its not available in %pre. how can I go about extracting the IP address from with in the %pre section I was going to do something

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

Starting back in RHEL/Cent 5 I found that the only way to make sure your interface enumeration was consistent after install with what you had during install was to create a udev rules file using the mac addresses as the key. It is easy to run a short script in postinstall to create it based on how anaconda has seen them. In order for this to work on Cent 6 you have to set biosdevname=0