HP ProLiant DL980 HP ProLiant Servers Troubleshooting Guide - Page 41

Internal system problems

Page 41 highlights

a. To a different slot on the same bus (not applicable for PCI Express) b. To a PCI, PCI-X, or PCI Express slot on a different bus c. To the same slot in another working server of the same or similar design If the board works in any of these slots, either the original slot is bad or the board was not properly seated. Reinsert the board into the original slot to verify. 4. If you are testing a board (or a device that connects to a board): a. Test the board with all other boards removed. b. Test the server with only that board removed. CAUTION: Clearing NVRAM deletes the configuration information. Refer to the server documentation for complete instructions before performing this operation or data loss could occur. 5. Clearing NVRAM can resolve various problems. Clear the NVRAM, but do not use the backup .SCI file if prompted. Have available any .CFG, .OVL, or .PCF files that are required. Internal system problems Battery pack problems The battery stops charging or begins to swell The batteries in BBWC battery packs are a consumable material. After 3 years of service, batteries may not provide predictable data retention times. If a battery fails completely, the HP Smart Array controller detects this condition and automatically restricts write cache functions to protect user data. To help ensure uninterrupted performance levels, HP recommends replacing battery packs at 3-year intervals. In NiMH batteries, the charging and discharging processes create and recombine inert gases, which can cause the button cell to swell in size by as much as 20%. Battery packs are designed to stop charging before excess swelling occurs. However, if excess swelling does occur, a pressure mechanism within the button cell releases these nontoxic, non-corrosive gases before the cell incurs physical damage. If this pressure release occurs, the battery no longer charges properly, and the storage solution reports a failed battery. CD-ROM and DVD drive problems System does not boot from the drive Action: 1. Be sure the drive boot order in RBSU is set so that the server boots from the CD-ROM drive first. 2. If the CD-ROM drive jumpers are set to CS (the factory default), be sure the CD-ROM drive is installed as device 0 on the cable so that it is in position for the server to boot from the drive. 3. Be sure no loose connections (on page 18) exist. 4. Be sure the media from which you are attempting to boot is not damaged and is a bootable CD. 5. If attempting to boot from a USB CD-ROM drive: Hardware problems 41

  • 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

Hardware problems 41
a.
To a different slot on the same bus (not applicable for PCI Express)
b.
To a PCI, PCI-X, or PCI Express slot on a different bus
c.
To the same slot in another working server of the same or similar design
If the board works in any of these slots, either the original slot is bad or the board was not properly
seated. Reinsert the board into the original slot to verify.
4.
If you are testing a board (or a device that connects to a board):
a.
Test the board with all other boards removed.
b.
Test the server with only that board removed.
CAUTION:
Clearing NVRAM deletes the configuration information. Refer to the server
documentation for complete instructions before performing this operation or data loss could
occur.
5.
Clearing NVRAM can resolve various problems. Clear the NVRAM, but do not use the backup .SCI
file if prompted. Have available any .CFG, .OVL, or .PCF files that are required.
Internal system problems
Battery pack problems
The battery stops charging or begins to swell
The batteries in BBWC battery packs are a consumable material. After 3 years of service, batteries may
not provide predictable data retention times. If a battery fails completely, the HP Smart Array controller
detects this condition and automatically restricts write cache functions to protect user data. To help ensure
uninterrupted performance levels, HP recommends replacing battery packs at 3-year intervals.
In NiMH batteries, the charging and discharging processes create and recombine inert gases, which can
cause the button cell to swell in size by as much as 20%. Battery packs are designed to stop charging
before excess swelling occurs.
However, if excess swelling does occur, a pressure mechanism within the button cell releases these non-
toxic, non-corrosive gases before the cell incurs physical damage. If this pressure release occurs, the
battery no longer charges properly, and the storage solution reports a failed battery.
CD-ROM and DVD drive problems
System does not boot from the drive
Action
:
1.
Be sure the drive boot order in RBSU is set so that the server boots from the CD-ROM drive first.
2.
If the CD-ROM drive jumpers are set to CS (the factory default), be sure the CD-ROM drive is
installed as device 0 on the cable so that it is in position for the server to boot from the drive.
3.
Be sure no loose connections (on page
18
) exist.
4.
Be sure the media from which you are attempting to boot is not damaged and is a bootable CD.
5.
If attempting to boot from a USB CD-ROM drive: