SCSI device does not respond

M

Matt Cross

I have just built a new computer, and it is my first
attempt at using SCSI devices. I have a Tekram DC-390U3W
ultra 160 scsi card, which has the LSI53c1010 chip made
by lsilogic (formerly symbios). My problem is as
follows. Whenever windows starts, it takes an extremely
long amount of time. This is true for Windows XP and
Windows 2000 (Win 98 does not have these startup
problems). By a long amount of time, I mean ~7-10min for
XP. After booting everything works fine, I think.

I get the following message about 30 times in the error
log each time that I boot: "The device,
\Device\Scsi\sym_u32, did not respond within the timeout
period." The device in question is my SCSI card, but I
don't know what to do about it. I've tried many
different drivers, but I can't one that works better than
the others. Please help me if you've had similar
problems or if you know what is happening. Thank you.
 
M

Michael W Ryder

Matt said:
I have just built a new computer, and it is my first
attempt at using SCSI devices. I have a Tekram DC-390U3W
ultra 160 scsi card, which has the LSI53c1010 chip made
by lsilogic (formerly symbios). My problem is as
follows. Whenever windows starts, it takes an extremely
long amount of time. This is true for Windows XP and
Windows 2000 (Win 98 does not have these startup
problems). By a long amount of time, I mean ~7-10min for
XP. After booting everything works fine, I think.

I get the following message about 30 times in the error
log each time that I boot: "The device,
\Device\Scsi\sym_u32, did not respond within the timeout
period." The device in question is my SCSI card, but I
don't know what to do about it. I've tried many
different drivers, but I can't one that works better than
the others. Please help me if you've had similar
problems or if you know what is happening. Thank you.


What devices do you have on the SCSI card? Are they all set to
different IDs? Finally are they properly terminated? If the devices
are set to the same address or if the chain(s) are not terminated you
will get problems like you mention.
 
M

Matt Cross

Michael,

I am only running a Seagate Cheetah 10k6 (ST335507LW) on
the card. It is set to ID 0 (SCSI card is set to 7). I
have the terminator that came with the card on the end of
the cable. Did I hook up the cable wrong? I have one
end plugged into the card. The next connector on the
cable is plugged into my harddrive. And I have the
terminator on the other end of the cable. Thanks for
your help.
-Matt
 
M

Michael W Ryder

Matt said:
Michael,

I am only running a Seagate Cheetah 10k6 (ST335507LW) on
the card. It is set to ID 0 (SCSI card is set to 7). I
have the terminator that came with the card on the end of
the cable. Did I hook up the cable wrong? I have one
end plugged into the card. The next connector on the
cable is plugged into my harddrive. And I have the
terminator on the other end of the cable. Thanks for
your help.
-Matt

I am not familiar with your card, but did you check for and install any
drivers for the card? Also, I am assuming that you set the drive up in
the card's bios along with making sure that termination is set up
properly on the card. On the Adaptec cards I am familiar with you need
to set termination for auto for any connectors that are not used.
Finally, the cable to the drive should be a LVD cable that has a
built-in terminator on the one end. The cable should not have any open
connectors -- if you only have the one drive it should have one
connector for the controller and the other end should have the connector
for the drive and then the terminator.
Beyond this you might want to check with the experts in
comp.periphs.scsi. Good luck.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top