Users Guide

Table 12. Windows Event Message mapped under LC logs monitored under S2D event
correlation (continued)
Windows Event Source - SourceID Windows Event Message Mapped on iDRAC LC Log
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 Majority of the pool drives hosting space
meta-data for storage space %1 failed a
space meta-data update, which caused
the storage pool to go in 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 allocate more
storage for, the storage space %1 has
failed. This is because there was a write
failure 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. iDRAC Service Module will replicate these
alerts into the Lifecycle controller logs in iDRAC with PPID as "NA".
Storage Spaces Direct (S2D) logs collection with SupportAssist Collection
Starting iSM 3.5.1, SupportAssist Collection (SAC) request will collect and package Storage Spaces Direct logs. This feature is
available only on Microsoft windows OS. The SDS Event Correlation feature should be enabled for SAC to include this log
collection report.
S.M.A.R.T logs for disks and Chipset into SupportAssist Collection (SAC)
report
iSM collects the data from the SATA chipset when the SAC is requested in real-time. S.M.A.R.T logs are not stored in iSM. If
iSM is not installed or connected, iDRAC cannot send the previously stored S.M.A.R.T logs to ensure that the configuration
matches.
This feature requires the S.M.A.R.T monitoring feature to be enabled in iSM, and Storage Logs under SupportAssist
Collection preferences is enabled in iDRAC.
36
iDRAC Service Module monitoring features