| Author |
Message |
pw
Guest
|
 Posted:
Fri Sep 24, 2004 12:16 am Post subject:
Unexpected SCSI Command Failure |
|
|
Installed an Adaptec AHA-2940UW PCI SCSI Controller, and attached a
Seagate ST39175LW drive by 68 pin cable.
At SCSI BIOS 2.20.0, the Seagate is listed as "Start Unit Request
Failed".
Within the SCSI BIOS, the Adaptec 240UW is listed as SCSI ID #7. The
Seagate is listed as SCSI ID #0.
Configuration options include "SCSI Parity Checking", which is
Enabled, and Host Adaptor SCSI Termination", which is set to
Automatic.
I don't know which SCSI Peripheral to boot from – I've tried both #0
and #7.
If I "Verify Disk Media" on the Seagate, I receive the following
message:
"Unexpected SCSI Command Failure"
Target SCSI ID: 0
SCSI CDB Sent: 03 00 00 00 0E 00 70 00 02 00
Host Adapter Status: 00h – No Host Adapter Error
Target Status: 02h – Check Condition
Sense Key: 02h – Not Ready
+Sense Code: 04h
+Sense Code Qualifier: 00h
Once in Windows XP:
Seagate drive is NOT seen in Disk Management, nor in My Computer.
The Seagate drive and Adaptec adaptor are both listed in Device
Manager as "…working properly". |
|
| Back to top |
|
 |
