Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2095999.1
Update Date:2016-09-22
Keywords:

Solution Type  Problem Resolution Sure

Solution  2095999.1 :   FS System: Disk Drive Replacement Does Not Change Status to Normal  


Related Items
  • Oracle FS1-2 Flash Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-11834100214>

Applies to:

Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

 A failed drive does not change its status after being physically replaced.

Cause

The component causing the drive to appear to be failed may actually be the drive backplane.

Solution

When compared to drive failures, bad slots in the drive backplane of an FS1-2 Drive Enclosure are extremely rare events. If a drive replacement does not resolve the problem, follow the steps below:

  1. Do NOT send back the original drive to Oracle until the problem is resolved.
  2. Contact Oracle support to have the Service Request assigned to a Technical Support Engineer.
  3. Note the status of the Drive LEDs.
  4. Using the appropriate Drive Enclosures number, gather a ddump (Diagnostic Dump) from both IOMs (IO Modules). Refer to the <Document 1954866.1> FS System: How to Collect the System-Wide Diagnostic Dump From Drive Enclosure (DE2-24C or DE2-24P) IO Module (IOM) for the instructions.


    NOTE: Default passwords for the FS1-2 are covered in <Document 2046703.1> FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System.
     

  5. Upload the ddump output from both IOMs to the Service Request. See <Document 1596914.1> My Oracle Support - How to series -> How to upload and attach files to Service Requests using three options for details.

    Internal Only...

    TSEs: Look in the ddump output just past the "DrvMgr" section where it lists the Drive Bay status of each slot.  Look at the suspected bad slot for any abnormalities. A comparison to an adjacent slot can be used if it is known to be good. Here is an example of a failure in slot 13.  Items to make note of are an invalid WWN, and faults 5 faults:
    **** Drive Bay 13 status ****
    present        : yes 
    SES_info_bit   : not set 
    RAID_info_byte : 0x0 
    spin up time   : 214+01:51:14.087 
    drive_type     : SAS 
    WWN            : 0000000000000000 
    faults         : SES set fault; GEM set fault; Comms problem (IO Module 1); Comms problem (IO Module 2); Voltage problem; 
    fault LED      : ON 
    array LED      : OFF 
    inject         : NONE 
    pending        : ONLINE 
    current        : ONLINE 
    SlotA 
      bypass       : 0x00 
    SlotB
      bypass       : 0x00
    force off      : no 

Given the disruptive nature of a Drive Enclosure chassis replacement, Oracle Support will likely send a second drive in an attempt to avoid that disruption. If the second replacement also fails, repeat steps 3 and 4 to help confirm if the chassis needs to be replaced.

NOTE: If a Drive Enclosure chassis replacement is needed, be sure to put the original drive back into its slot before the chassis replacement. Failure to do so will result in the Drive Group that has the drive failure not being imported afterwards, making the recovery of the FS1-2 more difficult.

 

References

<BUG:22500083> - DE 9 MIDPLANE WAS REPLACED AND NOW IT SHOWING AS DE 13 AND DG 4 OFFLINE

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback