A drive has a
DACStore that is unrecognizable because it was written by an earlier
version of the firmware.
What Caused the Problem?
A drive is incompatible for use in this storage array because it contains an older configuration database than what is supported by the storage array. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Electronic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.
Important Notes
This problem usually results from importing a drive from a storage array that is running a lower (older) version of firmware into a storage array running a higher (newer) version of firmware.
This drive can still be used in this storage array ONLY under the following conditions:
If you need to import the data into this storage array, you must upgrade the configuration database on the drive first. This must be done by reinserting the drive back into the source storage array and upgrading to the appropriate firmware.
If you do NOT need the data on the drive, you can initialize it in order to place the correct configuration database on the drive. However, this will erase all volume configuration information and data.
In order to keep the information that resides on this drive, you must reinsert it back into the original storage array.
You can replace the drive while the storage array is receiving I/O.
Recovery Steps
1 |
| ||||||||||||||||||||||
2 | Upgrade the configuration database on the drives by completing the following steps:
| ||||||||||||||||||||||
3 | Click Recheck 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. |
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_0205_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_DRIVE_INCOMPATIBLE_DOWNREV_DACSTORE_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.StateId7D97F928CCA7F30D9ABE71DDE2FC7E40" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId67C180DB2597334F76CF3A7B71CD4360" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>205</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>