Adaptec 29320LPE User Guide - Page 57

Common Error Messages, System Log, Words, Device connected, but not ready, Start unit request failed

Page 57 highlights

Chapter D: Troubleshooting ● 57 2 To view event details, select System Log from the Event Viewer tree. Double-click the appropriate Windows driver event that has an Event ID of 11. (There may be none or multiple driver events.) The top portion of the Event Detail dialog box displays information such as the time that the event was generated, the system on which the event occurred (in case of remote monitoring), and the description of the event. The Data section of the Event Details dialog box displays the error messages generated. Click the Words option. In the Data section of the dialog box, the entry in the second row and second column (to the right of the 0010: entry) lists the error message generated by the driver. The common error messages for the driver are described in Driver Error Messages below. Note: The entry in the third row of the last column identifies the SCSI ID of the device originating the error. Common Error Messages Here is what you should do if the following messages appear on the screen at bootup: "Device connected, but not ready" The host system received no answer when it requested data from an installed SCSI device. Run SCSISelect and set the Send Start Unit Command to Yes for the particular SCSI device ID. See Starting SCSISelect on page 36. Ensure that the device is set to spin up when the power is switched on. The spin up option is typically set by a jumper. (refer to the documentation for the device.) "Start unit request failed" This message can appear if the option to send Start Unit Command is set to Yes and device is not a disk drive. If this is the case, then change the setting to No in SCSISelect for the device. The SCSI card BIOS was unable to send a Start Unit Command to one of the installed SCSI devices. Run SCSISelect and disable the Send Start Unit Command for the device. "Time-out failure during..." An unexpected time-out occurred: ● Verify that the SCSI bus is properly terminated. ● Verify that all cables are properly connected. ● Try disconnecting the SCSI device cables from the SCSI card and then starting the system. If the system successfully restarts, one of the SCSI devices may be defective. Driver Error Messages The following error messages are listed sequentially according to the last three digits of the error message. For example, [xxxxx010], [xxxxx011], [xxxxx012], and so on. Note: When reporting problems to Adaptec Customer Support, be sure to include the complete error message in your problem description.

  • 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

Chapter D: Troubleshooting
57
2
To view event details, select
System Log
from the Event Viewer tree. Double-click the
appropriate Windows driver event that has an Event ID of 11. (There may be none or
multiple driver events.)
The top portion of the Event Detail dialog box displays information such as the time that
the event was generated, the system on which the event occurred (in case of remote
monitoring), and the description of the event. The Data section of the Event Details dialog
box displays the error messages generated.
Click the
Words
option.
In the Data section of the dialog box, the entry in the second row and second column (to
the right of the 0010: entry) lists the error message generated by the driver. The common
error messages for the driver are described in
Driver Error Messages
below.
Note:
The entry in the third row of the last column identifies the SCSI ID of the device
originating the error.
Common Error Messages
Here is what you should do if the following messages appear on the screen at bootup:
“Device connected, but not ready”
The host system received no answer when it requested data from an installed SCSI device.
Run SCSISelect and set the Send Start Unit Command to Yes for the particular SCSI device ID.
See
Starting SCSISelect
on page 36
.
Ensure that the device is set to spin up when the power is switched on. The spin up option is
typically set by a jumper. (refer to the documentation for the device.)
“Start unit request failed”
This message can appear if the option to send Start Unit Command is set to Yes and device is
not a disk drive. If this is the case, then change the setting to No in SCSISelect for the device.
The SCSI card BIOS was unable to send a Start Unit Command to one of the installed SCSI
devices. Run SCSI
Select
and disable the Send Start Unit Command for the device.
“Time-out failure during...”
An unexpected time-out occurred:
Verify that the SCSI bus is properly terminated.
Verify that all cables are properly connected.
Try disconnecting the SCSI device cables from the SCSI card and then starting the system.
If the system successfully restarts, one of the SCSI devices may be defective.
Driver Error Messages
The following error messages are listed sequentially according to the last three digits of the
error message. For example, [xxxxx010], [xxxxx011], [xxxxx012], and so on.
Note:
When reporting problems to Adaptec Customer Support, be sure to include the complete
error message in your problem description.