| Event ID | Event Source | Description | More Info |
|---|---|---|---|
| 2359 | Server Administrator | The physical disk is not certified. | Cause : The physical disk does not comply with the standards set by Dell and is not supported. Resolution : Replace the physical disk with a physical disk that is supported. |
| 1007 | Microsoft-Windows-Resource-Exhaustion-Detector | The Windows Resource Exhaustion Detector experienced a memory allocation failure. | |
| 2048 | Server Administrator | Device failed. | Cause : A storage component such as a physical disk or an enclosure has failed. The failed component may have been identified by the controller while performing a task such as a rescan or a check consistency. Resolution : Replace the failed component. You can identify which disk has failed by locating the disk that has a red “X†for its status. Perform a rescan after replacing the disk. |
| 2049 | Server Administrator | Physical disk removed. | Cause : A physical disk has been removed from the disk group. This alert can also be caused by loose or defective cables or by problems with the enclosure. Resolution : If a physical disk was removed from the disk group, either replace the disk or restore the original disk. On some controllers,a removed disk has a red "X" for its status. On other controllers, a removed disk may have an Offline status or is not displayed on the user interface. Perform a rescan after replacing or restoring the disk. If a disk has not been removed from the disk group, then check for problems with the cables. |
| 2123 | Server Administrator | Redundancy lost | Cause : A virtual disk or an enclosure has lost data redundancy. In the case of a virtual disk, one or more physical disks included in the virtual disk have failed.Due to the failed physical disk or disks, the virtual disk is no longer maintaining redundant (mirrored or parity) data.The failure of an additional physical disk will result in lost data. In the case of an enclosure, more than one enclosure component has failed. For example, the enclosure may have suffered the loss of all fans or all power supplies. Resolution : Identify and replace the failed components. To identify the failed component, select the Storage object and click the Health subtab. The controller status displayed on the Health subtab indicates whether a controller has a failed or degraded component. Click the controller that displays a Warning or Failed status. This action displays the controller Health subtab which displays the status of the individual controller components. Continue clicking the components with a Warning or Health status until you identify the failed component. |
| 2057 | Server Administrator | Virtual disk degraded. | Cause 1: This event is logged when a physical disk included in a redundant virtual disk fails. Because the virtual disk is redundant (uses mirrored or parity information) and only one physical disk has failed, the virtual disk can be rebuilt. Resolution 1: Configure a hot spare for the virtual disk if one is not already configured. Rebuild the virtual disk. When using an Expandable RAID Controller (PERC) PERC 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di,CERC ATA100/4ch, PERC 5/E, PERC 5/i or a Serial Attache SCSI (SAS) 5/iR. Cause 2: Cause 2: A physical disk in the disk group has been removed. Resolution 2: If a physical disk was removed from the disk group, either replace the disk or restore the original disk. You can identify which disk has been removed by locating the disk that has a red “X†for its status. Perform a rescan after replacing the disk. |
| 2052 | Server Administrator | Physical disk inserted. | Cause: This event is logged when Physical disk was inserted . Resolution : This is an informational event. |
| 2121 | Server Administrator | Device returned to normal | Cause : This alert is for informational purposes. A device that was previously in an error state has returned to a normal state. For example, if an enclosure became too hot and subsequently cooled down, then you may receive this alert. |
| 2065 | Server Administrator | Physical disk rebuild started. | Cause : This event is logged when Physical disk rebuild started. Resolution : This is an information event. |
| 21 | Microsoft-Windows-WindowsUpdateClient | Reboot required: To complete the installation of the following updates, the computer must be restarted. Until this computer has been restarted, Windows cannot search for or download new updates: %1 | According to Microsoft : Cause This event is logged when to complete the installation of the following updates, the computer must be restarted. Resolution Restart the system If updates are available but are not automatically downloaded, restart the system. Verify To confirm Windows Update Agent has installed updates: 1.Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. 2.At the command prompt, type eventvwr.msc and press ENTER to open Event Viewer. 3.To check for events in Event Viewer: a.In the left panel of Event Viewer, click Application and Service Logs. b.Expand Microsoft, and then expand Windows. c.Click WindowsUpdateClient, and then click Operational. d.Check to see if Event ID 19 is present in the event list to confirm that Windows Update Agent has successfully downloaded the updates. |
| 6008 | User32 | The previous system shutdown at %1 on %2 was unexpected. | According to Microsoft : Cause : This event is written during startup following an unexpected restart or shutdown. An unexpected restart or shutdown is one that the system cannot anticipate, such as when the user pushes the computer's reset button or unplugs the power cord. If the Persistent Time Stamp group policy setting is either enabled or not configured, system information is written to the data section of this event. This information includes a timestamp that indicates the computer's uptime in seconds before the unexpected shutdown occurred. Resolution: One or more of the following options might help to determine the cause of the unexpected shutdown: 1.Check the system event log for other events that occurred around the same time as the unexpected shutdown. 2.Find out whether the computer's reset button was pressed, the power cord was unplugged, or a general power failure occurred. |