Integrity Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

LUNS not getting visible

 
Scorpianzzz
Advisor

LUNS not getting visible

Hi,

I have configured a rx2660 server and presented LUNS to it from EVA4400. The OS installed is 11i v2.

When the system is shutdowned and then powered on, all the LUNS are visible and everything is fine...

Now when i reboot the system, the LUNS disappears...

1. When I do
# vgdisplay -v vg01

vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "vg01".

2. When I do
# vgchange -a y vg01

vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c4t0d1":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Warning: couldn't query physical volume "/dev/dsk/c4t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c6t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "vg01":
Quorum not present, or some physical volume(s) are missing.

3. But when I do
# ioscan -fnCdisk

It shows all physical volume as CLAIMED
... and then ALLOWS me to ACTIVATE Volume Group "vg01"

The file /etc/lvmtab also looks fine...

Can ne1 help me out with this problem. Its urgent...

Regards,
Rajiv
4 REPLIES 4
TTr
Honored Contributor

Re: LUNS not getting visible

It looks like a timing issue. When the server boots up and scans all the devices (ioscan) and then activates all the volume groups, the FC LUNs are not yet visible in the server. The ioscan forces the FC LUNs to become claimed and then you easily activate them manually.

Check if there are any disk or fiber related patches for the server that will make the server discover the LUNs quicker.

Also after the server has booted, try
"ioscan -fnkC disk" (note the "-k") a few times to see what the status of the LUNs is without forcing a rescan of the FC bus. Maybe the LUNs eventually become CLAIMED.

If all else fails, you can add an ioscan and vgchange towards the end of the boot process in /sbin/init.d, /sbin/rc3.d sequence just for these LUNs and VG.
Scorpianzzz
Advisor

Re: LUNS not getting visible

Hi,

Thanks 4 d reply...

I hav noticed that when i do
# ioscan -funCdisk
it DOES NOT CLAIM the disk...

but when i do
# ioscan -fnCdisk
it claims the disk...

Can u tell me more abt the script on rc3.d...
Cos tht ll b my last option

Thanks,
Rajiv


TTr
Honored Contributor

Re: LUNS not getting visible

Check for patches first and open a case with HP support as well. You should only use the method below as a last resort, it is not really a clean way of doing things in HP-UX. You can create a startup script called /sbin/init.d/fc-luns and in it you put the "ioscan..." and "vgchange -a y..." commands. Use the -H option in ioscan to limit the ioscan to the FC HBAs only. To create this script use the /sbin/init.d/templade as a template (I prefer to use the /sbin/inti.d/lp script). You only need a "start-msg" and "start" option in the script. Then you have to link the script in the startup sequence by creating a symbolic link in /sbin/rc3.d. Call this link /sbin/rc3.d/S999fc-luns and symbolic-link it to /sbin/init.d/fc-luns. This way the /sbin/init.d/fc-luns will run at the very end of the boot sequence. You would have to try it out and if necessary put delays before, in between and after the ioscan-vgchange commands.
Scorpianzzz
Advisor

Re: LUNS not getting visible

Thanks for all ur reply....

The problem has been resolved...

The main culprit was the FC card... replaced it and it worked fine...


Thanks again...