[4054] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Re: Three Controller setup

daemon@ATHENA.MIT.EDU (John Gibson)
Tue Jun 2 18:51:30 1998

Date: 	Tue, 02 Jun 1998 15:45:59 -0700
From: John Gibson <john.gibson@tekelec.com>
To: Linux Raid Mailing List <linux-raid@vger.rutgers.edu>
Cc: Linux SCSI Mailing List john <linux-scsi@vger.rutgers.edu>

Luca Berra wrote:
> The Adaptec 154x should have a block of dip switches on it, one
> of 'em disables the BIOS, so it won't try to boot (i don't have
> teh manual on hand, so i don't know which one is it).

Thank you (once again) Luca.  However, I had originally left the BIOS
enabled, but the the Tech at Adaptec told me to do as you suggested.  I
disabled the BIOS and the system didn't hang during the BIOS
initialization anymore.

What it did do was load LILO: and the linux kernel off of the PCI
controller's boot disk.  But after it loaded the aic7xxx driver and
(apparently) found all of the devices on the two 2940 PCI
controllers it loaded the 154x driver and assigned (?)
the 154x controller as SCSI controller #0.  The two 2940
controllers were assigned as controllers 1 and 2.  At that point it
attempted to find the boot device at SCSI ID #0 on controller 0 (154x).
This, of course, failed as the boot device is on the 2940 controller.

Should I manually configure the SCSI subsystem?  If so, How?

Should I try different disk controllers?  If so, Which one(s)?


Any help would be greatly appreciated.


...john



note: the original post follows for completeness   jg.



Subject: 
        Three Controller setup
   Date: 
        Tue, 02 Jun 1998 09:30:17 -0700
  From: 
        John Gibson <john.gibson@tekelec.com>
     To: 
        Linux SCSI Mailing List <linux-scsi@vger.rutgers.edu>
    CC: 
        Linux Raid Mailing List john <linux-raid@vger.rutgers.edu>


Any suggestions/recommendations on the following would be greatly
appreciated:

I want to use RAID1 (mirroring) with two SCSI controllers.  I would
also like to use one of the two controllers for my cdrom and tape
drives.  I chose the Adaptec AHA-2940UW SCSI controller.

I could not get a successful SCSI subsystem recovery when I
powered down (fault simulation) the mirrored data disk which
had the cdrom and tape attached to the same controller.  (Wide
SCSI vs narrow?)  The same simulation worked okay when I
powered down the drive which did not have the tape and cdrom
on its controller.

Since I have a spare ISA slot, I moved the tape and cdrom to
an Adaptec AHA-1540B ISA card.  Now the system wants to boot
from the ISA card which, of course only has the tape and cdrom
attached to it. It seems as if the 1540 ISA card is being set
up as SCSI controller 0 and the system expects to boot
from it.  Is there some explicit configuration file(s) that I can
specify which controller is the boot controller?

I did try using a 3rd AHA-2940UW PCI card instead of the AHA-1540B
ISA card.  That seems to be fine.  Everything seems to work this
way, but I need the PCI slot.


Thanks in Advance,

....john

******************************************************************
Configuration #1

All SCSI devices recognized.  Mirror (RAID1) set up okay on data disks.  
Test partitions on /dev/sdb1 and /dev/sdd1 are 200MB.  Power down
on /dev/sdd1 causes no problems.  The system and mirror work okay.

However, power down /dev/sdb1 causes the system to hang.  It looks
as if (layman here talking) the SCSI bus tries to reset but it
never really recovers correctly.

AHA-2940UW (PCI) (Controller 0)
  |
  |
  |--{ SCSI ID=0, LUN=0: boot disk, /dev/sda, Seagate ST32272W (2Gig) }
  |
  |
  |--{ SCSI ID=1, LUN=0: data disk, /dev/sdb1, Seagate ST19101W (9Gig) }
  |
  |
  |--{ SCSI ID=4, LUN=0: tape drive, /dev/st0, Exabyte Eliant 820 }
  |
  |
   --{ SCSI ID=6, LUN=0: cdrom drive, /dev/sr0, Toshiba XM5701B }


AHA-2940UW (PCI) (Controller 1)
  |
  |
  |--{ SCSI ID=0, LUN=0: boot mirror disk, /dev/sdc, Seagate ST32272W
(2Gig) }
  |
  |
   --{ SCSI ID=1, LUN=0: data mirror disk, /dev/sdd1, Seagate ST19101W
(9Gig) }



******************************************************************
Configuration #2

All SCSI devices recognized.  Mirror (RAID1) set up okay on data disks.  
Test partitions on /dev/sdb1 and /dev/sdd1 are 200MB.  Power down
on either /dev/sdb1 or /dev/sdd1 causes no problems.
The system and mirror work okay.

However, I can't really afford the loss of the PCI slot so I tried
using an ISA card.  See config #3.
 

AHA-2940UW (PCI) (Controller 0)
  |
  |
  |--{ SCSI ID=0, LUN=0: boot disk, /dev/sda, Seagate ST32272W (2Gig) }
  |
  |
   --{ SCSI ID=1, LUN=0: data disk, /dev/sdb1, Seagate ST19101W (9Gig) }

AHA-2940UW (PCI) (Controller 1)
  |
  |
  |--{ SCSI ID=0, LUN=0: boot mirror disk, /dev/sdc, Seagate ST32272W
(2Gig) }
  |
  |
   --{ SCSI ID=1, LUN=0: data mirror disk, /dev/sdd1, Seagate ST19101W
(9Gig) }
  

AHA-2940UW (PCI) (Controller 2)
  |
  |
  |--{ SCSI ID=4, LUN=0: tape drive, /dev/st0, Exabyte Eliant 820 }
  |
  |
   --{ SCSI ID=6, LUN=0: cdrom drive, /dev/sr0, Toshiba XM5701B }


******************************************************************
Configuration #3
 
This configuration is not booting.  It seems as if the 1540 ISA card
is being set up as SCSI controller 0 and the system expects to boot
from it.  Is there some explicit configuration file(s) that I can
specify which controller is the boot controller?


AHA-2940UW (PCI) (Controller 0: desired)
  |
  |
  |--{ SCSI ID=0, LUN=0: boot disk, /dev/sda, Seagate ST32272W (2Gig) }
  |
  |
   --{ SCSI ID=1, LUN=0: data disk, /dev/sdb1, Seagate ST19101W (9Gig) }
 

AHA-2940UW (PCI) (Controller 1: desired)
  |
  |
  |--{ SCSI ID=0, LUN=0: boot mirror disk, /dev/sdc, Seagate ST32272W
(2Gig) }
  |
  |
   --{ SCSI ID=1, LUN=0: data mirror disk, /dev/sdd1, Seagate ST19101W
(9Gig) }
  

AHA-1540B (ISA) (Controller 2: desired)
  |
  |
  |--{ SCSI ID=4, LUN=0: tape drive, /dev/st0, Exabyte Eliant 820 }
  |
  |
   --{ SCSI ID=6, LUN=0: cdrom drive, /dev/sr0, Toshiba XM5701B }


******************************************************************

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post