Hello, Hal. As I'm sure you are aware, SCA drives are mainly used in servers, where the SCA connector provides the data channels, power and the all important SCSI ID. With a regular SCSI drive, the SCSI ID is set with a small jumper block. The IDs run from 0-7 for narrow SCSI, and 0-15 for Wide. The SCSI controller itself usually takes ID7. With 5 drives in your machine already, plus the controller, chances are you have an ID conflict. If you are hooking up the SCA drive to a regular SCSI cable, you no doubt have one of those funky adapters that plugs in the back of the drive. That adapter has connectors for the SCSI cable, power, and a small group of pins for setting the SCSI ID. My own Linux box has a pair of SCA drives with exactly what I've described. Essentially, check to make sure that termination is set properly (should *only* be switched on on the devices at the ends of the chain), and that you have a unique ID for each of the SCSI devices, including the controller itself. Also, if I remember rightly, you cannot terminate an SCA device. The termination for a chain of SCA devices involves the connection of a separate terminitor block at the end of the cable. So if you have put the drive at the end of the chain, try moving it to the middle somewhere. You don't say what kind of controller you have, but on my various Adaptecs, the SCSI BIOS shows what devices are on what IDs when the machine is booted. If all the devices show up as ID7, then one of the devices is conflicting with the controller. I really hope this helps. Bye for now, Stuart.
-----Original Message----- From: Hal Schlicht [mailto:schlicht@chaffee.net] Sent: Friday, June 09, 2000 09:00 AM To: suse-linux-e@suse.com Subject: [SLE] Strange SCSI problem
Hello:
I've been running V 6.3 with no serious problems for quite some time now. My system is a Pentium II, 196 MB of RAM, 4 Seagate SCSI drives and a Hitachi 18 GB SCSI (Model DK319H-18WS) drive. As I said, my system works just fine with this configuration.
However, I bought another (new) Hitachi drive (Model DK319H-18WC) drive and now Linux won't boot with this new drive in the system. The ONLY difference between my first Hitachi drive and this new one is that the new one uses the Single Connector Adapter -- everything else is the same. The new drive has only a single small partiton (MSDOS) with no files, but Linux WILL NOT boot if it's plugged in to the system!
I'm no SCSI expert and this has really stumped me! Does anyone have any ideas?
Thanks,
Hal Schlicht
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/