Unowned LUNs CX4

There are unowned LUNs, but both SPs are up and running. (0)
Arrays with Multiple Problems: See
Knowledgebase article emc81176
when troubleshooting Fibre Channel
arrays with multiple problems. This
solution examines the order that the
Run spcollect on both SPs and review the logs for either CRU Signature Error, problems should be addressed to
or Cant assign Cache Dirty. maximize the chance of success.

NOTE: If the array contains one or more faulted drives or if the logs indicate that
there are back-end or disk-related errors that indicate faulty hardware, refer to the
appropriate troubleshooting tree.

If necessary, return to this tree. (1)

Clear the cache dirty condition using information in

Are there Cache Dirty solutions emc119801. Be sure to alert the customer of a
Yes
messages? (2) possible data loss associated with clearing the cache dirty
condition as all pending writes on the LUN are lost. (3)

No

Are there CRU signature

Yes Escalate to engineering. (5)
errors? (4)

No NOTE: When closing any

solved case, be sure to
specify in CSI what action
was taken that solved the
Are there still
No Close the case. (7) problem. If an escalation is
unowned LUNs? (6)
necessary, make sure that
you have the spcollect
data.
Yes

If there are still unowned LUNs, there may be a failed LCC or cable on one of the two Loops.
This will result in unowned LUNs only if failover software was not present, not configured
properly, or not working properly.

Check the logs on both SPs and make sure that both paths (A and B) are available.

If only one log shows the disks missing, that is further evidence that this is probably a faulted
LCC or cable (on the loop that shows them missing). (8)

Are there still

Close the case. (10) No Yes Escalate to engineering. (11)
unowned LUNs? (9)