HP Tc2120 serhp server tc2120 operations and maintenance guide - english - Page 81

Heading3 - Symptom:, Heading3 - Action:, Heading1 - IDE Problems

Get HP Tc2120 - Server - 256 MB RAM PDF manuals and user guides
UPC - 808736945332
View all HP Tc2120 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 81 highlights

Chapter 6 Troubleshooting This lets the SCSI BIOS for the boot controller board load, preventing conflicts from the other SCSI controllers. If necessary, remove the other SCSI controller boards, except the SCSI boot controller board, until you resolve the current problem. 3. Reboot the server and run the (BIOS) Setup Utility (press F10 during the boot process). 4. Select the Boot menu and the Boot Device Priority submenu. Make sure that the SCSI hard drive is not disabled. 5. Determine what the boot order is for this server model. See "Mass Storage" in Chapter 3, Installing and Configuring. 6. Verify the SCSI controller board is in the right place in the boot order. 7. Verify the SCSI boot drive (address ID = 0) is in the right place in the boot order. Symptom: • The SCSI devices stop working. Action: 1. Review the Troubleshooting Checklist and Mass Storage Guidelines before you continue. 2. Run the Diagnostics for Windows utility and: a. Verify the SCSI IDs and any relevant switch settings are correct. b. Verify the problem is the SCSI bus, by looking for specific information. 3. If an accessory board was added recently, check for a resource conflict between the new board and an existing accessory board. 4. Also, if you have changed the options on an existing board, there may be a resource conflict: a. Remove the new board and restart the server. b. If this corrects the problem, the board is either defective or it is trying to use a system resource used by the SCSI controller board. c. Check if the board is using memory, I/O addresses, or interrupt lines that are also used by the SCSI controller board. 5. Check for any recent changes or upgrades to the software. For example, has anyone moved, removed, or changed the configuration files or drivers? Refer to the software documentation for more information. 6. If you suspect hardware failure and there are no system error messages or beep codes, check each component associated with the failure. Equipment failure is probably the most unlikely reason for a SCSI devices failure. IDE Problems Symptom: • The IDE devices stop working. Action: 1. Review the Troubleshooting Checklist and Mass Storage Guidelines before you continue. 2. Reboot the server and run the (BIOS) Setup Utility (press F10 during the boot process). 3. Select the Boot menu and Boot Device Priority submenu. Make sure the device is not disabled. 75

  • 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
75
Chapter 6
Troubleshooting
This lets the SCSI BIOS for the boot controller board load, preventing conflicts from the other SCSI
controllers. If necessary, remove the other SCSI controller boards, except the SCSI boot controller board,
until you resolve the current problem.
3.
Reboot the server and run the (BIOS) Setup Utility (press F10 during the boot process).
4.
Select the Boot menu and the Boot Device Priority submenu. Make sure that the SCSI hard drive is not
disabled.
5.
Determine what the boot order is for this server model. See
“Mass Storage”
in
Chapter 3‚ Installing and
Configuring
.
6.
Verify the SCSI controller board is in the right place in the boot order.
7.
Verify the SCSI boot drive (address ID = 0) is in the right place in the boot order.
Symptom:
•
The SCSI devices stop working.
Action:
1.
Review the Troubleshooting Checklist and Mass Storage Guidelines before you continue.
2.
Run the Diagnostics for Windows utility and:
a.
Verify the SCSI IDs and any relevant switch settings are correct.
b.
Verify the problem is the SCSI bus, by looking for specific information.
3.
If an accessory board was added recently, check for a resource conflict between the new board and an
existing accessory board.
4.
Also, if you have changed the options on an existing board, there may be a resource conflict:
a.
Remove the new board and restart the server.
b.
If this corrects the problem, the board is either defective or it is trying to use a system resource used by
the SCSI controller board.
c.
Check if the board is using memory, I/O addresses, or interrupt lines that are also used by the SCSI
controller board.
5.
Check for any recent changes or upgrades to the software.
For example, has anyone moved, removed, or changed the configuration files or drivers? Refer to the
software documentation for more information.
6.
If you suspect hardware failure and there are no system error messages or beep codes, check each
component associated with the failure.
Equipment failure is probably the most unlikely reason for a SCSI devices failure.
IDE Problems
Symptom:
•
The IDE devices stop working.
Action:
1.
Review the Troubleshooting Checklist and Mass Storage Guidelines before you continue.
2.
Reboot the server and run the (BIOS) Setup Utility (press F10 during the boot process).
3.
Select the Boot menu and Boot Device Priority submenu. Make sure the device is not disabled.