1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8

1

Ensure that your replacement controller matches the controller in the storage array. If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

2

Stop all I/O to this storage array.

3

Turn off power to the affected tray.

4

Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.

5

6

7

If you have volumes mapped to hosts that have Automatic Volume Transfer (AVT) disabled, it may be necessary to redistribute the volumes to their preferred controller. Use the following steps to determine the AVT status of the hosts connected to your storage array:

8

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel.

2

Place the affected controller offline.

3

Read all of the following steps before taking any action.

4

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8

1

Ensure that your replacement controller matches the controller in the storage array. If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

2

Stop all I/O to this storage array.

3

Turn off power to the affected tray.

4

Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.

5

6

7

If you have volumes mapped to hosts that have Automatic Volume Transfer (AVT) disabled, it may be necessary to redistribute the volumes to their preferred controller. Use the following steps to determine the AVT status of the hosts connected to your storage array:

8

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel.

2

Place the affected controller offline.

3

Read all of the following steps before taking any action.

4

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8

1

Ensure that your replacement controller matches the controller in the storage array. If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

2

Stop all I/O to this storage array.

3

Turn off power to the affected tray.

4

Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.

5

6

7

If you have volumes mapped to hosts that have Automatic Volume Transfer (AVT) disabled, it may be necessary to redistribute the volumes to their preferred controller. Use the following steps to determine the AVT status of the hosts connected to your storage array:

8

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel.

2

Place the affected controller offline.

3

Read all of the following steps before taking any action.

4

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8

1

Ensure that your replacement controller matches the controller in the storage array. If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

2

Stop all I/O to this storage array.

3

Turn off power to the affected tray.

4

Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.

5

6

7

If you have volumes mapped to hosts that have Automatic Volume Transfer (AVT) disabled, it may be necessary to redistribute the volumes to their preferred controller. Use the following steps to determine the AVT status of the hosts connected to your storage array:

8

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel.

2

Place the affected controller offline.

3

Read all of the following steps before taking any action.

4

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8

1

Ensure that your replacement controller matches the controller in the storage array. If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

2

Stop all I/O to this storage array.

3

Turn off power to the affected tray.

4

Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.

5

6

7

If you have volumes mapped to hosts that have Automatic Volume Transfer (AVT) disabled, it may be necessary to redistribute the volumes to their preferred controller. Use the following steps to determine the AVT status of the hosts connected to your storage array:

8

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel.

2

Place the affected controller offline.

3

Read all of the following steps before taking any action.

4

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8

1

Ensure that your replacement controller matches the controller in the storage array. If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

2

Stop all I/O to this storage array.

3

Turn off power to the affected tray.

4

Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.

5

6

7

If you have volumes mapped to hosts that have Automatic Volume Transfer (AVT) disabled, it may be necessary to redistribute the volumes to their preferred controller. Use the following steps to determine the AVT status of the hosts connected to your storage array:

8

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel.

2

Place the affected controller offline.

3

Read all of the following steps before taking any action.

4

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8

1

Ensure that your replacement controller matches the controller in the storage array. If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

2

Stop all I/O to this storage array.

3

Turn off power to the affected tray.

4

Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.

5

6

7

If you have volumes mapped to hosts that have Automatic Volume Transfer (AVT) disabled, it may be necessary to redistribute the volumes to their preferred controller. Use the following steps to determine the AVT status of the hosts connected to your storage array:

8

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel.

2

Place the affected controller offline.

3

Read all of the following steps before taking any action.

4

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8

1

Ensure that your replacement controller matches the controller in the storage array. If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

2

Stop all I/O to this storage array.

3

Turn off power to the affected tray.

4

Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.

5

6

7

If you have volumes mapped to hosts that have Automatic Volume Transfer (AVT) disabled, it may be necessary to redistribute the volumes to their preferred controller. Use the following steps to determine the AVT status of the hosts connected to your storage array:

8

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel.

2

Place the affected controller offline.

3

Read all of the following steps before taking any action.

4

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8

1

Ensure that your replacement controller matches the controller in the storage array. If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

2

Stop all I/O to this storage array.

3

Turn off power to the affected tray.

4

Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.

5

6

7

If you have volumes mapped to hosts that have Automatic Volume Transfer (AVT) disabled, it may be necessary to redistribute the volumes to their preferred controller. Use the following steps to determine the AVT status of the hosts connected to your storage array:

8

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel.

2

Place the affected controller offline.

3

Read all of the following steps before taking any action.

4

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

click the Recheck button to see if the problem has been fixed.

