Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell EMC iDRAC Service Module 3.6 User’s Guide

PDF

Correlation of software events to hardware failures for Microsoft SDS

The event log files for hardware storage pool alerts or events are monitored by iSM with the server storage correlation feature. The server storage subsystem is monitored when Dell EMC storage controllers are used in RAID mode. But in Storage Spaces (SS) or Storage Space Direct (S2D), the server storage subsystem is monitored in a passthru mode, or the SATA chipset is used to create the storage pool. With this feature, hardware-defined alerts that are covered by the Lifecycle Controller (LC) log and software-defined alerts that are covered by operating system log files are merged, and the alerts are registered in the iDRAC Lifecycle log files.

This feature is installed with the iSM package and will be enabled by default. You can change the preferences in the iDRAC settings. As part of the monitoring, iSM will audit the log files for potential failures and warnings. iSM will embed the SS correlation events on the host to an equivalent Lifecycle Controller event. The SSLCMAP should only reach the Lifecycle log files and SupportAssist alert. You cannot configure the SSLCMAP to any other alert destination in iDRAC .

The following are the prerequisites for S2D log collection:
  • The SS event correlation feature must be enabled in the service module page in the iDRAC UI.
  • The PII filter must be disabled in the service module page in the iDRAC UI.
Table 1. Windows Event Message mapped under LC logs monitored under S2D event correlationThe following table describes the Windows Event Message that is mapped under LC logs monitored under S2D event correlation:
Windows event source—SourceID Windows event message Mapped on iDRAC LC log
StorageSpaces—drivers—100 Physical drive %1 failed to read the configuration or returned corrupt data for storage pool %2. As a result the in-memory configuration might not be the most recent copy of configuration. Return code: %3

MessageID : SDS0001

StorageSpaces—drivers—102 Most of the physical drives of storage pool %1 failed a configuration update, which caused the pool to go into a failed state. Return code: %2

MessageID : SDS0002

StorageSpaces—drivers—103 The capacity consumption of the storage pool %1 has exceeded the threshold limit set on the pool. Return code: %2

MessageID : SDS0003

StorageSpaces—drivers—200 Windows was unable to read the drive header for physical drive %1. If you know that the drive is still usable, then resetting the drive health by using command line or UI may clear this failure condition and enable you to reassign the drive to its storage pool. Return code: %2

MessageID : SDS0004

StorageSpaces—drivers—203 An I/O failure has occurred on physical drive %1. Return code: %2

MessageID : SDS0005

StorageSpaces—drivers—300 Physical drive %1 failed to read the configuration or returned corrupt data for storage space %2. As a result the in-memory configuration may not be the most recent copy of configuration. Return code: %3

MessageID : SDS0006

StorageSpaces—drivers—301 All pool drives failed to read the configuration or returned corrupt data for storage space %1. As a result the storage space will not attach. Return code: %2

MessageID : SDS0007

StorageSpaces—drivers—302 Most of the pool drives hosting space metadata for storage space %1 failed a space metadata update, which caused the storage pool to go to failed state. Return code: %2

MessageID : SDS0008

StorageSpaces—drivers—303 Drives hosting data for storage space have failed or are missing. As a result, no copy of data is available. Return code: %2

MessageID : SDS0009

StorageSpaces—drivers—304 One or more drives hosting data for storage space %1 have failed or are missing. As a result, at least one copy of data is not available. However, at least one copy of data is still available. Return code: %2

MessageID : SDS0010

StorageSpaces—drivers—306 The attempt to map, or to allocate more storage for, the storage space %1 has failed. This is because there was a write failure that is involved in the updating the storage space metadata. Return code: %2

MessageID : SDS0011

StorageSpaces—drivers—307 The attempt to unmap or trim the storage space %1 has failed. Return code: %2

MessageID : SDS0012

NOTE The Event and Error Message Reference Guide provides information about the event and error information that is generated by firmware and other agents that monitor system components.
NOTE PPID field is not recorded for alerts corresponding to a storage pool. iSM will replicate these alerts into the Lifecycle Controller log files in iDRAC with PPID as "NA."

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\