On Tue, 2008-12-16 at 11:52 -0500, Win Htin wrote: > 5. copied the currently booted kernel image from /boot dir to temp > directory. > cp /boot/initrd-2.6.18-92.1.18.el5.img /tmp/image > 6. cd /tmp/image > 7. mv initrd-2.6.18-92.1.18.el5.img initrd-2.6.18-92.1.18.el5.img.gz > 8. gzip -d initrd-2.6.18-92.1.18.el5.img.gz > (This will be inflated into initrd-2.6.18-92.el5.img file) > 9. cd /tmp/image && cpio -i --make-directories < > initrd-2.6.18-92.el5.img > 10. mv initrd-2.6.18-92.el5.img ../ > 11. vi "init" file and add: > a) echo "Loading intermodule.ko module" > insmod /lib/intermodule.ko > == just above the line ' echo "Loading qla2xxx.ko module" ' > b) echo "Loading qla2xxx_conf.ko module" > insmod /lib/qla2xxx_conf.ko > == just below the line ' echo "Loading qla2xxx.ko module" ' > 12. cp qla2xxx.ko file from /lib/modules/`uname > -r`/kernel/drivers/scsi/qla2xxx to /tmp/image/lib dir. > 13. cp qla2xxx_conf.ko file from /lib/modules/`uname > -r`/kernel/drivers/scsi/qla2xxx to /tmp/image/lib dir. > 14. cp /lib/modules/`uname > -r`/kernel/kernel/intermodule.ko /tmp/image/lib > 15. made the new initial ramdisk image: > cd /tmp/image && find . | cpio -o -H newc | gzip -9 -n > > ../initrd-`uname -r`-QLFO.img > 16. cd .. && cp initrd-`uname -r`-QLFO.img /boot > 17. vi /boot/grub/menu.lst file and added the QLogic initrd entry > 18. # init 6 from console
It's been a very long time since I used the Qlogic OEM drivers, and I have no idea why anyone would voluntarily submit themselves to supporting a system using these drivers, especially on a boot-from-san system. The native multipath support has come so far and is so much better and more flexible. Still, I think I remember that the qla2xxx_conf.ko module actually stores the configuration for the adapter. The "module" actually contains the data from /etc/qla2xxx.conf file which contains all of the setup information for LUN binding, failover, etc. I'm guessing your just copying "empty" versions of these modules and thus they contain no actual config information and thus find no LUNS. Ideally, you should post the information that's displayed when the module is loaded from your initrd. Can you see that the LUN's are actually being discovered by the driver? If you're having a hard time capturing data from the boot I'd suggest configuring a serial console to grab the data. Later, Tom _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
