HP ProLiant DL980 HP ProLiant Servers Troubleshooting Guide - Page 65

Boot problems

Page 65 highlights

Network connection fails on remote communication Because network connectivity cannot be guaranteed, it is possible for the administrative client to become disconnected from the target server during the ROM flash preparation. If any remote connectivity procedure fails during the ROM flash online preparation, the ROM flash does not occur for the target system. An error message describing the broken connection displays and the program exits. Attempt to ascertain and correct the cause of connection failure, and then restart the process. Failure occurs during ROM flash After the online flash preparation has been successfully completed, the system ROM is flashed offline. The flash cannot be interrupted during this process, or the ROM image is corrupted and the server does not start. The most likely reason for failure is a loss of power to the system during the flash process. Initiate ROMPaq disaster recovery procedures. Target system is not supported If the target system is not listed in the supported servers list, an error message appears and the program exits. Only supported systems can be upgraded using the Remote ROM Flash utility. To determine if the server is supported, see the HP website (http://www.hp.com/support). System requests recovery method during a firmware update When updating the firmware on a BitLocker™-encrypted server, always disable BitLocker™ before updating the firmware. If BitLocker™ is not disabled, the system requests the recovery method selected when BitLocker™ was configured. Failure to provide the correct recovery password or passwords results in loss of access to all encrypted data. If BitLocker™ is configured to measure option ROMs, you must follow the firmware upgrade steps in "Updating firmware (on page 82)." BitLocker™ can be configured to measure the following option ROMs: • iLO 2 • NIC • Smart Array storage • Standup HBAs Be sure to enable BitLocker™ after the firmware updates are complete. For information on performing ROM updates, see "Firmware maintenance (on page 80)." For information on BitLocker™, see BitLocker™ for servers on the Microsoft website (http://www.microsoft.com). Boot problems Server does not boot Possible cause: • The system ROMPaq flash fails. • The system ROM is corrupt. Software problems 65

  • 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

Software problems 65
Network connection fails on remote communication
Because network connectivity cannot be guaranteed, it is possible for the administrative client to become
disconnected from the target server during the ROM flash preparation. If any remote connectivity
procedure fails during the ROM flash online preparation, the ROM flash does not occur for the target
system. An error message describing the broken connection displays and the program exits. Attempt to
ascertain and correct the cause of connection failure, and then restart the process.
Failure occurs during ROM flash
After the online flash preparation has been successfully completed, the system ROM is flashed offline. The
flash cannot be interrupted during this process, or the ROM image is corrupted and the server does not
start. The most likely reason for failure is a loss of power to the system during the flash process. Initiate
ROMPaq disaster recovery procedures.
Target system is not supported
If the target system is not listed in the supported servers list, an error message appears and the program
exits. Only supported systems can be upgraded using the Remote ROM Flash utility. To determine if the
server is supported, see the HP website (
).
System requests recovery method during a firmware update
When updating the firmware on a BitLocker™-encrypted server, always disable BitLocker™ before
updating the firmware. If BitLocker™ is not disabled, the system requests the recovery method selected
when BitLocker™ was configured. Failure to provide the correct recovery password or passwords results
in loss of access to all encrypted data.
If BitLocker™ is configured to measure option ROMs, you must follow the firmware upgrade steps in
"Updating firmware (on page
82
)." BitLocker™ can be configured to measure the following option
ROMs:
iLO 2
NIC
Smart Array storage
Standup HBAs
Be sure to enable BitLocker™ after the firmware updates are complete.
For information on performing ROM updates, see "Firmware maintenance (on page
80
)."
For information on BitLocker™, see BitLocker™ for servers on the Microsoft website
(
).
Boot problems
Server does not boot
Possible cause:
The system ROMPaq flash fails.
The system ROM is corrupt.