Compaq ML530R Service Guide - Page 106

Array Configuration Utility ACU to con the, Either a board has been removed

Get Compaq ML530R - HP ProLiant - 128 MB RAM PDF manuals and user guides
UPC - 720591250300
View all Compaq ML530R manuals
Add to My Manuals
Save this manual to your list of manuals

Page 106 highlights

3-46 Compaq ProLiant ML530 Servers Maintenance and Service Guide Table 3-20 ADU Diagnostic Messages continued Message Description Loose cable detected - logical drives may be marked FAILED until corrected Controller unable to communicate with one or more physical drives, probably because of a cabling problem. Logical drives may be in a FAILED state until the condition is corrected, preventing access to data on the controller. If logical drives are marked FAILED, those logical drives will be unusable until problem corrected. Mirror data miscompare Data was found at reinitialization in the posted write memory; however, the mirror data compare test failed resulting in data being marked as invalid. Data loss is possible. No configuration for accelerator board The array accelerator board has not been configured. NVRAM configuration present, controller not detected EISA nonvolatile RAM has a configuration for an array controller, but there is no board in this slot. Either a board has been removed from the system or a board has been placed in the wrong slot. One or more drives is unable to support redundant controller operation At least one drive in use does not support redundant controller operation. Other controller indicates different hardware model The other controller in the redundant controller configuration is a different hardware model. Other controller indicates different firmware version The other controller in the redundant controller configuration is using a different firmware version. Other controller indicates different cache size The other controller in the redundant controller configuration has a different size array accelerator. Recommended Action Check all controllers and drive cable connections. Turn off the system. Check cables for tight connection to logical drives. Restart the system. If the same message recurs, cables may be bad. Replace the array accelerator board. If the array accelerator board is present, run the Array Configuration Utility (ACU) to configure the board. Place the array controller in the proper slot or run the System Configuration Utility to reconfigure nonvolatile RAM to reflect the removal or new position. Replace the drive that does not support redundant controller operation. Make sure both controllers are fully seated and using the same hardware model. Make sure both controllers are using the same firmware revision. Make sure both controllers are using the same capacity array accelerator. 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
3-46
Compaq ProLiant ML530 Servers Maintenance and Service Guide
Table 3-20
ADU Diagnostic Messages
continued
Message
Description
Recommended Action
Loose cable
detected
–
logical drives
may be marked
FAILED until
corrected
Controller unable to communicate
with one or more physical drives,
probably because of a cabling
problem.
Logical drives may be in a FAILED
state until the condition is corrected,
preventing access to data on the
controller. If logical drives are
marked FAILED, those logical drives
will be unusable until problem
corrected.
Check all controllers and drive cable
connections.
Turn off the system. Check cables for tight
connection to logical drives. Restart the system.
If the same message recurs, cables may be
bad.
Mirror data
miscompare
Data was found at reinitialization in
the posted write memory; however,
the mirror data compare test failed
resulting in data being marked as
invalid. Data loss is possible.
Replace the array accelerator board.
No configuration
for accelerator
board
The array accelerator board has not
been configured.
If the array accelerator board is present, run the
Array Configuration Utility (ACU) to configure the
board.
NVRAM
configuration
present,
controller not
detected
EISA nonvolatile RAM has a
configuration for an array controller,
but there is no board in this slot.
Either a board has been removed
from the system or a board has been
placed in the wrong slot.
Place the array controller in the proper slot or
run the System Configuration Utility to
reconfigure nonvolatile RAM to reflect the
removal or new position.
One or more
drives is unable
to support
redundant
controller
operation
At least one drive in use does not
support redundant controller
operation.
Replace the drive that does not support
redundant controller operation.
Other controller
indicates
different
hardware model
The other controller in the redundant
controller configuration is a different
hardware model.
Make sure both controllers are fully seated and
using the same hardware model.
Other controller
indicates
different
firmware version
The other controller in the redundant
controller configuration is using a
different firmware version.
Make sure both controllers are using the same
firmware revision.
Other controller
indicates
different cache
size
The other controller in the redundant
controller configuration has a
different size array accelerator.
Make sure both controllers are using the same
capacity array accelerator.
continued