Disk Enclosures
1752781 Members
6067 Online
108789 Solutions
New Discussion юеВ

disk enclosure problem on EVA4400?

 
iulianv
Advisor

disk enclosure problem on EVA4400?

briefly, the history is as it follows (the setup is an EVA4400 with one double-controller HSV300 enclosure and three disk enclosures):

a few days ago, one FATA disk simply disappears from its group - i only noticed it yesterday, re-inserted the disk and added it to its group again

before the leveling was complete, the disk disappears again, and all other disks in the same enclosure (some FATA, some 15K, so different disk groups) only remain reachable through a single port - to be more accurate, CV-EVA says that "Loop A" is unavailable for every disk in the enclosure; the other two enclosures are fine, and the problematic one reports both its I/O ports as "Good" in CV-EVA

i'll try replacing the disappeared disk soon, but i'm more concerned about the "missing loop" for all the disks - what might have caused that, what options do i have (besides CV-EVA event log) to further debug it, and what can i do to fix it? all these, as much as possible, without powering down the enclosure (i guess this would require shutting down the blade rack completely, since the disk groups will be unusable without one third of the physical volumes)

thanks in advance for any hints on this
20 REPLIES 20
Rob Leadbeater
Honored Contributor

Re: disk enclosure problem on EVA4400?

Hi,

The failing disk is probably causing some disturbance on the fibre channel loop, however your EVA4400 is almost certainly under support with HP so why speculate in a forum ?

Log a fault call !

Cheers,

Rob
iulianv
Advisor

Re: disk enclosure problem on EVA4400?

it is indeed under support - the whole rack was purchased about two months ago - i'll contact HP support after i reach some conclusion about the disappearing disk...

as i said, i just replaced it - the new one is reachable through both Loop A and B, but all the other disks in the enclosure still have Loop A not operational; i'll see what happens after leveling - is there any manual operation i have to do to "revive" Loop A on the rest of the disks, or it should go up automatically in case the FATA disk was the cause of the problem?
IBaltay
Honored Contributor

Re: disk enclosure problem on EVA4400?

Hi,
can you look at the controller log for determining the root cause of this behaviour pls? Can you list the main (critical) controller events here to seee what happened and to be able to interprete?
the pain is one part of the reality
iulianv
Advisor

Re: disk enclosure problem on EVA4400?

i'm attaching the related events, in reverse chronological order, as copy-pasted from CV-EVA's event log

leveling after replacing the "disappeared" disk completed normally - the new disk is reachable through both its ports, while all the other disks in the same enclosure still have LoopA unavailable; i'm thinking about restarting Controller 1 in the controller enclosure, in order to "force" port rediscovery of the devices
IBaltay
Honored Contributor

Re: disk enclosure problem on EVA4400?

Hi,
can you insert the problematic FATA disk in any other disk bay to see if the problem persists pls?
the pain is one part of the reality
patbourdon
Advisor

Re: disk enclosure problem on EVA4400?

hi, i just want reply to Rob, ok to "log a cal to support", but when support takes weeks to resolve a problem, you have to try to do the job yourself... i've some calls waiting for an good answer from hp support, sent a mail to support manager for speed up the call, but no solution to this day, so JulianV is right to try here... ;) (i'll log my problem in another thread in case somone can help me...).
Mark...
Honored Contributor

Re: disk enclosure problem on EVA4400?

Hi,

A few suggestions for you to try:
I often find that a problem is fixed but the warning triangle is still there on several items. Try clicking on every item with a triangle, in this case your disks and you MAY find that that will resolve your problem once you have clicked on all the items concerned. If this is the problem you should find that the warning triangle goes away when you click on each item but make sure you start at the lowest level ie the disks in this case.

If not, have you looked at the properties of the controllers and the "device ports" to see if there is a little tab that says "enable" as this will / should restart the loop concerned.

You can also open up the WOCP and look at the option "Configure controller device ports" which also has an option to re enable the device loops.

In the WOCP there are also some log files and controller information in the bottom two options. This may also give you some information about your current problem.

Finally I would suggest that if the disk disappeared from the loop/config in the first place then it could well be faulty and pulling it out and then putting it back in will not "make it better". If you have the capacity and you still have this "suspect" drive installed then I would suggest you use the "ungroup" tab to ungroup the drive correctly, then use the "remove" tab to take the drive physically out of the EVA and check the above suggestions again.

Mark...
if you have nothing useful to say, say nothing...
iulianv
Advisor

Re: disk enclosure problem on EVA4400?

on Monday i'll try inserting the problematic disk in another disk enclosure, to see if it "contaminates" that one as well; i'll also go wire the controller's management module's ethernet port, to see what WOCP has to say about this

as for clearing the yellow marks by clicking the items, what happens here is the other way around - when i open CV-EVA, all disks in the problematic enclosure are green under the "Hardware" tab; once i start clicking them, they get the yellow mark; but they are always yellow under the "Disk Groups" tab

i couldn't find any option to re-enable or restart disk ports or disk enclosure ports - just the "Shutdown" button for the two controllers
Mark...
Honored Contributor

Re: disk enclosure problem on EVA4400?

Hi,

The "enable" the loops tab only normally shows when a loop is down.

FYI - the default I/P address for the WOCP is 192.168.0.1
def user = "admin"
def password = NOTHING, just hit enter/return to login.

Mark...
if you have nothing useful to say, say nothing...