Dell iDRAC Service Module 5.0.1.0 User’s Guide
Software RAID alert monitoring
The software RAID feature on iSM enables alert monitoring in PERC S130 and later series of software RAID controllers, starting from iSM version 4.3.0.0. iSM supports the software RAID alert monitoring on Microsoft Windows operating system with software RAID configurations and logs the software RAID alerts in the Lifecycle log and operating system log.
iSM monitors the alerts when OMSA is running on the operating system. However, the alerts are logged only in the Lifecycle log, and not in the operating system log. When OMSA is not running on the operating system, iSM logs the alerts in the operating system log and the Lifecycle log. The source name for alerts logged in the operating system log is iDRACServiceModule-SWRAID. iSM monitors the alerts every 30 minutes and a maximum of 50 alerts are logged per day.
NOTE When
Lifecycle Log Replication feature is enabled on iSM, the software RAID alerts are logged in the operating system with the source name
Lifecycle Controller Log.
The following table provides the list of software RAID alerts monitored in iSM.
| Event ID | Severity | Description |
|---|---|---|
| PDR12 | Critical | <Physical disk name> initialization has failed. |
| VDR5 | Informational | <Virtual disk name> was deleted. |
| VDR8 | Warning | <Virtual disk name> is degraded either because the physical disk drive in the drive group is removed or the physical disk drive added in a redundant virtual drive has failed. |
| VDR25 | Informational | <Virtual disk name> rebuild is completed. |
| VDR20 | Critical | <Virtual disk name> rebuild failed. |
| VDR24 | Informational | Reconfiguration of <Virtual disk name> has completed. |
| VDR19 | Critical | Reconfiguration of <Virtual disk name> has failed. |
| VDR21 | Informational | Consistency check for <Virtual disk name> has completed. |
| VDR16 | Critical | Consistency check of <Virtual disk name> failed. |
| VDR4 | Informational | <Virtual disk name> was created. |
| VDR7 | Critical | <Virtual disk name> has failed. |
| PDR14 | Informational | <Physical disk name> initialization is complete. |
| VDR28 | Informational | A virtual disk and its mirror have been split. |
| VDR44 | Informational | <Virtual disk name> disk cache policy has changed. |
| PDR8 | Informational | <Physical disk name> is inserted. |
| PDR5 | Warning | <Physical disk name> is removed. |
| PDR98 | Warning | Command timeout occurred on <Physical disk name>.<args>. |
| CTL122 | Critical | Unable to update the RAID controller <RAID controller> firmware version because of an issue during the update process (programming timeout error). |
| CTL7 | Warning | Bad block medium error on <Controller name>. |
| CTL5 | Warning | Bad block replacement error on <Controller name>. |
| CTL14 | Warning | Single-bit ECC error limit exceeded on the <Controller name> DIMM. |
| CTL77 | Informational | Flash of new firmware image completed on <Controller name>. |
| VDR111 | Storage | Corrected disk storage medium error on <Virtual disk name>. |
| PDR17 | Informational | Global hot spare assigned to <Physical disk name>. |
| PDR13 | Critical | <Physical disk name> rebuild has failed. |
| PDR62 | Critical | The rebuild failed due to errors on the target <Physical disk name>. |
| VDR13 | Informational | <Virtual disk name> rebuild has started. |
| VDR12 | Informational | Reconfiguration has started for <Virtual disk>. |
| VDR9 | Informational | <Virtual disk name> consistency check has started. |
| PDR27 | Informational | Dedicated hot spare assigned to <Physical disk name>. |
| PDR33 | Informational | A dedicated hot spare has been removed. <Physical disk name> |
| PDR47 | Critical | A block on <Physical disk name> was punctured by the controller. |
| PDR58 | Warning | <Physical disk name> is incompatible. |
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: <>()\