Physical Disk warning state alert
Physical Disk has generated warning alert. Probable causes and corresponding resolutions for this condition are:
Cause | Resolutions |
Insufficient space available on <physical disk> to perform a copyback operation. | Replace the physical disk with a larger physical disk, and then restart the copyback operation. |
<PD Name> is removed. |
|
<physical disk> is offline. | Force the physical disk online or assign a hotspare to the virtual disk. |
Predictive failure reported for <physical disk>. | Replace the physical disk. Even though the disk may not have failed yet, it is strongly recommended that the disk be replaced. Review other messages for additional information. |
The <physical device> is not supported. | If the physical device is supported, then update the firmware to a supported version. If the physical device is not supported, then replace the physical device with one that is supported. |
The dedicated hot spare <PD Name> is too small. | Assign a larger disk as the dedicated hot spare. |
Insufficient space on the global hot spare <PD Name>. | Assign a larger disk as the global hot spare. |
A redundant path is broken. | Make sure the cables are attached securely. See the Cables Attached Correctly section for more information on checking the cables. Make sure both Enclosure Management Modules (EMMs) are healthy. |
Insufficient space available on the <physical disk> to perform a rebuild. | Replace the physical disk with one of correct protocol (SAS, SATA) with at least the required size. Force rebuild if it does not start automatically. |
Bad block table on <physical disk> is 80% full. | Replace the disk generating this message. |
Rebuild not possible on physical disk <PD Name>. | Remove drive, insert correct protocol type, and force a rebuild as imposed for controller and system. |
Bad block table on <physical disk> is full. | Replace the disk. |
Command timeout occurred on <physical disk>.<args>. | Check the disk is present or replace the disk. |
The reason for the error can vary depending on the situation. The firmware error code is indicated in the message.. | Verify the health of attached devices. Review the Lifecycle log for significant events. Replace faulty hardware, if required. Make sure the cables are attached securely. Refer to the storage hardware documentation for more information on checking the cable connections. |
This message is generated after a copyback stops on a physical disk during a rebuild operation. | Wait for rebuild to finish, then copyback should resume. |
The PCIe solid state device identified in the message has either reached or exceeded the warranted wear-out limit. | Back up the data on the device, and contact your service provider for further instructions. |
<physical disk> copyback stopped for rebuild. | Wait for rebuild to finish, then copyback should resume. |
The <PCIe solid state device name> has reached <percent> of warranted device wear-out limit. | No response action is required. |
The <PCIe solid state device name> has reached or exceeded its warranted wear-out limit. | Back up the data on the device, and contact your service provider for further instructions. |
Predictive failure reported for <PCIe solid state device name> | Back up the data on the device, and contact your service provider for further instructions. |
Error occurred on <physical disk> : <error code>. | Verify the health of attached devices. Review the Lifecycle log for significant events. Replace faulty hardware, if required. Make sure the cables are attached securely. Refer to the storage hardware documentation for more information on checking the cable connections. |
Copyback stopped for hot spare <physical disk> . | No response action is required. |
Microcode update on <physical disk> has failed. | Retry the update. If the update fails a second time, verify the update package is valid. If the update package is valid, replace the failing disk. Contact technical support if the problem persists. |
Additional information on this issue may be available. Launch the iDRAC Console to debug further.
Target | Dell.ManagedServer | ||
Category | Alert | ||
Enabled | True | ||
Event_ID | 4346 | ||
Event Source | LifeCycle Controller Log | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
| ||
Event Log | System |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.EventProvider | Default |
Alert | WriteAction | System.Health.GenerateAlert | Default |
WriteToDW | WriteAction | Microsoft.SystemCenter.DataWarehouse.PublishEventData | Default |
<Rule ID="Dell.ManagedServer.Alert.4346" Enabled="true" Target="DellManagedServer!Dell.ManagedServer" ConfirmDelivery="false" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Property[Type="DellManagedServer!Dell.ManagedServer"]/HostName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">4346</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">LifeCycle Controller Log</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.ManagedServer.Alert.4346.Rule"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/EventDisplayNumber$</SuppressionValue>
<SuppressionValue>$Data/Channel$</SuppressionValue>
<SuppressionValue>$Data/PublisherName$</SuppressionValue>
<SuppressionValue>$Data/LoggingComputer$</SuppressionValue>
<SuppressionValue>$Data/EventCategory$</SuppressionValue>
<SuppressionValue>$Data/EventLevel$</SuppressionValue>
<SuppressionValue>$Data/UserName$</SuppressionValue>
<SuppressionValue>$Data/EventNumber$</SuppressionValue>
<SuppressionValue>$Data/EventDescription$</SuppressionValue>
</Suppression>
<Custom1/>
<Custom2/>
<Custom3/>
<Custom4/>
<Custom5/>
<Custom6/>
<Custom7/>
<Custom8/>
<Custom9/>
<Custom10/>
</WriteAction>
<WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>
</WriteActions>
</Rule>