Compaq ProLiant 8000 ProLiant 8000 Intel Pentium III Xeon 700MHz Servers Maint - Page 142

Table 3-16, ADU Diagnostic Messages, Message, Description, Recommended Action

Get Compaq ProLiant 8000 PDF manuals and user guides View all Compaq ProLiant 8000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 142 highlights

Diagnostics and Troubleshooting 3-45 Table 3-16 ADU Diagnostic 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 Accelerator status: Dirty data detected. Unable to write dirty data to drives 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. This can occur when cache board is replaced with one of a different size. Data in the 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 error usually occurs when there is a problem with the drive(s). At least one cache line contains dirty data that the controller has been unable to flush (write) to the drives. This problem usually occurs when there is a problem with the drive(s). Recommended Action Install the array accelerator board on the array controller. If an array accelerator board is already installed, check for proper seating on the array controller board. If there are many parity errors, you may need to replace the array accelerator board. If there are many parity errors, you may need to replace the array accelerator board. If there are many parity errors, you may need to replace the array accelerator board. Normal operations should continue. Ensure that the array accelerator is properly seated. If the error continues, you may need to replace the array accelerator. Resolve problem with drive(s). The controller will then be able to write dirty data to drives and posted write operations will be restored. Resolve the problem with the drive(s). The controller will then be able to write dirty data to drives. 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
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
Diagnostics and Troubleshooting
3-45
Table 3-16
ADU Diagnostic Messages
Message
Description
Recommended Action
Accelerator
board not
detected
Array controller did not detect a
configured array accelerator board.
Install the array accelerator board on the array
controller. If an array accelerator board is
already 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, you may need to
replace the array accelerator board.
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, you may need to
replace the array accelerator board.
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, you may need to
replace the array accelerator board.
Accelerator
status: Cache
was
automatically
configured
during last
controller reset.
This 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 the cache was lost, but not
because of the battery being
discharged.
Ensure that the array accelerator is properly
seated. If the error continues, you may need to
replace the array accelerator.
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 error usually
occurs when there is a problem with
the drive(s).
Resolve problem with drive(s). The controller
will then be able to write dirty data to drives and
posted write operations will be restored.
Accelerator
status: Dirty data
detected. Unable
to write dirty
data to drives
At least one cache line contains dirty
data that the controller has been
unable to flush (write) to the drives.
This problem usually occurs when
there is a problem with the drive(s).
Resolve the problem with the drive(s). The
controller will then be able to write dirty data to
drives.
continued