HP ProLiant DL380p HP ProLiant Servers Troubleshooting Guide - Page 94

Accelerator Status: Cache was Automatically Con d During Last Controller, Reset

Page 94 highlights

Accelerator Status: Cache was Automatically Configured During Last Controller Reset Description: Cache board was replaced with one of a different size. Action: No action is required. Accelerator Status: Data in the Cache was Lost... ...due to some reason other than the battery being discharged. Description: Data in cache was lost, but not because of the battery being discharged. Action: Be sure the array accelerator is properly seated. If the error persists, 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. Description: 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 a problem with the drive or drives occurs. Action: Resolve the problem with the drive or drives. The controller can then write the dirty data to the drives. Posted-writes operations are restored. Accelerator Status: Dirty Data Detected... ...Unable to write dirty data to drives Description: 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 a problem with the drive or drives occurs. Action: Resolve the problem with the drive or drives. The controller can then write the dirty data to the drives. Accelerator Status: Excessive ECC Errors Detected in at Least One Cache Line... ...As a result, at least one cache line is no longer in use. Description: At least one line in the cache is no longer in use due to excessive ECC errors detected during use of the memory associated with that cache line. Action: Consider replacing the cache. If cache replacement is not done, the remaining cache lines generally continue to operate properly. Accelerator Status: Excessive ECC Errors Detected in Multiple Cache Lines... ...As a result, the cache is no longer in use. Description: The number of cache lines experiencing excessive ECC errors has reached a preset limit. Therefore, the cache has been shut down. Action: 1. Reseat the cache to the controller. 2. If the problem persists, replace the cache. Error messages 94

  • 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

Error messages 94
Accelerator Status: Cache was Automatically Configured During Last Controller
Reset
Description
: Cache board was replaced with one of a different size.
Action
: No action is required.
Accelerator Status: Data in the Cache was Lost...
...due to some reason other than the battery being discharged.
Description
: Data in cache was lost, but not because of the battery being discharged.
Action
: Be sure the array accelerator is properly seated. If the error persists, 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.
Description
: 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 a problem with the drive or drives occurs.
Action
: Resolve the problem with the drive or drives. The controller can then write the dirty data to the drives.
Posted-writes operations are restored.
Accelerator Status: Dirty Data Detected...
...Unable to write dirty data to drives
Description
: 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 a problem with the drive or drives occurs.
Action
: Resolve the problem with the drive or drives. The controller can then write the dirty data to the drives.
Accelerator Status: Excessive ECC Errors Detected in at Least One Cache Line...
...As a result, at least one cache line is no longer in use.
Description
: At least one line in the cache is no longer in use due to excessive ECC errors detected during use
of the memory associated with that cache line.
Action
: Consider replacing the cache. If cache replacement is not done, the remaining cache lines generally
continue to operate properly.
Accelerator Status: Excessive ECC Errors Detected in Multiple Cache Lines...
...As a result, the cache is no longer in use.
Description
: The number of cache lines experiencing excessive ECC errors has reached a preset limit.
Therefore, the cache has been shut down.
Action
:
1.
Reseat the cache to the controller.
2.
If the problem persists, replace the cache.