Cant see NEW LUN on RedHat Box
Hello,
I'm in LUN hell at the moment. Everytime I present a new LUN from my HP EVA to our RedHat box's, I have to reboot the server in order to see the new LUN ????? Im told the old Administrator used to see new luns within seconds by running the following commands: # hp_rescan -a # lssd I have also ran the above commands on RedHat machines and been able to see any new presented LUNS? What would cause hp_rescan to fail? As I say, once I reboot the box, lssd shows the new luns and then I just pvcreate them. Any ideas? R. Bboy-mass |
I guess it also comes down the hba drivers: if you're using qlogic try this:
http://kb.qlogic.com:8080/KanisaPlat...6/14182_f.html |
Yes, but we have always used the same HBA cards and drivers. So why would a driver stop working all of a sudden?
R. Bboy-mass |
I have the same problem as you.
HP advice me to raise the initrd file in order to manage the problem. Here is the mail HP send me : In summary: 1. Modify /boot/grub/grub.conf or whatever bootloader being used to pass the larger ram disk size as a parameter to the kernel. Grub: add the parameter ramdisk_size=n to the kernel line. Lilo: add new line append=ramdisk_size=n after kernel line. 2. Modify /sbin/mkinitrd and change the IMAGESIZE=n variable to match n in bootloader change. 3. Create a new ram disk with /sbin/mkinitrd script as usual For this configuration, use n=16000. I have done the manipulation yet because I can't reboot the server right now but. If you want to try, please return me the results. Hope it will be helpfull. |
This works on our systems (RH4 & RH5):
Code:
echo 1 > /sys/class/fc_host/host0/issue_lip # not necessarily needed -reinitializes the HBA |
I added a new LUN from IBM 8100, and the OS (RHEL 5.3) sees the new devices (fdisk -l), however when I run pvscan I do not see the new LUN. How do I get LVM to see the new LUNs?
Thanks, |
All times are GMT -5. The time now is 07:10 AM. |