I have a rather interesting issue with an onboard Promise RAID controller (20276 chipset) that maybe someone on this list has some insight on how I can resolve my problem. I am kickstarting servers that do not have CD-ROM or floppy drives, and given this, we build our own distributions from the base Redhat distro. In this case, we're dealing with Redhat 7.3 base distribution with all upgrades applied including kernel 2.4.20-18.7. The kernel is, for all intents and purposes, the Redhat stock 2.4.20-18.7 kernel rpm with all modules compiled in. In just kickstarting this server with a /dev/hda and the RAID array on /dev/hde and /dev/hdg (1x2 Mirrored) we boot and the promise module (pdcraid.o) IS NOT loaded by the kernel. At the root prompt we type modprobe pdcraid -- and it comes up working just fine, sees the array and lets us partition /dev/ataraid/d0 correctly. If we remove /dev/hda and leave the array in place, we are unable to kickstart the configuration onto the machine as it comes up and says that /dev/hde [resource is busy] and again, we're assuming the pdcraid module IS NOT being loaded at boot time. What am I missing here? It would seem so simple, but I have tried to put the device module in the kickstart configuration both as a %PRE command as well as using the device command to try to load it before the kickstart tries to start partitioning the machine. With the detection of the device by dmesg is there any need to add append information? Any help at this point would be deeply appreciated. Regards, -- J. Cary Howell Xilogix LLC
Attachment:
signature.asc
Description: This is a digitally signed message part
