topic Re: Only seeing one disk from EVA in Operating System - Linux

Only seeing one disk from EVA

Trent Ware — Wed, 28 May 2008 22:27:23 GMT

Recently we presented three disks from our EVA storage device to a new a new blade server. There was also installed new switches and firmware updated on the EVA. The blade server has a Qlogic 2462 card installed but after running the commands "hp_rescan -a" & "lssd" only one disk is seen.
Can anyone suggest what might be the problem?
If we configure the Qlogic drivers in Linux to run in single mode we see duplicate devices but only one when configured in failover mode.
Specs:
Blade - BL685c (Opteron)
EVA - EVA5000 (HSV110)
OS - Linux Red Hat AS 4 update 6
Regards,
Trent

Re: Only seeing one disk from EVA

Ivan Ferreira — Thu, 29 May 2008 00:57:37 GMT

What is the output of fdisk -l?
What devices do you see if you check your HBA with SanSurfer?

Re: Only seeing one disk from EVA

Trent Ware — Thu, 29 May 2008 01:20:16 GMT

Ivan,

Extract from "fdisk -l":
Disk /dev/cciss/c1d0: 366.8 GB, 366870733824 bytes
255 heads, 63 sectors/track, 44602 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/cciss/c1d0p1 1 44602 358265533+ 83 Linux

Disk /dev/sda: 429.4 GB, 429496729600 bytes
255 heads, 63 sectors/track, 52216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sda doesn't contain a valid partition table

---------------------------------------

Output from "lssd":
sda 0,0,3,3 COMPAQ HSV110 (C)COMPAQ 3110

---------------------------------------
We don't have SANSurfer installed. Also we presented the same three luns to an older DL385 and it saw all three.

Trent

Re: Only seeing one disk from EVA

Ivan Ferreira — Thu, 29 May 2008 03:14:00 GMT

>>> We don't have SANSurfer installed.

You should. This is a tool that may help you to troubleshoot problems, and you should check if you have Persistent target binding enabled.

Re: Only seeing one disk from EVA

Trent Ware — Tue, 03 Jun 2008 05:27:16 GMT

Problem resolved when from within the EVA Command View interface we changed the Host's IP address to static from dynamic!

Trent