Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Dell/EMC FC4500 & Powerpath path failures

Posted on 2006-07-13
10
Medium Priority
?
510 Views
Last Modified: 2013-11-15
Hi,
 
We have clustered PE2600's with a FC4500 with 5 DAE's direct attached.
 
We experienced multiple disk failures in our last DAE and after replacing the disks and rebinding the LUN, we are unable to access the disk within the OS (2000 Server) or Powerpath.
 
Everything looks fine within Navisphere, with no faults.
We have OpenManage Array Manager on one node which fails to find the disk when a scan is done.
On the other node we don't have array manager and when doing a scan within Windows Disk Management it also fails to find the disk.
 
Within power path we see the disk (probably from before we encountered multiple disk failures), but it says that the storage device has a failed status. It also shows the two paths c3t0d8 & c4t1d8 with a status of failed and a state of closed.
I've tried running powermt restore, with and without the force option, but it just tells me: Clariion device path c3t0d8 is currently dead, and the same for c4t1d8.
Anyone know how we can regain access to this enclosure??
Any help would be very much appreciated.
Thanks,
mark
0
Comment
Question by:markmall
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2
10 Comments
 
LVL 30

Expert Comment

by:Duncan Meyers
ID: 17106221
My immediate suspicision is that you may not have added the new LUN into the Storage Group that the server is in.

You'll need to start Navisphere Manager (from the fibre channel connected host)and log in.

In the Storage Tree, expand out Storage Groups. You'll see one or more storage groups. If you open up the storage groups, you'll see that they have a host and one or more LUNs in each one. Right-click on the storage group with the troublesome host in it and click on 'Select LUNs'. Click on the new LUN, click on the arrow pointing to the right and click on OK. Now reboot the host and it will see the LUN.

 
0
 
LVL 30

Expert Comment

by:Duncan Meyers
ID: 17106229
If the above solution doesn't fix your problem, then we'll need more information about your environment:

How many hosts are attached?
Are the hosts direct-connect or via a FC switch?
What is the FC4500 software revision?(click on the array serial number in Navisphere Manager, select properties and select the software tab. The FLARE code revision will be either in the format 02.06.0.x00.xx or (more likely) xx.xxxx. Could you also click on the Access Control tab and see if the Access Control Enabled tick box is ticked an greyed out?
0
 

Author Comment

by:markmall
ID: 17106683
Hi Meyersd,

Thanks for you replies.
Firstly, we have two hosts attached and they're direct connected.
Secondly, we don't use storage groups.

When I get the properties of the array, I don't have a software tab or an access control tab, I just have the following tabs:
General
Cache
Memory
Storage Access.
Am I looking in the right place? I don't see anywhere else where there's a software tab!?
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
LVL 30

Expert Comment

by:Duncan Meyers
ID: 17107879
Ummmm...

You're on Navisphere 5.3 or earlier I guess. Which means some pretty serious remembering on my part :-)

The Storage Access tab will have a tick box that says something like "enable access control" but if you only have two hosts and no storage groups, then you're unlikely to have access control enabled anyway - it was an extra-cost option on those earlier arrays.

Do you have two FC cables from each host to the array or one cable only from each host to the array? If you have a single cable only, or both cables to the same storage processor, then the most liekly cause of your problem is that the new LUN is assigned to the other storag eprocessor. To trespass the LUN, right click on it and select "trespass". If that fixes your problem you'll then need to open the properties of that LUN and set the default SP to that storage processor.

...

A penny has just dropped. It may be that clusdisk.sys is masking the new LUN. You can check that by disabling clusdisk.sys. Go into Computer Management - Device Manager. Enable "Show Hidden Devices" on the View menu, then Expand Non-Plug and Play Drivers, right-click Cluster Disk Driver, click Properties, click the Driver tab, in the Startup type list click Disabled, and then click OK, the restart the computer. If you can then see the new LUN, create a partition on it, the reenable clusdisk.sys and reboot. ***Note that you should only have one node running in the cluster when you do this.****

Another thing to try depends on your FC HBAs and how old they are. You could try going into the HBA BIOS, enable the HBA BIOS and then check to see if the card can see any FC devices. Make sure that you disable the BIOS once again after you've finished the test.
0
 

Author Comment

by:markmall
ID: 17112264
Thanks again for these suggestions.
I had a look in "About" on Navisphere and it says our version is 6.2.0.6.0.
On the Storage Access tab there's just one option that says "Enforce Fair Access", but as you suggested it's greyed out.

I've tried the trespass scenario, but that didn't fix the problem.

I'm keen to try the clusdisk scenario as well, but I'm obviously going to have to schedule some down time to try that. It's the weekend here now and so I won't get a chance to organise that for a few days. I'll let you know how I get on when I've gotten around to it.
Thanks again.
mark
0
 
LVL 30

Accepted Solution

by:
Duncan Meyers earned 2000 total points
ID: 17113455
You can probably/almost certainly get away with bringing up the second box with clusdisk.sys disabled - but there's always a risk that Windows will try to write to the disks that it can see - and that results in terminal corruption. I've sucessfully done the clusdisk thing on a quite a few occasions and got away with it, but it's far better to be safe than sorry...
0
 
LVL 30

Expert Comment

by:Duncan Meyers
ID: 17597714
Points please!
0

Featured Post

New benefit for Premium Members - Upgrade now!

Ready to get started with anonymous questions today? It's easy! Learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Microservice architecture adoption brings many advantages, but can add intricacy. Selecting the right orchestration tool is most important for business specific needs.
Backups and Disaster RecoveryIn this post, we’ll look at strategies for backups and disaster recovery.
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This Micro Tutorial will teach you how to reformat your flash drive. Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. Make sure to backup all files before reformatting. This w…

670 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question