HP NetServer LP 2000r HP Netserver Ultra3 SCSI HBA Guide - Page 86

The target device reports a Busy status. Another program may already be using

Get HP NetServer LP 2000r PDF manuals and user guides View all HP NetServer LP 2000r manuals
Add to My Manuals
Save this manual to your list of manuals

Page 86 highlights

9. Type Y to rebuild the kernel environment. 10. Reboot the system. Error Messages The error messages listed below are the messages associated with the adl60 driver. Messages are listed sequentially according to the last three digits of the error code. For example, [xxxxx010], [xxxxx011], [xxxxx012], etc. NOTE When reporting problems to Customer Support, be sure to include the complete error message in your problem description. [xxxxx020] Adapter or target device not responding or not connected The target device did not respond to the adapter. If the device is present, refer to your host bus adapter User's Guide for troubleshooting information. If the device is no longer connected to the system, ignore this error. [xxxxx022] Adapter or target device protocol error The adapter or target device has broken the communication protocol. A badly behaving device could cause this message to appear. Normally this is not a serious problem. If you get this message frequently over a short period of time, it could indicate that the device or system is malfunctioning. Unplug or power down unused devices to see if the problem persists. [xxxxx030] Target device busy [xxxxx032] Target device busy The target device reports a Busy status. Another program may already be using this device. [xxxxx09D] Unexpected interrupt The HP driver received an interrupt from the system that does not correspond to any adapter supported by the driver. This could be caused by another host bus adapter from a different vendor, such as a video card or network card. The problem can also be caused by malfunctioning hardware. 80

  • 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
80
9. Type
Y
to rebuild the kernel environment.
10. Reboot the system.
Error Messages
The error messages listed below are the messages associated with the adl60
driver. Messages are listed sequentially according to the last three digits of the
error code. For example, [xxxxx010], [xxxxx011], [xxxxx012], etc.
NOTE
When reporting problems to Customer Support, be sure to include the
complete error message in your problem description.
[xxxxx020] Adapter or target device not responding or not connected
The target device did not respond to the adapter. If the device is present, refer to
your host bus adapter User’s Guide for troubleshooting information. If the
device is no longer connected to the system, ignore this error.
[xxxxx022] Adapter or target device protocol error
The adapter or target device has broken the communication protocol. A badly
behaving device could cause this message to appear. Normally this is not a
serious problem. If you get this message frequently over a short period of time,
it could indicate that the device or system is malfunctioning. Unplug or power
down unused devices to see if the problem persists.
[xxxxx030] Target device busy
[xxxxx032] Target device busy
The target device reports a Busy status. Another program may already be using
this device.
[xxxxx09D] Unexpected interrupt
The HP driver received an interrupt from the system that does not correspond to
any adapter supported by the driver. This could be caused by another host bus
adapter from a different vendor, such as a video card or network card. The
problem can also be caused by malfunctioning hardware.