Compaq DL580R01 Service Guide - Page 103

Table 3-18, Array Diagnostic Utility ADU Error Messages, Message, Description, Recommended Action

Get Compaq DL580R01 - ProLiant - 512 MB RAM PDF manuals and user guides
UPC - 720591221416
View all Compaq DL580R01 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 103 highlights

3-34 Compaq ProLiant DL580 Server Maintenance and Service Guide Table 3-18 Array Diagnostic Utility (ADU) Error Messages Message Accelerator board not detected Accelerator error log Accelerator parity read errors: X Accelerator parity write errors: X Accelerator status: Cache was automatically configured during last controller reset Accelerator status: Data in the cache was lost due to some reason other than the battery being discharged. Accelerator status: Dirty data detected has reached limit. Cache still enabled, but writes no longer being posted. Description Array controller did not detect a configured array accelerator board. List of the last 32 parity errors on transfers to or from memory on the array accelerator board. Displays starting memory address, transfer count, and operation (read and write). Number of times that read memory parity errors were detected during transfers from memory on array accelerator board. Number of times that write memory parity errors were detected during transfers to memory on the array accelerator board. Can occur when cache board is replaced with one of a different size. Data in cache was lost, but not because of the battery being discharged. The number of cache lines containing dirty data that cannot be flushed (written) to the drives has reached a preset limit. The cache is still enabled, but writes are no longer being posted. This problem usually occurs when there is a problem with the drive or drives. Recommended Action Install array accelerator board on array controller. If an array accelerator board is installed, check for proper seating on the array controller board. If there are many parity errors, the array accelerator board may need to be replaced. If there are many parity errors, the array accelerator board may need to be replaced. If there are many parity errors, the array accelerator board may need to be replaced. Normal operations should continue. Check to be sure that the array accelerator is properly seated. If the error continues, the array accelerator may need to be replaced. Resolve the problem with the drive or drives, and then the controller can write the dirty data to the drives. Posted-writes operations are restored. continued

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
3-34
Compaq ProLiant DL580 Server Maintenance and Service Guide
Table 3-18
Array Diagnostic Utility (ADU) Error Messages
Message
Description
Recommended Action
Accelerator board
not detected
Array controller did not detect a
configured array accelerator board.
Install array accelerator board on array controller.
If an array accelerator board is installed, check
for proper seating on the array controller board.
Accelerator error log
List of the last 32 parity errors on
transfers to or from memory on the
array accelerator board. Displays
starting memory address, transfer
count, and operation (read and
write).
If there are many parity errors, the array
accelerator board may need to be replaced.
Accelerator parity
read errors:
X
Number of times that read memory
parity errors were detected during
transfers from memory on array
accelerator board.
If there are many parity errors, the array
accelerator board may need to be replaced.
Accelerator parity
write errors:
X
Number of times that write memory
parity errors were detected during
transfers to memory on the array
accelerator board.
If there are many parity errors, the array
accelerator board may need to be replaced.
Accelerator status:
Cache was
automatically
configured during
last controller reset
Can occur when cache board is
replaced with one of a different
size.
Normal operations should continue.
Accelerator status:
Data in the cache
was lost due to
some reason other
than the battery
being discharged.
Data in cache was lost, but not
because of the battery being
discharged.
Check to be sure that the array accelerator is
properly seated. If the error continues, the array
accelerator may need to be replaced.
Accelerator status:
Dirty data detected
has reached limit.
Cache still enabled,
but writes no longer
being posted.
The number of cache lines
containing dirty data that cannot be
flushed (written) to the drives has
reached a preset limit. The cache is
still enabled, but writes are no
longer being posted. This problem
usually occurs when there is a
problem with the drive or drives.
Resolve the problem with the drive or drives, and
then the controller can write the dirty data to the
drives. Posted-writes operations are restored.
continued