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-79-1996351.1
Update Date:2018-01-08
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  1996351.1 :   Oracle ZFS Storage Appliance: Actions to Perform for FAULTED Drive Status  


Related Items
  • Sun ZFS Storage 7420
  •  
  • Sun Storage 7110 Unified Storage System
  •  
  • Oracle ZFS Storage ZS3-2
  •  
  • Sun Storage 7210 Unified Storage System
  •  
  • Oracle ZFS Storage ZS3-4
  •  
  • Sun Storage 7310 Unified Storage System
  •  
  • Sun ZFS Storage 7120
  •  
  • Sun ZFS Storage 7320
  •  
  • Sun Storage 7720 Unified Storage System
  •  
  • Oracle ZFS Storage ZS3-BA
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
  •  




In this Document
Purpose
Scope
Details


Applies to:

Sun ZFS Storage 7420 - Version All Versions and later
Oracle ZFS Storage ZS3-2 - Version All Versions and later
Sun Storage 7720 Unified Storage System - Version All Versions and later
Sun Storage 7210 Unified Storage System - Version All Versions and later
Oracle ZFS Storage ZS3-BA - Version All Versions and later
7000 Appliance OS (Fishworks)

Purpose

 This document is intended to provide the right actions to perform in case of UNAVAIL or FAULTED status on a drive

Scope

 Several actions can be considered while an UNAVAIL or FAULTED status is observed on a drive. 

Details

A faulted device behaves as if the device could not be opened, and no I/O is attempted.   FMA will activate a spare for this drive if one is available.

 

On systems running 2011.1.x firmware, a drive which has a fault is a FAULTED drive.

On systems running 2013.1.x firmware, a drive which has a fault is an UNAVAIL drive.

On systems running 2013.1.x firmware, a drive FAULTED or UNAVAIL should simply be physically replaced.

 

Drive status should not be cleared with the CLI/BUI markrepaired function without investigation.

 

The CLI allows the administrator to do this:

s7120-ftlauder-a:> maintenance problems select problem-000 markrepaired
Marking a problem repaired indicates that an administrator has fixed the underlying
problem and restored any affected components to their normal state. This is typically
only performed by Oracle service personnel or a documented Oracle repair procedure.

Are you sure you want to mark this problem repaired?

Are you sure? (Y/N) Y
Problem "75d0c5d4-a8d8-4b82-ee6d-adf1f457cad5" has been marked repaired.

If the user uses "markrepaired", and if the reopen of the device succeeds, the drive may come up with an ONLINE status, though the reason why it was degraded has disappeared, and some counters of errors reached are reset. 

Therefore, all sorts of bad behaviour may occur for this drive, potentially causing bad consequences on the ZFS pool, for instance - slowness or data corruption.

Marking errors repaired should not be done without investigation.

 

If there is some belief that the drive is not really UNAVAIL or FAULTED, and should not have been marked that way, the customer must involve Oracle Support and have a Support Representative analyze the situation of this drive.

The Support representative will request a support bundle and after analysis may provide a bug number and explanation why the drive was marked as UNAVAIL or FAULTED and then ask for the problem to be marked "repaired" as shown above.

In other cases, the errors generated by FMA on the appliance should not be marked repaired.

 


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