HP ProLiant DL380 G3 with MSA500 HP ProLiant Servers Troubleshooting Guide - Page 46

SD card problems, USB drive key problems

Page 46 highlights

A new 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.hp.com/go/bizsupport). 2. Be sure the drive bay is not defective by installing the hard drive in another bay. 3. Run HP Insight Diagnostics (on page 75). Then, replace failed components as indicated. 4. When the drive is a replacement drive on an array controller, be sure that the drive is the same type and of the same or larger capacity than the original drive. Data is inaccessible Action: 1. Be sure the files are not corrupt. Run the repair utility for the operating system. 2. Be sure no viruses exist on the server. Run a current version of a virus scan utility. 3. When a TPM is installed and is being used with BitLocker™, be sure the TPM is enabled in RBSU ("HP ROM-Based Setup Utility" on page 67). See the TPM replacement recovery procedure in the operating system documentation. 4. When migrating encrypted data to a new server, be sure to follow the recovery procedures in the operating system documentation. Server response time is slower than usual Action: 1. Be sure the hard drive is not full. If needed, increase the amount of free space on the hard drive. HP recommends that hard drives have a minimum of 15 percent free space. 2. Review information about the operating system encryption technology, which can cause a decrease in server performance. For more information, see the operating system documentation. SD card 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 SD card. 2. Reseat the SD card. USB drive key problems System does not boot from the drive Action: 1. Be sure that USB is enabled in RBSU. 2. Be sure the drive boot order in RBSU is set so that the server boots from the USB drive key. 3. Reseat the USB drive key. Hardware problems 46

  • 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

Hardware problems 46
A new drive is not recognized
Action
:
1.
Be sure the drive is supported. To determine drive support, see the server documentation or the HP
website (
).
2.
Be sure the drive bay is not defective by installing the hard drive in another bay.
3.
Run HP Insight Diagnostics (on page
75
). Then, replace failed components as indicated.
4.
When the drive is a replacement drive on an array controller, be sure that the drive is the same type and
of the same or larger capacity than the original drive.
Data is inaccessible
Action
:
1.
Be sure the files are not corrupt. Run the repair utility for the operating system.
2.
Be sure no viruses exist on the server. Run a current version of a virus scan utility.
3.
When a TPM is installed and is being used with BitLockerâ„¢, be sure the TPM is enabled in RBSU ("
HP
ROM-Based Setup Utility
" on page
67
). See the TPM replacement recovery procedure in the operating
system documentation.
4.
When migrating encrypted data to a new server, be sure to follow the recovery procedures in the
operating system documentation.
Server response time is slower than usual
Action
:
1.
Be sure the hard drive is not full. If needed, increase the amount of free space on the hard drive. HP
recommends that hard drives have a minimum of 15 percent free space.
2.
Review information about the operating system encryption technology, which can cause a decrease in
server performance. For more information, see the operating system documentation.
SD card 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 SD card.
2.
Reseat the SD card.
USB drive key problems
System does not boot from the drive
Action
:
1.
Be sure that USB is enabled in RBSU.
2.
Be sure the drive boot order in RBSU is set so that the server boots from the USB drive key.
3.
Reseat the USB drive key.