HP Surestore Disk Array FC60 HP SureStore E Disk Array 12H User's and Service - Page 183

HP Surestore Disk Array FC60 Manual

Get HP Surestore Disk Array FC60 PDF manuals and user guides View all HP Surestore Disk Array FC60 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 183 highlights

Troubleshooting Troubleshooting Event Code Descriptions Event Number (DEC/hex) Event Name Event Predictive Suspected Logged Maintenance Components Implication Description 221/0xdd Cache Version Mismatch In RAM Image Y See errors None associated with shutdown A new version of controller firmware has been download with writes stuck in cache. Normally there will be no writes stuck in cache and a firmware download will complete without any problems. However, if there are writes stuck in cache, the upload will fail with this event code. To correct this it may be necessary to revert to the old version of firmware and solve whatever problem is causing writes to be stuck in cache (probably one or more disks have failed). 222/0xde RAM Version Mismatch Y NA None The upload routine was unable to upload part of the disk NVRAM image because the current firmware does not support that use of RAM. (Most likely an older version of firmware is trying to upload a disk image posted by some other firmware version.) 183

  • 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
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
Troubleshooting
Event Code Descriptions
183
Troubleshooting
Event
Number
(DEC/hex)
Event Name
Event
Logged
Predictive
Maintenance
Implication
Suspected
Components
Description
221/0xdd
Cache Version
Mismatch In
RAM Image
Y
See errors
associated with
shutdown
None
A new version of controller
firmware has been download
with writes stuck in cache.
Normally there will be no
writes stuck in cache and a
firmware download will
complete without any
problems. However, if there
are writes stuck in cache, the
upload will fail with this event
code.
To correct this it may be
necessary to revert to the old
version of firmware and solve
whatever problem is causing
writes to be stuck in cache
(probably one or more disks
have failed).
222/0xde
RAM Version
Mismatch
Y
NA
None
The upload routine was unable
to upload part of the disk
NVRAM image because the
current firmware does not
support that use of RAM.
(Most likely an older version
of firmware is trying to upload
a disk image posted by some
other firmware version.)