Unsupported SATA Protocol Connection
The causes and resolutions refer to the Dell Modular Disk Storage Manager recovery guru. Launch Dell Modular Disk Storage Manager to diagnose and fix the recovery failure as follows:
Open Start >> Programs >> Dell >> MD Storage Manager >> Modular Disk Storage Manager Client.
If the MD Storage Array is already being managed by MDSM, you can proceed with the Causes and Resolution sections.
From Edit -> Add Storage Array, provide the IP address of the MD Storage Array and Add it to the discovered devices configuration in order to manage it.
Select the MD Storage Array and follow the steps specified in this recovery guru.
The RAID controller module is reporting an unsupported SATA protocol connection. This is likely due to a SATA physical disk being connected to a SAS connection without a SAS to SATA interposer. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Possible loss of data accessibility. Do not remove a component when either (1) the Service Action (removal) Allowed (SAA) field in the Details area of this recovery procedure is NO, or (2) the SAA LED on the affected component is OFF (note that some products do not have SAA LEDs). Removing a component while its SAA LED is OFF may result in temporary loss of access to your data. Refer to the following Important Notes for more detail. Caution: Electrostatic 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
It is recommended that the affected physical disk be replaced immediately.
No data has been lost.
You can replace the physical disk while the storage array is receiving I/O.
Service Action Allowed Important Information:
The Service Action (removal) Allowed field in the Details area indicates whether or not you can safely remove the component. If the SAA field is NO, then the affected component must remain in place until you service another component first.
The Service action LED on Component field in the Details area indicates whether or not a physical SAA LED is present on the hardware component. This field does NOT indicate whether the LED is ON or OFF (that indication is provided by the Service action (removal) allowed field).
If a component does not have an SAA LED, then it is OK to remove the component when its fault LED is lit and the Service Action (removal) Allowed field = YES in the Details area.
The Service Action (removal) Allowed field shown in the Details area and the physical SAA LED on the hardware component (if supported) MUST match before you remove the affected component. In rare cases (such as multiple problems), the status of the LED and the SAA field may not match. If there is a mismatch, then you should NOT remove the component until these indications match.
1 | Check the Component Requiring Service field in the Details area to determine which physical disk needs to be replaced. |
2 | Remove the physical disk (the fault indicator light on the affected physical disk canister should be lit). |
3 | Replace the current physical disk with one that contains a SAS to SATA interposer. |
3 | Insert the new physical disk. Its fault indicator light may be lit for a short time (one minute or less). |
4 | Click the Recheck button 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 | Microsoft.SystemCenter.ManagementServer | ||
| Category | Alert | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Warning | ||
| Alert Priority | Normal | ||
| Remotable | True | ||
| Alert Message |
|
| ID | Module Type | TypeId | RunAs |
|---|---|---|---|
| DS | DataSource | Microsoft.Windows.ScriptGenerated.EventProvider | Default |
| Alert | WriteAction | System.Health.GenerateAlert | Default |
| WriteToDW | WriteAction | Microsoft.SystemCenter.DataWarehouse.PublishEventData | Default |
Home
<Rule ID="Dell.MDStorageArray.ABBXMLEvent379" Enabled="onEssentialMonitoring" Target="SystemCenter!Microsoft.SystemCenter.ManagementServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.ScriptGenerated.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<ScriptName>RBODEventGenerator</ScriptName>
<EventNumber>379</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent379.StringResource"]$</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>