The copy then fail operation is waiting for additional capacity in the disk pool.
What Caused the Problem?
A drive is reporting internal errors that could cause the drive to fail. SANtricity has attempted to automatically copy the drive's contents as a safety precaution, but was unable to as there is either not enough free capacity in the disk pool or removing the drive would cause the disk pool to contain less than the minimum of 11 drives. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Risk of Data Loss. If a "Degraded Volume" problem is also displayed in the Recovery Guru Summary area, always fix the "Degraded Volume" problem first. Fixing the "Impending Drive Failure" problem before fixing a "Degraded Volume" may result in data loss.
Caution: Electrostatic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching the components without using a proper ground may damage the equipment.
Important Notes
If the drive fails, you may lose redundancy.
Because the drive has not failed, its fault indicator light will not be turned on.
You can replace the drive while the volumes associated to the affected drive are receiving I/O.
Whenever possible it is recommended to copy the drive's contents to its disk pool before failing the drive, as it greatly reduces the possibility of data loss.
Recovery Steps
Check the number of drives contained in the drive's disk pool by selecting the disk pool in the Storage and Copy Services tab of the Array Management Window.
If... | Then... |
The drive's disk pool contains 11 drives. | Go to Procedure for disk pool containing 11 drives . |
The drive's disk pool contains 12 or more drives. | Go to Procedure for disk pool containing 12 or more drives . |
Procedure for disk pool containing 11 drives
SANtricity is unable to automatically copy the affected drive as the drive's disk pool does not contain at least 12 drives. You can resolve this problem in several ways:
Add one or more drives to the disk pool.(recommended)
Physically replace the drive before it fails.
Take no further action and replace the drive once it fails.
If... | Then... |
You want to add drives to the disk pool. (recommended) | Perform the following steps:
|
You want to physically replace the drive before it fails. | Perform the following steps:
|
You want to take no further action and wait for the affected drive to fail. | You can then complete the recovery steps to fix the "Failed Disk Pool Drive" problem when it is reported. You need to do nothing more in this procedure. |
Procedure for disk pool containing 12 or more drives
SANtricity is unable to automatically copy the affected drive as there is not enough usable capacity in the drive's disk pool. You can resolve this problem in several ways (or through a combination of these):
Replace any failed drives in the disk pool.(recommended)
Add drives to expand the usable capacity of the disk pool.
Delete any unneeded volumes in the disk pool to free up capacity.
Physically replace the drive before it fails.
Take no further action and replace the drive once it fails.
If... | Then... |
You want to replace any failed drives in the disk pool.(recommended) | Select the failed disk pool drive procedure from the Recovery Guru Summary area and use the associated recovery steps to fix the failed drive. Repeat the recovery steps for all of the drives you want to replace. Note: SANtricity will begin copying the drive to the disk pool once the newly replaced drive has finished reconstructing. |
You want to expand the usable capacity of the disk pool by adding drives. | Perform the following steps:
|
You want to physically replace the drive before it fails. | Perform the following steps:
|
You want to take no further action and wait for the affected drive to fail. | You can then complete the recovery steps to fix the "Failed Disk Pool Drive" problem when it is reported. You need to do nothing more in this procedure. |
Target | NetAppESeries.StorageArray | ||
Parent Monitor | NetAppESeries.StorageArrayAvailability | ||
Category | Custom | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | NetAppESeries.FailureUnitMonitorType | ||
Remotable | True | ||
Accessibility | Internal | ||
Alert Message |
| ||
RunAs | Default | ||
Comment | Machine generated entity |
<UnitMonitor ID="NetAppESeries.FailureID_0457_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppESeries.StorageArray" ParentMonitorID="NetAppESeries.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppESeries.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppESeries.REC_COPY_THEN_FAIL_WAITING_ON_DDP_CAPACITY_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="NetAppESeries.StateId46E48695B4D5523CCC56022D2A07DBA6" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateIdDCFD010DC70AC2293CA82E217359A3C2" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>457</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>