HP ML350 HP ProLiant Servers Troubleshooting Guide - Page 43

System completes POST but drive fails, No har, Hard drive is not recognized by the server, d drives

Page 43 highlights

System completes POST but drive fails Action: 1. Be sure no loose connections (on page 17) exist. 2. Be sure no device conflict exists. 3. Be sure the hard drive is cabled properly and terminated if necessary. 4. Be sure the hard drive data cable is working by replacing it with a known functional cable. 5. Be sure the access panel is installed properly when the server is operating. Drives may overheat and cause sluggish response or drive failure. 6. Run Insight Diagnostics ("HP Insight Diagnostics" on page 74) and replace failed components as indicated. 7. Run RBSU ("HP ROM-Based Setup Utility" on page 65) to verify that the boot controller order is set properly. No hard drives are recognized Action: 1. Be sure no power problems (on page 36) exist. 2. Check for loose connections (on page 17). 3. Be sure that the controller supports the hard drives being installed. 4. Be sure the controller has the most recent firmware. Hard drive is not recognized by the server Action: 1. Check the hard drive LEDs to be sure they indicate normal function. For information on hard drive LEDs, see hard drive LED combinations (on page 19). For server-specific hard drive LED information, see the server documentation or the HP website (http://www.hp.com). 2. Be sure no loose connections (on page 17) exist. 3. Be sure the correct drive controller drivers are installed. 4. Be sure the hard drive is configured properly: a. To determine the proper configuration, see the hard drive documentation. b. Remove the hard drive and be sure the configuration jumpers are set properly. c. For a non-hot-plug hard drive, be sure a conflict does not exist with another hard drive. Check for SCSI ID conflicts. d. When using an array controller, be sure the hard drive is configured in an array. Run ACU ("Array Configuration Utility" on page 67). A new hard drive is not recognized Action: 1. Be sure the drive is supported. To determine drive support, see the server documentation or the HP website (http://www.docs.hp.com). 2. Be sure the drive bay is not defective by installing the hard drive in another bay. Hardware problems 43

  • 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

System completes POST but drive fails
2.
inated if necessary.
5.
e server is operating. Drives may overheat and
drive failure.
("
HP Insight Diagnostics
" on page
74
) and replace failed components as
RBSU ("
HP ROM-Based Setup Utility
" on page
65
) to verify that the boot controller order is set
No har
4.
Be sure the controller has the most recent firmware.
Hard drive is not recognized by the server
rmation on hard drive
ion,
Action
:
1.
Be sure no loose connections (on page
17
) exist.
Be sure no device conflict exists.
3.
Be sure the hard drive is cabled properly and term
4.
Be sure the hard drive data cable is working by replacing it with a known functional cable.
Be sure the access panel is installed properly when th
cause sluggish response or
6.
Run Insight Diagnostics
indicated.
7.
Run
properly.
d drives are recognized
Action
:
1.
Be sure no power problems (on page
36
) exist.
2.
Check for loose connections (on page
17
).
3.
Be sure that the controller supports the hard drives being installed.
Action
:
1.
Check the hard drive LEDs to be sure they indicate normal function. For info
LEDs, see hard drive LED combinations (on page
19
). For server-specific hard drive LED informat
see the server documentation or the HP website (
).
2.
Be sure no loose connections (on page
17
) exist.
s are installed.
sure the hard drive is configured properly:
r
icts.
Configuration Utility
" on page
67
).
A new
r
1.
ocumentation or the HP
3.
Be sure the correct drive controller driver
4.
Be
a.
To determine the proper configuration, see the hard drive documentation.
b.
Remove the hard drive and be sure the configuration jumpers are set properly.
c.
For a non-hot-plug hard drive, be sure a conflict does not exist with another hard drive. Check fo
SCSI ID confl
d.
When using an array controller, be sure the hard drive is configured in an array. Run ACU
("
Array
ha d drive is not recognized
Action
:
Be sure the drive is supported. To determine drive support, see the server d
website (
).
2.
Be sure the drive bay is not defective by installing the hard drive in another bay.
Hardware problems 43