topic Re: Disk Allocation in KickStart in Operating System - Linux

Disk Allocation in KickStart

ramizkhan — Tue, 06 Apr 2010 17:48:20 GMT

Can Anyone please help me for disk space allocation in kickstart file ?

This is my KickStart File

=======
#platform=x86, AMD64, or Intel EM64T
# System authorization information
auth --useshadow --enablemd5
# System bootloader configuration
bootloader --append="rhgb quiet" --location=mbr --driveorder=cciss/c0d0,cciss/c0d1
# Clear the Master Boot Record
zerombr
# Partition clearing information
clearpart --all --initlabel
# Use graphical install
graphical
# Firewall configuration
firewall --enabled --ssh
# Run the Setup Agent on first boot
firstboot --disable
# System keyboard
keyboard us
# System language
lang en_US
# Installation logging level
logging --level=info
# Use NFS installation media
nfs --server=10.32.200.6 --dir=/u01/oracle/OEL5/
# Network information
network --bootproto=dhcp --device=eth1 --onboot=on
# Reboot after installation
reboot
#Root password
rootpw --iscrypted $1$nDAdMwX7$QZgec1cFbmjla.tA3Y6ho.

# SELinux configuration
selinux --enforcing
# System timezone
timezone --isUtc America/Chicago
# Install OS instead of upgrade
install
# X Window System configuration information
xconfig --defaultdesktop=GNOME --depth=8 --resolution=640x480 --startxonboot
# Disk partitioning information
part /var --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=180
part /home --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=20
part / --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=300
part /usr --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=200
part /tmp --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=50
part /boot --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=20

=========

Ok the Error I get from Above KickStart File is following

Error:

Your selected packages require 2988MB of free space for installation, but you do not have enough available. You can change your selections or reboot.

My Question is :

Even though I created all the partitions on one "cciss/c0d0" why in KickStart it says following

--driveorder=cciss/c0d0,cciss/c0d1

This is the sample from another machine where I install Linux manually..But if in my Kickstart file If I mention "c0d0p8 or c0d0p6" it says it cant find this drive...

How Should I use"c0d0p3,c0d0p7,c0d0p8.." and all in my KickStart File ????

sample from other similar machine
===============================

/dev/cciss/c0d0p8 965M 567M 350M 62% /
/dev/cciss/c0d0p7 965M 20M 896M 3% /home
/dev/cciss/c0d0p6 3.8G 178M 3.5G 5% /var
/dev/cciss/c0d0p5 7.6G 2.2G 5.1G 30% /tmp
/dev/cciss/c0d0p3 7.6G 3.4G 3.9G 47% /usr
/dev/cciss/c0d0p1 487M 20M 442M 5% /boot
tmpfs 32G 16G 17G 49% /dev/shm

Re: Disk Allocation in KickStart

Stephen P. Schaefer — Wed, 07 Apr 2010 03:42:33 GMT

The "--size" options you specify are in megabytes. Assuming the disk space available is approximately the same as the example you site at the end, to achieve the same layout your disk partitioning would look like

# Disk partitioning information
part /var --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=3800
part /home --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=965
part / --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=965
part /usr --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=7600
part /tmp --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=7600
part /boot --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=487

although to allow for rounding errors, I would actually use

part /home --bytes-per-inode=4096 --fstype="ext3" --ondisk=cciss/c0d0 --size=1 --grow

(/tmp and /var are also appropriate candidates for the "use what's left" filesystems)

--driveorder is a hint to the installation software about which drive is preferred as the boot drive by the BIOS. I haven't had to deal with a situation where the default was inappropriate; I don't expect to specify it until I encounter a situation where it would make a difference (e.g., I change the BIOS to boot from the 2nd drive because it's solid state and that's where I want to put the OS, instead of the 1st (default) drive which is a traditional platter and more appropriate for the intended application data).

Re: Disk Allocation in KickStart

Vipulinux — Wed, 07 Apr 2010 14:00:10 GMT

Hi

Another way is to install a fresh machine manually and then in root directory there will be a file called anaconda.cfg; use this file as your ks file for all other kickstart installs.

Cheers
Vipul

Re: Disk Allocation in KickStart

ramizkhan — Thu, 08 Apr 2010 16:51:52 GMT

Actually, I opened the sample Anaconda.cfg Kickstart file and Used that
it works perfectly fine