• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SCSI HDD question?

2

2336

Elite Member
Folks,
I've got two Western Digital 18.3GB 10,000 rpm HDDs that I'm just itching to use. Just one problem, I keep getting an error message "start unit request failed" Here's the basic setup - Adaptec 19160 controller card, three connector (two device) 68-pin cable, two W-D model WDE18310-0040A3 68-pin, 10,000rpm HDDs. I've tried both HDDs on my test rig, Tyan Trinity 400 MoBo with PIII 450 KatMai core 256MB RAM, I get the same error message. If I try the HDDs singly on my primary rig I get the same error message. My primary rig is a BioStar M7NCD, Barton core 2500+, 512MB PC2700, Adaptec 19160, and HDD 0 is a Seagate 18.2 15,000rpm. I've even tried setting up my test rig with an Adaptec 2940UW and both HDDs and get the same message. Going by W-D's info there is only jumper settings for the device ID and one default jumper setting at jumpers 21-22. I've tried every device ID and tried with and without pins 21-22 jumpered and it makes no difference. I've tried to e-mail W-D about this but they don't provide e-mail support for SCSI HDDs - sheesh! I'm not a super-guru when it comes to SCSI but I thought I had a decent working knowledge. Am I missing something folks, or are these HDDs dead? Any help would be GREATLY appreciated!!! TIA!😉

Rick
 
Sounds like your drives are toasted...I checked just to make sure, but your newer adaptec card has LVD SCSI on the 68pin connector, but the older one does not have LVD, so the drives should have worked on one or the other. If you get the same error with both cards, then it may be the cable (I've had many problems with high density ATA cables, so SCSI cables may have the same issues).

hope this helps,
Red
 
Red,
I've tried using three different cables. Two of them are three connector 68-pin flat no terminator, and the third was a braided 4 connector 68-pin, with a terminator on the last connector.
 
Have you tried the working cable out of your other rig? I've had a few bad scsi cables of late. Also, are you sure the card itself is functioning properly?
 
Rick, just curious, did you go into SCSI bios and disable send start unit command and see if that made a difference? Saw that suggesting on Google

Send Start Unit Command - When set to Yes, sends the Start Unit Command to the SCSI peripheral at bootup. Enabling this option reduces the load on your computer's power supply by allowing the SCSI bus to turn on SCSI peripherals one-at-a-time when the computer boots. Otherwise, all SCSI peripherals turn on at the same time. Most peripherals require you to set a jumper before they can respond to this command.

Another reference from Adaptec for the 29160 says to check cables are snug, drives may be defective. 🙁

 
Big Lar, one of the cables I tried was the one from my working primary rig. mastertech01, John, I'll try that out tomorrow. Not sure but I think I may have tried it already. I'll try it again just to make sure.😉
 
You must have one terminator (best is an active external), and only one, at the end of each cable segment - IOW, make sure the terminations built into the drives are disabled (jumper off). Even though it is probably not necessary, I always enable the TermPower (pins 27/28 on WD) ONLY on the drive nearest an external terminator (do this only on one drive on each cable segment). Connect devices to the cable from the end in. No duplicate or skipped SCSI Id numbers.
. For your WD drives to work optimally, you should connect them to an LVD capable host adapter with an LVD rated cable and LVD rated terminator. Here are your jumper settings - The settings for the 9100 series should be the ones to use: Linkage .

Sources for cables and other SCSI stuff:
hypermicro.com (may offer free ground shipping if you mention www.storagereview.com - check the SR site for latest offer)
centrix-intl.com
pc-pitstop.com
scsi4me.com (offers PayPal as a payment option)
and I can often find stuff for low bucks on eBay.

for lots of SCSI info and links:

http://www.scsifaq.org

.bh.
 
Okay guys, here's where we're at now. I went into the SCSI BIOS and set the "send start unit command" to NO. Now upon bootup they come up as "connected but not ready." I've tried jumpering pins 27-28 on device 0, which is closest to the terminator and then turning the "send start unit command" back on and "start unit request failed" comes up again I've tried both of the above with pins 21-22 jumpered and unjumpered. This series of "tests" were run using a LVD/SE twisted pair 68-pin cable with terminator.
 
Well as nothing else seems to be working, I would maybe try letting 1 of the drives get the start command, and see what gives then.
 
Tried that as well. The one that is getting the start command still comes up as "start unit request failed", and the other one shows as "connected but not ready."
 
I was afraid of that. I just wanted to run this problem past the more knowledgeable members of the forums before I gave up. Thanks folks.🙂

Rick
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top