Help configuring SCSI drive (Unexpected SCSI Command Failure)

Help configuring SCSI drive (Unexpected SCSI Command Failure)

Post by v2pate » Tue, 08 Mar 2005 06:57:00


Hi, I received two drives and a controller card from somebody, and I'm
having trouble getting them to work. One drive is a WD Enterprise
18gb drive 68-pin LVD, the other is an IBM 36LZX 68-pin (U160 I'm
pretty sure) drive, and the controller card is an Adaptec 2940U2W. I
currently have a SCSI setup in my system with 3 small UW drives (1
4.5GB IBM 9ES and 2 2.25GB Seagate Barracuda), a Yamaha 6416S CDRW,
and an HP Scanjet 5p all a man connected to an Adaptec 2940UW with no
problems.

Now I tried the WD drive first and I tried it with my 2940UW card
first and when the card scans ID's for drives/devices it makes a wierd
chirping sound. The drive is really noisy in general but makes that
chirping sound when being detected. I couldn't get the drive to be
detected in fdisk or windows setup when booting from a windows CD. I
went in the SCSI BIOS and the drive is detected, but when I try to
verify media or format the drive I get the following error:

UNEXPECTED SCSI COMMAND FAILURE
Target SCSI ID: 1
SCSI CDB Sent: 03 00 00 00 0E 00 70 00 02 00
Host Adapter status: 00h-No Host Adapter
Target Status: 02h-Check Condition
Sense Key: 02h-not ready
+Sense Code: 4ch
+Sense Code Qualifier:00h

I got the same error when I tried it with the 2940U2W card as well.
Now with LVD do you have to have an active terminator? Because I
can't find a terminator jumper on the drive. There's a jumper to
enable SE mode, so I did that, but would you still need active
termination? I tried the drive with my old UW cable, as well as a
LVD/SE cable with an active terminator, but I got the same problem.
The only difference is that the drive seemed really slow with the UW
cable and wouldn't detect sometimes. Does it matter what specific
connector you use on a cable with multiple connectors?

Now with the IBM 36LZX I tried with both cards as well and I got a
similar message. The difference with this drive is that it keeps
spinning up and then stops spinning for a while, and then spins up
again etc. It has a termination jumper so I assume it's not LVD, but
I tried with both cables. I got a "wide negotiation failed" message
when I had the CDRW hooked up with it on the 50-pin channel, so I
disconnected it. After that theit to drive sometimes displays the
message "Start Unit Request Failed" when detected instead of Hard Disk
0 or Hard Disk 1 etc. Going into the card BIOS to format disk or
verify media, I got the message:

UNEXPECTED SCSI COMMAND FAILURE
Target SCSI ID: 1
SCSI CDB Sent: 03 00 00 00 0E 00 70 00 02 00
Host Adapter status: 00h-No Host Adapter
Target Status: 02h-Check Condition
Sense Key: 02h-not ready
+Sense Code: 04h
+Sense Code Qualifier:00h

I don't know if I'm doing something wrong, but I haven't had problem
like this before. With my old drives it was no problems. Just set
the ID jumpers and plug and play.

Could both drives be bad? I don't know, maybe the guy who gave them
to me figured that I would think I'm doing something wrong since the
likelihood of two bad drives is slim. Sorry for the long post. Any
help would be appreciated.
 
 
 

Help configuring SCSI drive (Unexpected SCSI Command Failure)

Post by Rob Tur » Tue, 08 Mar 2005 07:09:42


ASC/ASCQ 4C/00 means "Logical unit failed self-configuration". Most likely
the drive can't read anything about it's internal configuration from a
number of reserved sectors. That drive is toast..


You'll need to make sure the bus is properly terminated. If it can't be
terminated by the drive (most LVD drives don't have on-board termination)
then you'll need to use a matching terminator on the last connector of the
cable. The LVD/SE cable you described should work OK.


That drive isn't able to find it's home position. It's toast too.


Sounds like you got yourself two matching bricks, sorry. Try to get the guy
to take them back..

Rob

 
 
 

Help configuring SCSI drive (Unexpected SCSI Command Failure)

Post by v2pate » Tue, 08 Mar 2005 23:59:26

Rob Turk" < XXXX@XXXXX.COM > wrote in message news:<422b7f29$0$49300$ XXXX@XXXXX.COM >...

Thanks for the info. I was fearing that they were bad, but I was
hoping that I was just doing something wrong. The 36GB drive is still
under warranty so it's not a huge deal, but the 18GB warranty expired
a little while ago.

Can I ask how you determined the problems from the error codes? Is
there a website that details what the error codes mean?

About termination, does the terminator have to be on that last
connector (the one that's spaced really closely to the second last
connector)? For example, if I had a 5 device cable but only had one
drive, is it possible to put the terminator on the third connector,
thereby cutting off the extra connectors you don't need?
 
 
 

Help configuring SCSI drive (Unexpected SCSI Command Failure)

Post by Folkert Ri » Wed, 09 Mar 2005 02:52:40

v2patel" < XXXX@XXXXX.COM > wrote in message news: XXXX@XXXXX.COM

Differential drives don't have onboard terminators.


Yup.



Nope. Not under normal conditions.


Looks like it.


Or knew what he gave away.

 
 
 

Help configuring SCSI drive (Unexpected SCSI Command Failure)

Post by Folkert Ri » Wed, 09 Mar 2005 02:54:02


Nope, that is
04/00 LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE
http://www.yqcomputer.com/ #ASC_04

On an IBM that is a spindle motor related problem:
"Start spindle motor fail".
 
 
 

Help configuring SCSI drive (Unexpected SCSI Command Failure)

Post by Rob Tur » Wed, 09 Mar 2005 15:47:21


The codes are in the SCSI standard. Here's a link (borrowed from Folkert's
message):
http://www.yqcomputer.com/

If you ever see codes with numbers of 80 (hex) or above then they are Vendor
Unique and you'll have to ask the vendor of the device what the code means.
In your case it's all in the list.

Rob