No compatible spares are available to reconstruct this vdisk if it experiences a disk failure.
Warning Event 484.
No compatible spares are available to reconstruct this vdisk if it experiences a disk failure. Only vdisks that have dedicated spares will start reconstruction automatically.
This situation puts data at increased risk because it will require user action to configure a disk as a dedicated or global spare before reconstruction can begin on the indicated vdisk if a disk in that vdisk fails in the future.
If the last global spare has been deleted or used for reconstruction, all vdisks that do not have at least one dedicated spare are at increased risk. Note that even though there may be global spares still available, they cannot be used for reconstruction of a vdisk if that vdisk uses larger-capacity disks or a different type of disk; so this event may be logged even when there are unused global spares. If the dynamic spares feature is enabled, this event will be logged even if there is an available disk that may be used for reconstruction.
Configure disks as dedicated spares or global spares.
For a dedicated spare, the disk must be of the same type as the other disks in the vdisk and at least as large and should have the same or better performance.
For a global spare, it is best to choose a disk that is as big as or bigger than the largest disk of its type in the system and of equal or greater performance. If the system contains a mix of disk types (SATA, SAS, SSD, for example), there should be at least one global spare of each type (unless dedicated spares are used to protect every vdisk of a given type).
| Target | MSA.System | ||
| Category | Alert | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Warning | ||
| Alert Priority | Low | ||
| Remotable | False | ||
| Alert Message |
|
| ID | Module Type | TypeId | RunAs |
|---|---|---|---|
| Event | DataSource | MSA.DataSource.Event.System | Default |
| EventFilter | ConditionDetection | MSA.ConditionDetection.Filter.Event | Default |
| Alert | WriteAction | System.Health.GenerateAlert | Default |
Home<Rule ID="MSA.Rule.Event.System.Warning.484" Enabled="true" Target="MSA.System" ConfirmDelivery="true" Remotable="false" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="Event" TypeID="MSA.DataSource.Event.System"/>
</DataSources>
<ConditionDetection ID="EventFilter" TypeID="MSA.ConditionDetection.Filter.Event">
<EventCode>484</EventCode>
<SeverityNumeric>2</SeverityNumeric>
</ConditionDetection>
<WriteActions>
<WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">
<Priority>0</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="AlertMessageIDcbcc178a644a4660b84acd2a177f528d"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Target/Property[Type="System!System.Entity"]/DisplayName$</AlertParameter1>
<AlertParameter2>$Target/Property[Type="MSA.System"]/PrimaryIP$</AlertParameter2>
<AlertParameter3>$Target/Property[Type="MSA.System"]/SecondaryIP$</AlertParameter3>
<AlertParameter4>$Data/Property[@Name='severity']$</AlertParameter4>
<AlertParameter5>$Data/Property[@Name='message']$</AlertParameter5>
</AlertParameters>
</WriteAction>
</WriteActions>
</Rule>