KICKSTARTing HPDL380G4 with RHELAS30UP3

[Aydin SASMAZ]

Hi all

using kickstart with rhleas30 update 3, it is no possible to create partitions on a cciss drive. Its very important because Im trying to set up some cluster systems by that way.

here is my kickstart config file ks.cfg
install
lang en_US.UTF-8
langsupport --default en_US.UTF-8 en_US.UTF-8 tr_TR.UTF-8
keyboard trq
mouse generic3ps/2 --device psaux
xconfig --card "ATI Mach64" --videoram 8192 --hsync 31.0-54.0 --vsync 50-120 --resolution 1024x768 --depth 24 --defaultdesktop gnome
network --device eth0 --bootproto static --ip 160.75.100.6 --netmask 255.255.255.0 --gateway 160.75.100.254 --nameserver 160.75.2.20,160.75.20.100,160.75.5.20 --hostname lnxsrv3-test2.itu.edu.tr
network --device eth1 --bootproto dhcp --hostname lnxsrv3-test2.itu.edu.tr
url --url ftp://160.75.2.215/RedHatELAS3.0UP3/i386
rootpw --iscrypted $1 xxxxx
firewall --disabled
authconfig --enableshadow --enablemd5 --enableldap --ldapserver="xxxxxx" --ldapbasedn="xxxxx" --enablekrb5 --krb5realm=xxxxxx --krb5adminserver="xxxx"
timezone --utc Europe/Istanbul
bootloader --location=mbr
zerombr yes
clearpart --all
part swap --size=2000 --ondisk=cciss/c0d0p1 --asprimary
part / --fstype ext3 --size=25000 --ondisk=cciss/c0d0p2 --asprimary
part /var/log --fstype ext3 --size=9000 --ondisk=cciss/c0d0p3 --asprimary


any ideas appreciated

thanks
aydin sasmaz

[Stuart Browne]

The 380G4's are using the on-board SA6i right?

I beleive you'll need the updated 'cciss' driver which is on the HP website, to be included into the boot-image that you're booting using.

Once that's in there, you'll have more luck.

URL's which might be of use:
http://h18000.www1.hp.com/support/files/server/us/download/22028.html
http://h18000.www1.hp.com/support/files/server/us/download/22017.html (unfortunately this appears to be for UP2 not UP3).

[Aydin SASMAZ]

Hi Stuart

actually im using RHELAS3.0 update 3 installion cds therefore modules come with it.I hane not encountered any problem in the usual installation from update 3 isos. Cd recognize and load the cciss.o driver hence i can create partitions via fdisk or diskdruid. But whenever i want to install g4 system with kickstart(ks.cfg), it cannot find the disk although it loads the correct updated driver. I suspect there is a problem with my kickstart conf like that part;
clearpart --all
part swap --size=2000 --ondisk=cciss/c0d0p1 --asprimary
part / --fstype ext3 --size=25000 --ondisk=cciss/c0d0p2 --asprimary
part /var/log --fstype ext3 --size=9000 --ondisk=cciss/c0d0p3 --asprimary

one of the error messages is about it cant create primary partitions. when i remove keywork asprimary, it also complaining about cant finding disk to create partitons. there is also similar problems, when i create partions manually and using onpart instead of ondisk

for additional info, g4 system's smart array firmware version 2.27

thanks for your assistence

[Aydin SASMAZ]

Hi

There is a bit strange situation has occurred that kickstart phyton scripts wants to create the root partition first than the others additionaly swap part the last. now this can work with this conf
clearpart --all
part swap --size 2000 --ondisk cciss/c0d0
part / --fstype "ext3" --size 1 --grow --ondisk cciss/c0d0

and if you would like to specify partition cciss/c0d0p1, kickstart interrupt and hit a bug (it says !!) creating a bug report!!

Do we have to follow a strict order to create partitions while we are using kickstart

[cemtan · Accepted solution]

For the SA6404 controller and all Red Hat Linux versions, excluding the lastest Red Hat Enterprise Linux 3 Update 2 and Red Hat Enterprise Linux 2.1 Update 4, the kickstart file will need to be modified to include the ondisk option to all the part command and drive option to the clearpart command to reference the appropriate controller and disk. For example, the clearpart and part /boot lines may look like
clearpart --all --drives=cciss/c0d0,cciss/c1d0
part /boot --size 50 --ondisk=cciss/c0d0

[Aydin SASMAZ]

thanks for everyone helped