Copy Back not Starting After Replacing a Faulty Drive in a Sun Storage 2500, 2500-M2, 6140, 6540, 6580, 6780 and Flexline 380 (Doc ID 1164893.1)

Last updated on JULY 17, 2017

Applies to:

Sun Storage 6780 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage Flexline 380 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2530 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 6540 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2540 Array - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Symptoms

Use case 1

  1. Drive failed by SYSTEM or USER.
  2. Reconstruction completes to GHS successfully.
  3. Failed drive is replaced in the enclosure.

Results:

Use case 2

  1. Drive failed by SYSTEM or USER.
  2. Reconstruction to GHS starts.
  3. Failed drive is removed and replaced from system prior to the reconstruction completes.
  4. Reconstruction completes successfully.

Results:

Use case 3

  1. Drive is pulled from system.
  2. Reconstruction to GHS starts and completes.
  3. Failed drive is replaced.

Results:

Use case 4

  1. Drive is bypassed by the array fimware due to a hardware issue.
  2. Reconstruction to GHS starts upon the next write failure and it completes later.
  3. Bypassed drive is removed and replaced.

Results:

Cause

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