I don't see any error message during initial ramdisk "insmod" commands. It hangs at the point where it starts looking for the LVs with the "lvm vgscan --ignorelockingfailure" command. I can't do "lsmod" since the server doesn't boot. It goes into kernel panic and I have to power recycle it. TIA.
> ------------------------------ > > Message: 4 > Date: Tue, 16 Dec 2008 18:08:17 -0500 > From: solarflow99 <[email protected]> > Subject: Re: [rhelv5-list] Custom initrd for RHEL5.2 with qla2xxx > driver cannot find LVs at boot time > To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list" > <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > as long as the module is in your initrd it should be ok. What does lsmod > show, is it actually loaded? > > > On Tue, Dec 16, 2008 at 11:52 AM, Win Htin <[email protected]> wrote: > > > Hi folks, > > > > My first posting here. > > > > I am trying to make a custom init ramdisk on RHEL5.2 with qla2xxx drivers > > but the boot ups consistently fail with the following message: > > > > Red Hat nash version 5.1.19.6 starting > > Reading all physical volumes. This may take a while... > > No volume groups found > > Volume group "Volgroup00" not found > > Unable to access resume device (/dev/VolGroup00/root) > > mount: could not find filesystem '/dev/root' > > setuproot: moving /dev failed: No such file or directory > > setuproot: error mounting /proc: No such file or directory > > setuproot: error mounting /sys: No such file or directory > > switchroot: mount failed: No such file or directory > > kernel panic - not syncing : Attempted to kill init! > > > > Booting the server with standard 2.6.18-92.1.18.el5 initrd directly from > > SAN disk works without any issues. We are trying to use the customized > > initrd so that we can make use of the extra features QLogic drivers > provide > > at hardware level (configured through SanSurfer) instead of using dynamic > > multipathing etc. > > > > Following is a rather long mail I submitted at the QLogic forum: > > > > ================= START ========================== > > OS platform : RHEL5.2 x86_64 & CentOS 5.2 > > Server HW : IBM BladeServer HS21XM > > HBA : QMI2472 > > SAN : IBM DS4700 > > (NOTE : Tried the same on both RHEL5.2 and CentOS5.2) > > > > A bit of history: > > 1. The server can boot up directly from SAN with the current default > > "2.6.18-92.1.18.el5" RHEL5.2 kernel. > > 2. We also have a number of same type HW custom re-compiled with QLogic > > qla2xxx drivers on RHEL4. > > 3. We are trying to use the customized kernel so that we can make use of > > the extra features QLogic drivers provide at hardware level (configure > > through SanSurfer) instead of using dynamic multipathing etc. > > > > Following is the exact steps I took. > > 1. Install kernel-devel and kernel-headers packages. > > 2. download the QLogic driver file and extract the file into /tmp/qlogic > > directory > > 3. issue the command ./drvsetup (which creates the directory > > qla2xxx-8.01.07.15 > > 4. ran the following commands: > > a) cd qla2xxx-8.01.07.15/ > > b) grep -r pci_module_init * > > and edited the files ql2300.c, ql2100.c, ql2322.c, ql2200.c and > > ql2400.c > > changing the entry "pci_module_init" to "pci_register_driver" in > each > > file. > > c) ./extras/build.sh install > > d) depmod -av > > e) mkdir /initrd > > 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 > > > > Following is the error I'm still getting. > > > > ---------------------------------------------------------------- > > Red Hat nash version 5.1.19.6 starting > > **(the command "lvm vgscan --ignorelockingfailure" is generating the > > following 2 lines)** > > Reading all physical volumes. This may take a while... > > No volume groups found > > Volume group "Volgroup00" not found > > Unable to access resume device (/dev/VolGroup00/root) > > mount: could not find filesystem '/dev/root' > > setuproot: moving /dev failed: No such file or directory > > setuproot: error mounting /proc: No such file or directory > > setuproot: error mounting /sys: No such file or directory > > switchroot: mount failed: No such file or directory > > kernel panic - not syncing : Attempted to kill init! > > ---------------------------------------------------------------- > > > > Since I don't see any other error messages, I think I can safely assume > all > > kernel modules loaded properly but am still having grief with the LVs. > This > > is the major difference between RHEL4 and RHEL5. We didn't have LVs in > our > > RHEL4 servers. Then again, why is it working with the default RHEL5.2 > > kernel? It finds the LVs without any problems. Am I looking into > something > > totally unrelated with QLogic modules now? > > ==================== END ========================== > > > > I've been trying to resolve this problem for the past week without > success. > > Help is much appreciated. TIA. > > > > > > email : [email protected] > > "The unexamined life is not worth living" -- Socrates >
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
