I'm attempting to use a Kickstart file to provision a Thinkmate server that has 8 SDDs (0-7). The kickstart file I'm using is a slightly edited version of one that we successfully use all over our environment. The only change I made was to only partition the first two drives and leave the others as jbod due to requirements of the software the server will be running.
Not having much luck googling....
I'm working on our ks.cgi, and in the case that we're using gpt, I know
that kickstart can't, natively, use gpt yet. However, it is my impression
clearpart --initlabel --none --drives=$DISK
would wipe the GPT label. (Plus, googling, I find that initlabel is
Am I wrong about initlabel?
I was trying to do a kickstart installation for CentOS 6.4 but it always show me a warning of re-initializing the HDD as it say may contain invalid partition table or a virtual disk.
I have added below is the snapshot of the kickstart file I am trying to use
# System bootloader configuration
bootloader --append="crashkernel=auto rhgb quiet" --location=mbr --driveorder="sda"
# Clear the M
After managing to get a Fedora ISO to rebuild successfully (for a USB stick) after adding a kickstart file (http://serverfault.com/questions/548405/), I now have an issue with locating the kickstart file on the USB media.
When this is done from a CDROM you can simply kickckstart by adding this parameter to boot:
This will kickstart (providing the kickstart file is named ks.cfg a
I've been trying to use a kickstart file to guide the Red Hat installer (RHEL6.5) without user intervention. It correctly looks for the kickstart file in /dev/sdb/fs.cfg, but because the USB is recognized as /dev/sda, it is actually located at /dev/sda/fs.cfg.
In my kickstart installation I specify that the operating system should be installed on /dev/sda.
We have some Dell machines in our environment with iDRAC. When virtual media is attached in iDRAC, it maps Virtual CD drives and Virtual Floppy drives as /dev/sda and /dev/sdb leaving my desired installation drive as /dev/sdc.