Bruce Morgen
Guest
|
| Posted:
Fri Sep 24, 2004 1:56 am Post subject:
Re: Unexpected SCSI Command Failure |
|
|
pw@marginwalker.com (pw) wrote:
| Quote: | Installed an Adaptec AHA-2940UW PCI SCSI Controller, and attached a
Seagate ST39175LW drive by 68 pin cable.
At SCSI BIOS 2.20.0, the Seagate is listed as "Start Unit Request
Failed".
Within the SCSI BIOS, the Adaptec 240UW is listed as SCSI ID #7. The
Seagate is listed as SCSI ID #0.
Configuration options include "SCSI Parity Checking", which is
Enabled, and Host Adaptor SCSI Termination", which is set to
Automatic.
I don't know which SCSI Peripheral to boot from – I've tried both #0
and #7.
If I "Verify Disk Media" on the Seagate, I receive the following
message:
"Unexpected SCSI Command Failure"
Target SCSI ID: 0
SCSI CDB Sent: 03 00 00 00 0E 00 70 00 02 00
Host Adapter Status: 00h – No Host Adapter Error
Target Status: 02h – Check Condition
Sense Key: 02h – Not Ready
+Sense Code: 04h
+Sense Code Qualifier: 00h
Once in Windows XP:
Seagate drive is NOT seen in Disk Management, nor in My Computer.
The Seagate drive and Adaptec adaptor are both listed in Device
Manager as "…working properly".
|
Tell me/us about the "68 pin
cable" -- you have a drive
without a built-in terminator
and that means you must
provide one at the far end of
the physical SCSI chain from
the controller. Some LVD/SE
cables have a permanently
attached terminators (which
should very close to the last
available connector), but
many other wide SCSI cables
don't, including most (all?)
of the plain jane pre-LVD
ribbon cables.
.................................................................
Posted via TITANnews - Uncensored Newsgroups Access
|
|
| Back to top |
|
|
Bryan Hoover
Guest
|
| Posted:
Fri Sep 24, 2004 2:10 am Post subject:
Re: Unexpected SCSI Command Failure |
|
|
Bruce Morgen wrote:
| Quote: |
pw@marginwalker.com (pw) wrote:
Tell me/us about the "68 pin
cable" -- you have a drive
without a built-in terminator
and that means you must
provide one at the far end of
the physical SCSI chain from
the controller. Some LVD/SE
cables have a permanently
attached terminators (which
should very close to the last
available connector), but
many other wide SCSI cables
don't, including most (all?)
of the plain jane pre-LVD
ribbon cables.
|
While on the subject of terminators here, if I could interject a
question.
Why is the terminator on the farthest connector? Seems like you'd want
it on the one following the last device if nothing else. I havn't
gotten my drives or connectors yet, so I don't really even know what
they look like. I'm assuming that a terminator is just like a
connector, except it's "null".
I'm thinking of it as the controller following the bus until it reaches
a the terminator, a dead end, at which point it knows there are no other
devices on the bus. If there are empty connectors between the last
device, and the terminator, isn't that a waste of time for the
controller, and doesn't it defeat the purpose of dampening signal
reflection?
Of course, electrically, I really don't know much about what any of this
means. I'm trying to get some feel for the nature, and more importantly
the proper use, of these elements.
Bryan
| Quote: |
................................................................
Posted via TITANnews - Uncensored Newsgroups Access
at http://www.TitanNews.com
-=Every Newsgroup - Anonymous, UNCENSORED, BROADBAND Downloads=-
|
--
I depict hope so vividly that every hopeful individual will recognize
himself in my portrayal; and yet it is a fake, for while I depict it I
am thinking of recollection. - (Soren Kierkegaard - Either/Or)
http://www.wecs.com/content.htm
This signature file is generated by Pick-a-Tag !
Written by Jeroen van Vaarsel
http://www.google.com/search?hl=en&ie=ISO-8859-1&q=pick-a-tag |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted:
Fri Sep 24, 2004 2:57 am Post subject:
Re: Unexpected SCSI Command Failure |
|
|
"pw" <pw@marginwalker.com> wrote in message news:a7afd510.0409231216.e26f659@posting.google.com
| Quote: | Installed an Adaptec AHA-2940UW PCI SCSI Controller, and attached a
Seagate ST39175LW drive by 68 pin cable.
At SCSI BIOS 2.20.0, the Seagate is listed as "Start Unit Request Failed".
|
Then it is dead. the bring up sequence (spinup and selftest) failed.
| Quote: |
Within the SCSI BIOS, the Adaptec 240UW is listed as SCSI ID #7.
The Seagate is listed as SCSI ID #0.
Configuration options include "SCSI Parity Checking", which is
Enabled, and Host Adaptor SCSI Termination", which is set to Automatic.
I don't know which SCSI Peripheral to boot from – I've tried both #0
and #7.
If I "Verify Disk Media" on the Seagate, I receive the following message:
"Unexpected SCSI Command Failure"
Target SCSI ID: 0
SCSI CDB Sent: 03 00 00 00 0E 00 70 00 02 00
Host Adapter Status: 00h – No Host Adapter Error
Target Status: 02h – Check Condition
Sense Key: 02h – Not Ready
|
'Not Ready' because the bring up sequence failed.
| Quote: | +Sense Code: 04h
+Sense Code Qualifier: 00h
Once in Windows XP:
Seagate drive is NOT seen in Disk Management, nor in My Computer.
|
Because it is not ready.
| Quote: |
The Seagate drive and Adaptec adaptor are both listed in Device
Manager as "…working properly".
|
Well, to the point that it does respond. |
|
| Back to top |
|
|
Mike Walsh
Guest
|
| Posted:
Sun Sep 26, 2004 1:07 am Post subject:
Re: Unexpected SCSI Command Failure |
|
|
Each end of the bus should be terminated, to reduce noise and reflected signals. If the termination is somewhere other than the end of the cable then any cable beyond the termination would be a stub which would reflect a signal. Such a stub would probably not conform to specs because allowable stub length is quite short. Termination impedance should be the same as cable impedance and is comparatively low. I don't remember what the impedance of a scsi bus is, but most cable termination (except coax) is around 100 ohms. The impedance of a device connection is much higher and does not have a great effect on overall bus impedance.
Bryan Hoover wrote:
| Quote: |
While on the subject of terminators here, if I could interject a
question.
Why is the terminator on the farthest connector? Seems like you'd want
it on the one following the last device if nothing else. I havn't
gotten my drives or connectors yet, so I don't really even know what
they look like. I'm assuming that a terminator is just like a
connector, except it's "null".
I'm thinking of it as the controller following the bus until it reaches
a the terminator, a dead end, at which point it knows there are no other
devices on the bus. If there are empty connectors between the last
device, and the terminator, isn't that a waste of time for the
controller, and doesn't it defeat the purpose of dampening signal
reflection?
Of course, electrically, I really don't know much about what any of this
means. I'm trying to get some feel for the nature, and more importantly
the proper use, of these elements.
Bryan
|
--
When replying by Email include NewSGrouP (case sensitive) in Subject
Mike Walsh
West Palm Beach, Florida, U.S.A. |
|
| Back to top |
|
|
Bryan Hoover
Guest
|
| Posted:
Sun Sep 26, 2004 2:35 am Post subject:
Re: Unexpected SCSI Command Failure |
|
|
Mike Walsh wrote:
| Quote: |
Each end of the bus should be terminated, to reduce noise and reflected signals. If the termination is somewhere other than the end of the cable then any cable beyond the termination would be a stub which would reflect a signal. Such a stub would probably not conform to specs because allowable stub length is quite short. Termination impedance should be the same as cable impedance and is comparatively low. I don't remember what the impedance of a scsi bus is, but most cable termination (except coax) is around 100 ohms. The impedance of a device connection is much higher and does not have a great effect on overall bus impedance.
|
-------
I did learn, from one of the specs that I've read along the way, that
the termination idea is not so much related to signaling the end of the
bus, but rather dampening reflection in general.
The internal connector cables I've been looking at often have the
terminator included. Is more or less common for these included
terminators to be active or passive? From what I've learned, active
terminators should be used with anything rated over 5 or 10MB/sec. So
if the cable as advertised as being for U2W SCSI-3, or just UW, with
terminator, would it be safe to assume that's an active terminator? I
mean, what's the general practice if any? -- safer to buy terminators
separtely, or generally, common for the right terminator to come with
the cable as specified in the ad?
Bryan
| Quote: |
Bryan Hoover wrote:
While on the subject of terminators here, if I could interject a
question.
Why is the terminator on the farthest connector? Seems like you'd want
it on the one following the last device if nothing else. I havn't
gotten my drives or connectors yet, so I don't really even know what
they look like. I'm assuming that a terminator is just like a
connector, except it's "null".
I'm thinking of it as the controller following the bus until it reaches
a the terminator, a dead end, at which point it knows there are no other
devices on the bus. If there are empty connectors between the last
device, and the terminator, isn't that a waste of time for the
controller, and doesn't it defeat the purpose of dampening signal
reflection?
Of course, electrically, I really don't know much about what any of this
means. I'm trying to get some feel for the nature, and more importantly
the proper use, of these elements.
Bryan
--
When replying by Email include NewSGrouP (case sensitive) in Subject
Mike Walsh
West Palm Beach, Florida, U.S.A.
|
--
That's why my soul always reverts to the Old Testament and to
Shakespeare. There at least one feels that it's human beings talking.
There people hate, people love, people murder their enemy and curse his
descendants through all generations, there people sin. - (Soren
Kierkegaard - Either/Or)
http://www.wecs.com/content.htm
This signature file is generated by Pick-a-Tag !
Written by Jeroen van Vaarsel
http://www.google.com/search?hl=en&ie=ISO-8859-1&q=pick-a-tag |
|
| Back to top |
|
|
Mike Walsh
Guest
|
| Posted:
Sun Sep 26, 2004 4:20 am Post subject:
Re: Unexpected SCSI Command Failure |
|
|
Most of the SCSI devices I work with are older SE (single ended). These drives have built in termination. Newer LVD (low voltage differential) drives don't have built in termination and require a separate active terminator. Most 40 MB/sec or slower devices are SE, most 80 MB/sec or faster devices are LVD. As far as i know all terminators that come with cables are active terminators for LVD.
Bryan Hoover wrote:
| Quote: |
The internal connector cables I've been looking at often have the
terminator included. Is more or less common for these included
terminators to be active or passive? From what I've learned, active
terminators should be used with anything rated over 5 or 10MB/sec. So
if the cable as advertised as being for U2W SCSI-3, or just UW, with
terminator, would it be safe to assume that's an active terminator? I
mean, what's the general practice if any? -- safer to buy terminators
separtely, or generally, common for the right terminator to come with
the cable as specified in the ad?
|
--
When replying by Email include NewSGrouP (case sensitive) in Subject
Mike Walsh
West Palm Beach, Florida, U.S.A. |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted:
Sun Sep 26, 2004 6:40 pm Post subject:
Re: Unexpected SCSI Command Failure |
|
|
"Mike Walsh" <mikew137@sbcglobal.net> wrote in message news:41560B50.9F8CBF9C@sbcglobal.net
| Quote: | Most of the SCSI devices I work with are older SE (single ended).
These drives have built in termination.
|
Your's maybe. Most SE drives but not all.
| Quote: | Newer LVD (low voltage differential) drives don't have built in termination
and require a separate active terminator.
|
and you need a separate terminator, active or LVD.
| Quote: | Most 40 MB/sec or slower devices are SE,
|
All of them.
| Quote: | most 80 MB/sec or faster devices are LVD.
|
All of them.
| Quote: | As far as i know all terminators that come with cables are active
terminators for LVD.
|
If they are (advertized as) LVD cables.
There are also SE cables that come with an (usually) 'active' terminator.
If it is flat and square (usually small pcb with a lid on) assume active.
If it looks like it may only just house a resisternetwork on the connec-
tor (beefed-up connector) then assume passive. However, a resistor
network, a small voltage regulator and 2 small capacitors still make an
active terminator. It takes a little bit of imagination of what is in there.
LVD terminators usually say LVD on them.
| Quote: |
Bryan Hoover wrote:
The internal connector cables I've been looking at often have the
terminator included. Is more or less common for these included
terminators to be active or passive? From what I've learned, active
terminators should be used with anything rated over 5 or 10MB/sec. So
if the cable as advertised as being for U2W SCSI-3, or just UW, with
terminator, would it be safe to assume that's an active terminator? I
mean, what's the general practice if any? -- safer to buy terminators
separtely, or generally, common for the right terminator to come with
the cable as specified in the ad? |
|
|
| Back to top |
|
|
Bryan Hoover
Guest
|
| Posted:
Sun Sep 26, 2004 7:46 pm Post subject:
Re: Unexpected SCSI Command Failure |
|
|
Mike Walsh wrote:
| Quote: |
Most of the SCSI devices I work with are older SE (single ended). These drives have built in termination. Newer LVD (low voltage differential) drives don't have built in termination and require a separate active terminator. Most 40 MB/sec or slower devices are SE, most 80 MB/sec or faster devices are LVD. As far as i know all terminators that come with cables are active terminators for LVD.
|
My impression is that single connector ribbons need to be terminated as
well, is that right? I bought 3 of these, and not sure. If I'm going
to use them, I'm thinking I may to get an adapter sort of terminator
that goes on the device, and accepts the device end of the ribbon, as
the devices themselves don't do termination.
Bryan
| Quote: | Bryan Hoover wrote:
The internal connector cables I've been looking at often have the
terminator included. Is more or less common for these included
terminators to be active or passive? From what I've learned, active
terminators should be used with anything rated over 5 or 10MB/sec. So
if the cable as advertised as being for U2W SCSI-3, or just UW, with
terminator, would it be safe to assume that's an active terminator? I
mean, what's the general practice if any? -- safer to buy terminators
separtely, or generally, common for the right terminator to come with
the cable as specified in the ad?
--
When replying by Email include NewSGrouP (case sensitive) in Subject
Mike Walsh
West Palm Beach, Florida, U.S.A.
|
--
Nothing in the world has more potential for beauty than woman. Nothing
has more potential to destroy it, than the world. - (Anonymous)
http://www.wecs.com/content.htm
This signature file is generated by Pick-a-Tag !
Written by Jeroen van Vaarsel
http://www.google.com/search?hl=en&ie=ISO-8859-1&q=pick-a-tag |
|
| Back to top |
|
|
Robert Nichols
Guest
|
| Posted:
Mon Sep 27, 2004 12:31 am Post subject:
Re: Unexpected SCSI Command Failure |
|
|
In article <4156E46F.1493C103@wecs.com>,
Bryan Hoover <bhoover@wecs.com> wrote:
:
:My impression is that single connector ribbons need to be terminated as
:well, is that right? I bought 3 of these, and not sure. If I'm going
:to use them, I'm thinking I may to get an adapter sort of terminator
:that goes on the device, and accepts the device end of the ribbon, as
:the devices themselves don't do termination.
In SE SCSI, the maximum length of an unterminated stub is 10 cm, and
I've seen cases where a single-device cable (2 connectors, total) of
that length failed to work properly unless the far end was terminated.
--
Bob Nichols AT comcast.net I am "rnichols42" |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted:
Mon Sep 27, 2004 7:08 pm Post subject:
Re: Unexpected SCSI Command Failure |
|
|
"Robert Nichols" <SEE_SIGNATURE@localhost.localdomain.invalid> wrote in message news:cj7n1s$55k$1@omega-3a.right.here
| Quote: | In article 4156E46F.1493C103@wecs.com, Bryan Hoover <bhoover@wecs.com> wrote:
My impression is that single connector ribbons need to be terminated as
well, is that right? I bought 3 of these, and not sure. If I'm going
to use them, I'm thinking I may to get an adapter sort of terminator
that goes on the device, and accepts the device end of the ribbon, as
the devices themselves don't do termination.
In SE SCSI, the maximum length of an unterminated stub is 10 cm,
|
There is no such thing as a terminated stub.
Stubs, by definition, are unterminated.
| Quote: | and I've seen cases where a single-device cable (2 connectors, total) of
that length failed to work properly unless the far end was terminated. |
|
|
| Back to top |
|
|
pw
Guest
|
| Posted:
Mon Sep 27, 2004 10:35 pm Post subject:
Re: Unexpected SCSI Command Failure |
|
|
Bruce Morgen <editor@juno.com> wrote in message news:<kae6l0puv9m2k9mnmcq97q3lusb5e9eeiu@4ax.com>...
| Quote: | pw@marginwalker.com (pw) wrote:
Installed an Adaptec AHA-2940UW PCI SCSI Controller, and attached a
Seagate ST39175LW drive by 68 pin cable.
At SCSI BIOS 2.20.0, the Seagate is listed as "Start Unit Request
Failed".
Within the SCSI BIOS, the Adaptec 240UW is listed as SCSI ID #7. The
Seagate is listed as SCSI ID #0.
Configuration options include "SCSI Parity Checking", which is
Enabled, and Host Adaptor SCSI Termination", which is set to
Automatic.
I don't know which SCSI Peripheral to boot from ? I've tried both #0
and #7.
If I "Verify Disk Media" on the Seagate, I receive the following
message:
"Unexpected SCSI Command Failure"
Target SCSI ID: 0
SCSI CDB Sent: 03 00 00 00 0E 00 70 00 02 00
Host Adapter Status: 00h ? No Host Adapter Error
Target Status: 02h ? Check Condition
Sense Key: 02h ? Not Ready
+Sense Code: 04h
+Sense Code Qualifier: 00h
Once in Windows XP:
Seagate drive is NOT seen in Disk Management, nor in My Computer.
The Seagate drive and Adaptec adaptor are both listed in Device
Manager as "?working properly".
Tell me/us about the "68 pin
cable" -- you have a drive
without a built-in terminator
and that means you must
provide one at the far end of
the physical SCSI chain from
the controller. Some LVD/SE
cables have a permanently
attached terminators (which
should very close to the last
available connector), but
many other wide SCSI cables
don't, including most (all?)
of the plain jane pre-LVD
ribbon cables.
|
68-pin cable with a "block-style" terminator at the very end of the cable... |
|
| Back to top |
|
|
pw
Guest
|
| Posted:
Mon Sep 27, 2004 10:43 pm Post subject:
Re: Unexpected SCSI Command Failure |
|
|
"Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message news:<2rhouiF1aukpqU1@uni-berlin.de>...
| Quote: | "pw" <pw@marginwalker.com> wrote in message news:a7afd510.0409231216.e26f659@posting.google.com
Installed an Adaptec AHA-2940UW PCI SCSI Controller, and attached a
Seagate ST39175LW drive by 68 pin cable.
At SCSI BIOS 2.20.0, the Seagate is listed as "Start Unit Request Failed".
Then it is dead. the bring up sequence (spinup and selftest) failed.
|
the drive is dead? for sure? i can just chuck it in the garbage?? |
|
| Back to top |
|
|
Folkert Rienstra
Guest
|
| Posted:
Tue Sep 28, 2004 2:38 am Post subject:
Re: Unexpected SCSI Command Failure |
|
|
"pw" <pw@marginwalker.com> wrote in message news:a7afd510.0409271043.577e55cf@posting.google.com
| Quote: | "Folkert Rienstra" <see_reply-to@myweb.nl> wrote in message news:<2rhouiF1aukpqU1@uni-berlin.de>...
"pw" <pw@marginwalker.com> wrote in message news:a7afd510.0409231216.e26f659@posting.google.com
Installed an Adaptec AHA-2940UW PCI SCSI Controller, and attached a
Seagate ST39175LW drive by 68 pin cable.
At SCSI BIOS 2.20.0, the Seagate is listed as "Start Unit Request Failed".
Then it is dead. the bring up sequence (spinup and selftest) failed.
the drive is dead?
|
Yup.
| Quote: | for sure? i can just chuck it in the garbage??
|
Or check the warranty. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in