- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Disk Allocation in KickStart
Operating System - Linux
1822158
Members
3285
Online
109640
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2010 10:48 AM
тАО04-06-2010 10:48 AM
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
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
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2010 08:42 PM
тАО04-06-2010 08:42 PM
Solution
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).
# 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).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-07-2010 07:00 AM
тАО04-07-2010 07:00 AM
Re: Disk Allocation in KickStart
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-08-2010 09:51 AM
тАО04-08-2010 09:51 AM
Re: Disk Allocation in KickStart
Actually, I opened the sample Anaconda.cfg Kickstart file and Used that
it works perfectly fine
it works perfectly fine
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP