Drive path redundancy loss
A communication path with a drive has been lost.
Correct this failure as soon as possible. If the drive's other port or any other component fails on the working channel, the drive will be failed. The Details area reports the affected shelf, drive, volumes, and the working channel over which it can communicate with the drive.
The fault indicator light on the affected drive will be off because the drive has not failed.
If instructed to fail and replace a drive, ensure the replacement drive has a capacity equal to or greater than the failed drive.
If instructed to replace a controller or an IOM canister, contact your Technical Support Engineer if you do not have a replacement controller or IOM canister available.
The NV status LED on the controller will stay lit until all cached data has been written to the storage array's drives. Removing the controller before the NV status LED has turned off will result in data loss.
The data on the affected volumes will be lost once you perform the next step. Be sure you have backed up your data before going to step 19.
Do not disconnect any cables on the working channel. Doing so may cause a possible loss of data accessibility.
Always use proper anti-static protection when handling components. Touching components without using a grounding wrist strap may damage the equipment.
Recovery Steps
Fix any other problems reported by the Recovery Guru before attempting to fix this problem.
Create a back-up of the storage array's configuration data on your local system using the Command Line Interface.
From a command prompt run the save storageArray dbmDatabase command using the sourceLocation=onboard and contentType=all options.
Command Prompt example: (exact syntax will be dependent on your operating system)SMcli (hostname or IP address) -c "save storageArray dbmDatabase sourceLocation=onboard contentType=all
file= \"dbmDatabase.zip\" ;"Help with E-Series CLI commands is available from the online Document Center or by contacting Technical Support.
Is the affected shelf listed in the Details area a controller shelf or a drive shelf?
If the affected shelf is a controller shelf, go to step 11.
If the affected shelf is a drive shelf, go to step 4.
To determine the non-working channel, start at the expansion port on the controller shelf corresponding to the working channel (refer to the labels on the back of the controller shelf if needed). Trace the cable from the working channel to the IOM canister in the affected drive shelf reported in the Details area.
Locate the other IOM canister in the affected drive shelf (this is the canister on the non-working channel).
You need to replace the IOM canister. Contact your Technical Support Engineer if you do not have a replacement IOM canister.
Does your storage array have one or two controllers?
If the storage array has one controller, go to step 8.
If the storage array has two controllers, go to step 9.
Perform the following steps to replace the IOM canister on the non-working channel.
Label the cables to the IOM canister on the non-working channel. The labels will help you correctly reconnect the cables to the new IOM canister.
Stop I/O from all hosts connected to the storage array and wait at least five minutes to ensure that any data in the controller's cache is written to the storage array's drives.
Select the Save icon in the Recovery Guru to save the remaining steps to a file. These steps will no longer be accessible after you complete step d.
Turn off power to all power-fan canisters in the controller shelf.
Remove the IOM canister.
Set all switches on the new IOM canister to the same values as the old IOM canister.
Insert the new IOM canister into the drive shelf.
Using the labels created in step a, reconnect the cables to the replaced canister.
Wait one minute.
Turn on power to all power-fan canisters in the controller shelf. Wait until all drives have completed the spin-up process, then go to step 10.
Perform the following steps to replace the IOM canister on the non-working channel.
Label the cables to the IOM canister on the non-working channel. The labels will help you correctly reconnect the cables to the new IOM canister.
Remove the IOM canister.
Set all switches on the new IOM canister to the same values as the old IOM canister.
Insert the new IOM canister into the drive shelf.
Using the labels created in step a, reconnect the cables to the replaced canister.
Wait one minute.
Select Recheck to ensure the problem has been resolved. If the problem is not resolved, go to step 11.
Stop all I/O to all volumes in volume groups or disk pools associated with the affected drive. If another drive fails in the volume group or disk pool while you are performing this procedure, you will lose data.
Reseating the drive may clear up the path redundancy problem.
Remove the drive and then re-insert it.
Wait one minute.
Select Recheck to ensure the problem has been resolved. If the problem is not resolved, go to step 14.
You must replace the drive. The procedure you use depends on the RAID level of the volume group associated with the affected drive. Is the RAID level listed in the Details area RAID 0?
If yes, ensure all of the volumes in the table are Optimal, and then go to step 15.
If no, go to step 24.
Cancel any volume copy operations that include affected volumes listed in the Details area.
Go to Home.
Select the Show operations in progress link.
Search the table for volume copy operations that include an affected volume. If a volume copy operation is found, select Stop to cancel the volume copy operation.
Repeat step c until all volume copy operations including all affected volumes have been stopped.
Delete any snapshot volumes associated with the affected volumes in the Details area. The snapshot volumes will no longer be valid after you fail the drive in step 19.
Go to . Then, select the Snapshot Volumes tab.
Search for affected volumes in the table using the Name column. If the volumes are listed in the table they are snapshot volumes, otherwise they are not.
If a snapshot volume is found that is associated with an affected volume, select to delete the snapshot volume.
Repeat step c until all snapshot volumes associated with affected volumes have been deleted.
Select the Save icon in the Recovery Guru to save the remaining steps to a file. These steps will no longer be accessible after you complete step 19.
Back up all data on the affected volumes listed in the Details area.
Physically replace the affected drive.
Go to Hardware.
Highlight the drive listed in the Details area.
Select Fail to fail the drive, making sure to unselect Copy contents of drive before failing.
Remove the failed drive (its fault indicator light should be on).
Wait 30 seconds.
Insert the new drive. Its fault indicator light may be lit for a short time (one minute or less).
Initialize all of the affected volumes.
Go to .
Select Initialize volumes under More to initialize all of the volumes shown in the Details area.
Wait until all of the volume initialization operations have completed.
The volume initialization operations' progress can be viewed by going to Home and selecting View operations in progress.
Add the affected volumes back to the operating system, and restore the affected volumes' data from backup. You may need to reboot the system to see the re-initialized volumes.
Select Recheck to ensure the problem has been resolved. If the problem is not resolved, a problem has occured on the controller and it needs to be replaced. Go to step 27.
Although not required, you should backup all data on all volumes associated with the affected drive.
Follow the steps to fail the drive.
Go to Hardware.
Highlight the affected drive.
Select Fail from the drive's menu options.
Wait 30 seconds and then insert a new drive. Its fault indicator light may be lit for a short time (one minute or less).
Select Recheck to ensure the problem has been resolved. If the problem is not resolved, a problem has occured on the controller and it needs to be replaced. Go to step 27.
Does your storage array have one or two controllers?
If the storage array has one controller, go to step 28.
If the storage array has two controllers, go to step 36.
Stop I/O from all hosts connected to the storage array and wait at least five minutes to ensure that any data in the controller's cache is written to the storage array's drives.
Select the Save icon in the Recovery Guru to save the remaining steps to a file. These steps will no longer be accessible after you complete step 30.
Turn off power to all power-fan canisters in the controller shelf.
Label each cable connected to the controller canister.
Remove the controller.
Remove the battery from the removed controller and place it into the new controller. Refer to your hardware documentation for the battery replacement procedure.
Wait one minute, and then insert the new controller firmly into place and reconnect the cables.
Turn on power to all power-fan canisters in the controller shelf. Wait until all drives have completed the spin-up process, and then go to step 43.
Are any hosts connected to this storage array NOT running a host-based, multi-path failover driver?
If yes, stop I/O from those hosts to the storage array, and then go to step 37.
If no, go to step 37.
Select the Save icon in the Recovery Guru to save the remaining steps to a file. These steps will no longer be accessible after you complete step 38.
Manually place the affected controller offline.
Go to Hardware.
Highlight the controller shown in the Details area. The controller is located on the backside of the controller shelf.
Select Place Offline.
Select Recheck to rerun the Recovery Guru. The original Drive Path Redundancy Loss problem should now be replaced by an Offline Controller problem.
Follow the recovery steps in the Offline Controller procedure until you have removed the controller.
Remove the battery from the removed controller and place it into the new controller. Refer to your hardware documentation for the battery replacement procedure.
Wait one minute, and then insert the new controller firmly into place and reconnect the cables.
Select Recheck to ensure the problem has been resolved.