may be lossing it, but have you tried this ? heres one I used to use for the dl380 a while ago, only seemed to have problems with the bigger tri-PCI bus servers, but the dual PCI was fine. never had to specify a module but # # Language # lang en_US # # Network # network --bootproto dhcp # # NFS root server # nfs --server 172.16.28.147 --dir /mnt/kick # # optional non-autodetected device specification (ethernet, scsi, cdrom) # Deal with compaq array device scsi cpqarray # Onboard intel 82558/9 ? device ethernet eepro100 ## Cant remeber if it has an onboard AIC controller # device scsi aic7xxx # keyboard uk # # Partitioning # Get rid of the compaq partition, can't use remotley, use CD instead. zerombr yes clearpart --all yours A.r.b. -----Original Message----- From: kickstart-list-admin@xxxxxxxxxx [mailto:kickstart-list-admin@xxxxxxxxxx]On Behalf Of pierre-yves.verdon Sent: 11 December 2001 16:11 To: Carl Riches; kickstart-list@xxxxxxxxxx Subject: Re: need help for compaq dl360 with smart array . > No, because you will have already partitioned the disk in %pre and you > don't tell ks.cfg to zero the partition table. > > > well actually the kickstart installation stop after an output "loading > > module cpqarray" and then print "can not open device c0d0". > > if i switch to the console, the direcory /dev/ida and the device c0d0 > > have been created, but if i do "fdisk /dev/ida/c0d0" i get the same > > error "can not open device c0d0". > > if i do "lsmod" no cpqarray module have been loaded > > Have you done a manual installation to verify that the name of your > device? Is it really a cpqarray device? yes, i have check the modules that have benn loaded on a manually installed dl360, it's a cpqarray device below the "dmesg" output on a manually install dl360: cpqarray: Device 0x1000 has been found at bus 0 dev 1 func 0 Compaq SMART2 Driver (v 2.4.3) Found 1 controller(s) cpqarray: Finding drives on ida0 (Integrated Array) cpqarray ida/c0d0: blksz=512 nr_blks=71122560 cpqarray: Starting firmware's background processing below the lsmod output on a manually install dl360 Module Size Used by autofs 9568 1 (autoclean) eepro100 16144 2 (autoclean) ipchains 32192 0 (unused) cpqarray 15920 10 sd_mod 11040 0 (unused) scsi_mod 88656 1 [sd_mod] > My tack was different. I explicitly stated the start and end cylinders of > each partition. I feel that is is important to ensure that everything > happens the way I want it to happen. I got this information by first > doing a manual installation of the operating system, using fdisk to format > the disk. I made sure to _not_ erase and/or overwrite the "Compaq > Diagnostics" partition (/dev/ida/c0d0p3, but the first ten cylinders of > the disk). during the manually instaal i have erase the "Compaq Diagnostics" partition..... i have done the kickstart install with your "tack" but it didn't work ... (at the end my new kickstart config) i have notice some difference between the manual installation and the kickstart installation: after the "loading module cpqarray" i have switch to the terminal 2 in both redhat 7.1 kickstart and 7.1 manual redhat 7.1 manual: redhat 7.1 kickstart output from "lsmod" vfat vfat fat msdos sr_mod fat sd_mod raid5 scsi_mod xor ide-cd raid 1 cdrom raid 0 cpqarray eepro100 sr_mod sd_mod scsi_mod ide-cd cdrom so i have a new question: i would like to load in the %pre section some modules, how should i do? is suppose that there is something to uncompress or anything else... knowing that during the manual installation if i do: rmmod msdos -----> the module msdos is unloaded insmod msdos.o -----> the module msdos is loaded during the kickstart installation if i do: insmod msdos.o -----> the module msdos is *NOT* loaded auth --enablemd5 --useshadow cdrom keyboard us lang en_US lilo --location mbr part / --size 8000 part swap --size 512 mouse genericps/2 rootpw ft,2,ms timezone MET %packages @ Base %pre mkdir /dev/ida mknod /dev/ida/c0d0 b 72 0 chmod 660 /dev/ida/c0d0 echo | fdisk /dev/ida/c0d0 <<EOF n p 1 2008 n p 2 2009 2138 t 2 82 w EOF _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/kickstart-list