If this problem still appears in the Summary area, go to step 3.

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8

1

Ensure that your replacement controller matches the controller in the storage array. If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

2

Stop all I/O to this storage array.

3

Turn off power to the affected tray.

4

Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.

5

6

7

If you have volumes mapped to hosts that have Automatic Volume Transfer (AVT) disabled, it may be necessary to redistribute the volumes to their preferred controller. Use the following steps to determine the AVT status of the hosts connected to your storage array:

8

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel.

2

Place the affected controller offline.

3

Read all of the following steps before taking any action.

4

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8

1

Ensure that your replacement controller matches the controller in the storage array. If you do not have a controller with the appropriate replacement part number, contact your technical support representative.

2

Stop all I/O to this storage array.

3

Turn off power to the affected tray.

4

Remove the affected controller. Refer to the Enterprise Management Window (EMW) to view which management method you are using to manage this storage array.

5

6

7

If you have volumes mapped to hosts that have Automatic Volume Transfer (AVT) disabled, it may be necessary to redistribute the volumes to their preferred controller. Use the following steps to determine the AVT status of the hosts connected to your storage array:

8

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Determine which is the affected controller by locating the non-working channel. Refer to step 3 at the beginning of this recovery procedure for details on how to locate the non-working channel.

2

Place the affected controller offline.

3

Read all of the following steps before taking any action.

4

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.

1

Fix any other problems reported by the Recovery Guru before attempting to fix this problem.

2

3

4

Locate the other ESM canister in the affected drive tray (this is the canister on the non-working channel).

5

Replace the ESM canister on the non-working channel using the following steps:

6

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area.

7

You must replace the drive. Which procedure you use depends on the RAID level of the volume group associated with the affected drive. To determine the associated volume group, highlight the affected drive in the Physical View of the Array Management Window and select View >> Associated Elements. Next highlight the associated volume group in the Logical View of the Array Management Window.

1

Stop all I/O to the affected volumes.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Back up all data on the affected volumes. (Step 7 will destroy all data on the affected volumes.)

Note: To the operating system (OS), a failed volume is the same as a failed non-RAID drive. Refer to the OS documentation for requirements concerning failed drives and apply them where necessary.

5

If any of the affected volumes are also source or target volumes in a copy operation that is either Pending or In Progress, you must stop the copy operation before continuing.

Go to the Copy Manager by selecting Volume >> Copy >> Copy Manager, then highlight each copy pair that contains an affected volume and select Copy >> Stop.

6

If you have snapshot volumes associated with the affected volumes, these snapshot volumes will no longer be valid once you fail the drive in step 8.

If necessary, perform any operations on the snapshot volumes and then delete them.

7

Caution: Possible loss of data accessibility. Transitioning volumes to failed may cause the loss of accessibility to data on the volumes. Make sure that you back up all data on the affected volumes before starting this step.

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The affected volumes become Failed .

8

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

9

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

Note: Wait until the replaced drive is ready (its fault indicator light must be off) before attempting to initialize the volumes in step 10.

10

Highlight the volume group associated with the replaced drive in the Logical View of the Array Management Window and select Advanced >> Recovery >> Initialize >> Volume Group.

• The volumes in the volume group are initialized, one at a time.
• To monitor initialization progress for a volume, highlight the volume in the Logical View of the Array Management Window and select Volume >> Properties. Note that when the initialization is completed, the progress bar is no longer displayed.
• When initialization is completed, all volumes in the volume group are Optimal .

Important: Make sure you save this procedure by selecting Save As. Once you fix the failure, you will not be able to access the information from Recovery Guru.

11

1

You should stop all I/O to all volumes in the volume group associated with the affected drive to reduce the possibility of data loss. If another drive fails in this volume group while you are performing this procedure, you will lose data.

2

Reseating the drive may clear up the path redundancy problem. Remove the drive and then re-insert it.

Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not failed. In this situation, it is acceptable to remove the battery even though the Service Action Allowed is NO.

3

Wait 40 seconds, and then click the Recheck button to rerun the Recovery Guru to ensure that the problem has been fixed.

4

Although not required, you should back up all data on all volumes associated with the affected drive.

5

Highlight the affected drive in the Physical View of the Array Management Window and select Advanced >> Recovery >> Fail Drive. The associated volumes become Degraded .

6

Remove the failed drive (its fault indicator light should be on).

Note: Make sure the replacement drive has a capacity equal to or greater than the failed drive.

7

Wait 30 seconds, then insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).

8