I'm trying to install CentOS 5.5 from harddrive using a kickstart file. Kickstart file is read correctly, it contains the following 3 lines (+ additional config):
I've downloaded both CentOS-5.5-i386-bin-DVD.iso and CentOS-5.5-i386-bin-1of7.iso, but anaconda (the installer) asks: - What partition and directory on that partition holds the CD (iso9660) images for CentOS? ...
VT3 gives these messages:
INFO: partition /dev/sda11 selected
INFO: mounting device sda11 for hard drive install
INFO: mntloop loop7 on /tmp/loopimage as /tmp/hdimage/repos/CentOS/5.5/isos/i386/CentOS-5.5-i386-bin-1of7.iso fd is 12
I have a working Centos 5.4 (== Red Hat Enterprise Linux 5.4) kickstart installation working with pxe boot.I am now trying to do the same kickstart installation but from a SCSI harddrive on the hardware box itself.In other words, the system already has an older distribution on it, and it has a formatted LVM partition with free space. I expect to upload an initrd, vmlinux, ks.cfg at the top of this partition, edit the grub.conf with something like so:
when i use kickstart to install centos from cdrom (i make it myself in my way),i got a %post script problem with the kickstart file. 1.%post script used to copy my own software from cdrom to hard disk.then make install automaitlly with bash script.
the %post script like : %post mkdir -p /myownsoftware cp -r /mnt/myownsoftware/* /myownsoftware cd /myownsoftware
we can't get the clients in our lab to do a kickstart install. we're doing the install by booting from the Centos 5.3 net install cd and anaconda starts, but terminates abnormally reporting a SIGSEGV fault. Interestingly, attempts at doing an install from a CD and without the network connection results in this error:
X11TransSocketINETConnect() can't get address for localhost:6001. Temporary failure in name resolution.
Can an unattended Kickstart support both IDE (hda) and SCSI (sda)? The goal is to to create a new virtual machine from scratch. What I have works for Parallels in which a new VM defaults to emulate an IDE hard disk. It does not work for VMware Workstation which defaults to emulate a SCSI disk.
The relevant Kickstart section: bootloader --location=mbr --driveorder=hda --append="rhgb quiet"
I'd like to install centos from a USB stick on to a hard drive and also include a custom kickstart on the USB stick to run post-build scripts or install additional packages, which the additional packages would also be on the USB stick..Are there any howto's already written?
i've worked with Linux for a while now, but never in a double boot kind of way (except using wubi), and i'm still kind of a newby.i have 2 harddrivesfirst one has only 1 partition; Windows XPsecond one has 1 empty partition, simple storageand another partition where i installed fedora core, and GRUB is also located on this harddrive.I changed harddrive priority to my second harddrive, result:GRUB comes up, no problem, but when I try to boot windows, it tells mentldr is missing ctrl alt del to continueso i changed the harddisk priority back to the way it was, where the first drive containing windows is first priority... but then, no GRUB.i've tried editing the grub conf,i've tried fixboot/fixmbrtl;dr:no ntdlr when linux harddrive is main priorityno grub when windows harddrive is main priority
Does anyone know of a way to tell the CentOS installer -not- to use LVM in a kickstart? We've been using a system that lets us define which particular drives to use during the installation as part of our deployment system. This does not work now that LVM is the 'default' in CentOS. I've looked over the options and I see how to FORCE particular LVM configurations, but I see no way to just turn it off.
I created a kickstart file and put it on a floppy. I have installed several times to refine the process and confused. I am not sure if the kickstart file is even being used by grub. I specified
autostep --autoscreenshot The install STILL asks me all those questions I was trying to avoid by doing autostep in the first place, and /root/anaconda-screenshots coes not exist.
I specified linux = hd:fd0:/ks.cfg
as a Grub command line option. I got that line off a forum, so it may be inaccurate. Anyone know if that is correctd? If I screw that up, shouldn't anaconda complain about file-not-found? Are the screenshots only applicable to graphics mode or also to text mode? (I have been using text mode, assuming text file screen dumps would appear in that subdirectory...)
I am trying to kickstart and want in post install to copy some files from a shared directory, to enable passwd less ssh and having same users across the clusters. But the cp does not work, nor does .ssh directory is getting created I have pasted my post install script below.
I have been using the same kickstart more or less since release 5.2 but it fails with 5.5. It looks like it is good all the way to the final stages. Does anyone know what has changed in anaconda for this release? I think the first boot process has changed as well.
i have two centos systems one automounts the external usb hard drive and other doesn't what do you think could be missing in the system that is not automounting the external usb drive.
I've been trying to mount an NTFS USB hardrive inside a Xen DomU, but I keep receiving a permission denied error.I am using CentOS release 5.4 (Final) x86_64 for both Dom0 and DomU with latest updates
DomU # mount /mnt/iomega ntfs-3g-mount: mount failed: Permission denied
Steps taken to reach the error:
1. I installed fuse and fuse-ntfs-3g in the Dom0 and successfully mounted the USD drive to make sure it worked. Then I unmounted it and block attached it to the DomU.
Dom0 # xm block-attach DomU phy:/dev/sdd xvdc r
2. I installed fuse and fuse-ntfs-3g in the DomU.I turned off SELinux (Though I don't think this is an issue)
DomU # /usr/sbin/getenforce Permissive
3. checked for the USB drive with fdisk and found it /dev/xvdc1
DomU # /sbin/fdisk -l Disk /dev/xvda: 10.4 GB, 10485760000 bytes[code]...........
I have downloaded the following kickstart file for installing minimal < 300 MB space centOS 5.2. I have created a Virtual Machine for Linux and attempting to install CentOS.here is my kickstart file:
I am using the "harddrive" option in a kickstart config to have it pick up isolinux files from a USB flash drive. I have been able to get it work by specifying the device name directly, but if I specify a LABEL or UUID, it does not work.Here is what my ks.cfg looks like.
Code: install text harddrive --partition=LABEL="/install" --dir=/ lang en_US.UTF-8
[Code]...
It almost seems like the version of Anaconda in Centos5.4 does not support specifying UUID or LABELs, but I have not been able to confirm that from the Release notes.Appreciate any tips/references/documentation.
I'm trying to dynamically write command section stubs with a pre-script to be included via %include. The simplest of these contains the disk partitioning commands. Following the canonical examples,[URL].. for one, of this found in every source of documentation for RHEL/Fedora variants does not work. Anaconda attempts to prompt for interaction to get the partitioning scheme and a cmdline install stops with "In interactive mode parttype, can't continue". I've stripped things down to the following two cases:
I am trying to do a kickstart installation of CentOS 5.5 x86 using a static IP on eth1. (The machine has 4 ethernet ports). I set ks, ksdevice, ip, netmask, and noipv6 when the boot disc asks for the init commands.I have similar networking information configured in the kickstart script. I have tried switching the order of the network config lines in the kickstart script to place eth1 at the top. Either way the installation hangs. On tty3 I can see that the command last called is getNetConfig. All of this configuration is using static IPs. I'm not sure why it thinks it has to do anything extra... Is there a problem trying to reuse the same eth1 NIC for the second stage? I have tried using the same and different IPs on the same subnet but nothing changes the outcome. Both the kickstart file and the install tree are on the same subnet, the same server in fact. Both are accessed via FTP but I had this problem with NFS as well.
I'm building kickstart files for my various machines.On my xen virtualization servers, I'm trying to get dom0_mem=512M added to the grub kernel line. Unfortunately, the bootloader --append option gets added to the linux kernel line, not the xen kernel line, which doesn't have the desired effect.Is there another way to put this into the kickstart file or should I use sed to put it into grub.conf in my post install section?
For portability reasons; I am building a standalone kickstart ISO; based of Cent5.2. I am to the point where I can load my ks file (linux ks=cdrom:/ks.cfg), it reads it fine; and performs the install as I want.
Where I am having a problem; is a good way to have the install use upgraded RPM's, not the base; specifically a kernel with a few needed tweaks in it; which is packaged in an rpm.
I attempted to place my kernel rpm's into the CentOS directory and rerun creatrepo; but I simply managed to corrupt the base repo on the install media.
I recently set up a kickstart server using Centos 5. I copied all 7 of the centos 5 install cd's to the tree. I made the install cd, it boots fine. I'm using http, when I'm prompted, I put in the web site: 1.1.1.1 and the Centos directory of /network-install/RPM
I get the following error:
Unable to retrieve [URL]
I've been told the double slashes after the ip address is not a problem, and I've tested that through a browser, by browsing the same location. (not sure if that's a valid test, but it did find the directory and display the files.)
we use for the installation of our machines bladelogic. We have different servers. Some servers have only one network interface, but it can be 2, 4 or may be more. There is always one network device for using PXE, but it is not always eth0.Is there any way to run kickstart without the entering of the PXE-Device so, that kickstart checks all the network devices in the system?
System gets corrupted when I abort a kickstart installationI have a simple kickstart installation of CentOS 5.5 (same issue on 5.3)The only user interaction is the partitioning screen.if, in my cfg file, I state :-
# Partition clearing information clearpart --all --initlabel or
I am trying to create a workflow for upgrading various systems using kickstart. I was hoping folks can point me in the right direction.I have a system which already has Centos installed on it. However it is a stripped down version of Centos using a custom kickstart installer. Now I would like to upgrade these systems, using an updated kickstart file spec. I would like to be able to copy over required files into a partition on the system, make a change in the grub.conf, reboot the system and expect the system to use the kickstart file and the iso file located on a partition on the system to self upgrade the entire system.The partition which holds the iso on these systems may be raided, or it may be an LVM partition.
How do I specify in the kickstart file that the location of the iso is on an LVM partition? Is this even supported? I have tried specifiying the disk like so:
< -- isolinux/ks/harddrive.cfg -- > upgrade text harddrive --partition=mapper/VolGroup00-LogVol02 --dir=/isolinux
[code]...
But the installer did not seem to like it. Instead of the iso, can I put the entire tree instead? Would that work?
I put a script into the post installation of kickstart and the log showed that the yum that is started in the script had to wait for yum to finish. I understand I can (and will) put this package in the packages section, but isn't it bad that yum is still finishing up when the post installation is initialized? Has anyone else noticed this?
I want a new kernel RPM in my custom CentOS 5 kickstart distro. I built the kernel, got a nice kernel RPM out, and replaced it in my ks.cfg. The install goes fine until the very end, where Anaconda prints some spurious stuff about mkinitrd failing.I get why it might fail -the kernel version argument to mkinitrd was no doubt for the old kernel. But I have no idea where this is -it's not in the ks.cfg afaict, and so I don't quite get where Anaconda / mkinitrd gets it from.
I'd eventually like to use this kernel for the installer as well, but I think I understand that process much better.How do I tell kickstart / Anaconda / mkinitrd to use the new kernel version number?
