R/Evolution 2000 Series, Руководство по устранению неисправностей

Страница: 69 / 130

Chapter 5 Troubleshooting Using Event Logs 69
For example:
Reviewing Event Logs
When reviewing events, do the following:
1. Review the critical/warning events.
Identify the primary events and any that might be the cause of the primary event.
For example, an over temperature event could cause a drive failure.
2. Review the event log for the controller that reported the critical/warning event by
viewing the event log by controller. Locate the critical/warning events in the
sequence.
Repeat this step for the other controller if necessary.
3. Review the events that occurred before and after the primary event.
During this review you are looking for any events that might indicate the cause of
the critical/warning event. You are also looking for events that resulted from the
critical/warning event, known as secondary events.
4. Review the events following the primary and secondary events.
You are looking for any actions that might have already been taken to resolve the
problems reported by the events.
Event SN
A29856
A29809
Date/Time
08-06 09:35:07
08-04 12:12:05
Code
33
65
Severity
I
C
Controller
A
A
Description
Time/date has been changed
Uncorrectable ECC error in
buffer memory address 0x0 on
bootup