Re: how to slave scsi drives?
If you are to boot from this drive, your BIOS must be enabled on the SCSI
controller. To set the ID on a barracuda (newer ones, anyway), there are
two sets of ID jumpers. If facing the drive from the back, you have pins
like so:
=================== :::::: /****\
8421
(where ==== is SCSI connector, ::: are pins, and /****\ is power connector)
On the front, with drive upright, facing front:
-------------------- [ ]::::::
8421
(where ---- is circuit board, [ ] is a block, and ::: are pins)
Put jumpers on the proper pins to total whatever SCSI ID you need. Your
lower drives under Linux are the lowest SCSI ID, ie: in a system with a HDD
on ID 0, a CDROM on ID 3, and another HDD on ID 5, ID 0= /dev/sda,
ID 5=/dev/sdb. If another is added on ID 1, for example, ID 5 gets bumped
to /dev/sdc, and ID 1 becomes /dev/sdb.
There is no master/slave combination in SCSI. In IDE, the controller on
the master drive addresses the slave drive, in SCSI the SCSI interface card
addresses all drives by ID.
--
Kevin Blackham 801-539-0852
Senior Tech, XMission Internet 877-XMISSION
spin@xmission.com 877-964-7746
http://www.xmission.com/help
On Tue, May 02, 2000 at 01:17:37AM +0800, Erik Peter P. Abella wrote:
> Hello All,
>
> I'm trying to migrate my current system on ST34520LW (Seagate) on to a
> Barracuda that I don't know how to slave. I don't have this problem with IDE
> hardisks because toggling the drive status from slave to master is done
> simply by transferring a single jumper. On my Barracuda, I see some pins in
> the front that would accomodate a fairly small jumper and a large jumper at
> the back (J6?) that covers 8 pins. I tried toggling it to change the SCSI-ID
> but the AHA-2940UW BIOS only detects one drive (and the HDA itself) and
> still can't detect the Barracuda.
>
> Some input will be greatly appreciated.
>
> Cheers,
>
>
> Erik Peter P. Abella
>
>
> --
> To UNSUBSCRIBE, email to debian-isp-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: