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 FEBRUARY 10, 2025

Applies to:

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:

• For firmware 6.xx.xx.xx:
  The copy back operation will start, assuming that there are not more than two (2) operation in a combination of reconstruction or copy back taking place on the system. If so, it will be queued.
• For firmware 7.10.xx.xx (all revisions) through 7.35.xx.xx (all revisions):
  The copy back operation will start, assuming that there are not more than two (2) operation in a combination of reconstruction or copy back taking place on the system. If so, this requires user intervention to trigger the copy back. (See the Solution below)
• For firmware 7.50.xx.xx (all revisions) and higher:
  The copy back operation will start, assuming that there are not more than two (2) operation in a combination of reconstruction or copy back taking place on the system. If so, it will be queued.

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:

• For firmware 6.xx.xx.xx:
  The copy back operation will start, assuming that there are not more than two (2) operation in a combination of reconstruction or copy back taking place on the system. If so, it will be queued.
• For firmware 7.10.xx.xx (all revisions) through 7.35.xx.xx (all revisions):
  The copy back operation will not get queued and start automatically. This requires user intervention to trigger the copy back. (See the Solution below)
• For firmware 7.50.xx.xx (all revisions) and higher:
  The copy back operation will start, assuming that there are not more than two (2) operation in a combination of reconstruction or copy back taking place on the system. If so, it will be queued.

Use case 3

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

Results:

• For firmware 6.xx.xx.xx:
  The copy back operation will start, assuming that there are not more than two (2) operation in a combination of reconstruction or copy back taking place on the system. If so, it will be queued.
• For firmware 7.xx.xx.xx:
  The copy back operation will not get queued and start automatically. This requires user intervention to trigger the copy back. (See the Solution below)

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:

• For firmware 07.60.53.10 and later in the 6000 series:
  The copy back operation will not start automatically. This requires user intervention to trigger the copy back. (See the Solution below)
• For firmware 07.35.67.10 and later in the 2500 series:
  The copy back operation will not start automatically. This requires user intervention to trigger the copy back. (See the Solution below)
• For firmware 07.77.13.11 and later in the 2500-M2 series:
  The copy back operation will not start automatically. This requires user intervention to trigger the copy back. (See the Solution below)
  
  
  

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.