Steps For Clearing Devices in Unusable or Failing State From cfgadm After LUNs Have Already Been Removed (Doc ID 1639070.1)

Last updated on JULY 29, 2016

Applies to:

Sun Storage FCoE CNA - Version All Versions to All Versions [Release All Releases]
Sun Storage FC HBA - Version All Versions to All Versions [Release All Releases]
Sun SPARC Enterprise M5000 Server - Version All Versions to All Versions [Release All Releases]
Emulex FC HBA - Version All Versions to All Versions [Release All Releases]
Solaris Operating System - Version 11.2 to 11.2 [Release 11.0]
Information in this document applies to any platform.

Goal

This document is for Fibre Channel (FC) LUNs not iSCSI or SCSI LUNs, primarily addresses LUNs and Targets that were access via a FC Switch fabric.

For issues clearing device entries of FC LUNs from a Direct Attached Storage (DAS) unit see section "Direct Attached Storage (DAS)"

The procedures outlined here are practical when dealing with a single or small group of LUNs.
If a large number of LUNs have been removed then a reboot would be quickest and cleanest way to clear them.

If you have not yet started removing LUNs and/or Targets from Solaris go to following document first:
Best Practice "Before" Removing LUN(s) and/or Target(s) From a Solaris Server (Doc ID 1639048.1

 

Note: If still unable to remove unuable devices after going thru this document see following doc:

Mapping new Luns Solaris host fails - cfgadm present LUN as Unusable - cannot remove unusable entries(Doc ID 1412745.1)

 


Before Beginning

Before attempting any of the steps in this document it is "Highly Recommended" that a explorer output be collected so there is a before and after reference. See Explorer section at the end below for instructions on preserving previous explorer outputs, upgrading to latest version of explorer and collecting new explorer with appropriate options.
 
This document deals with LUNs and Targets that have already been "intentionally" removed from Solaris server view, but device references in cfgadm, format, /var/adm/messages, etc. still exist and attempts to clear them using cfgadm command (see section below) have not succeeded.

These issues are primarily due to LUNs device tree entries still being seen or used by one or more applications on the server.

The disk may be seen in format as:

6. c4t500601653XXXXXXXd0 <drive type unknown> /pci@1,700000/SUNW,qlc@0,1/fp@0,0/ssd@w500601653XXXXXXX,0

or

in the messages files something like this:

Sep 10 10:51:28 server01 scsi: [ID 107833 kern.warning] WARNING: /pci@1,700000/SUNW,qlc@0,1/fp@0,0/ssd@w500601653XXXXXXX,0 (ssd50):
Sep 10 10:51:28 server01 drive offline


Any LUNs or Targets found to be in a NON-Optimal state and were not intentionally removed should be investigated before proceeding.

See doc
SAN Fibre Channel (FC) Storage Connectivity Issues (Doc ID 1502843.1)

Also recommend reviewing "How to Help Avoid These Types of Issues In The Future" section below as well.

 
TRY this first :  cfgadm command

This command is used when a subset (not all) of LUNs under certain Targets are removed. When removing an entire Target and all it LUNs see Target Removal section below.

Normally, when a LUN is removed Solaris will change it to a "failed/failing" state in cfgadm command output then within 30 second it will change to a "unusable" state.

1. If LUNs have not changed to unusable state yet , try running the following command then check again:



Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms