Welche Hardware: Raid-5 / Scsi-Controller

Toens Bueker toens.bueker at lists0903.nurfuerspam.neuroserve.de
Thu Jul 29 20:30:18 CEST 2004


Florian Lohoff <flo at rfc822.org> meinte:

> > > > adaptec hat halt binary treiber - und der 2010S soll anders als
> > > > 2100S nicht unter woody out of the box laufen. (ZCR)
> > >
> > > sed:~# cat /proc/scsi/dpt_i2o/0
> > > Adaptec I2O RAID Driver Version: 2.4 Build 5
> > >
> > > Vendor: Adaptec  Model: 2100S            FW:FS04
> > 
> > ja eben, mit dem 2100S (voller Raid-Controller) ist es kein Problem - 
> > aber der 2010S (das ist ein total anderes Device - ohne Scsi-Chip, also 
> > zero-channel) soll nicht I20-compliant sein.
> 
> Ohne das jetzt genau im Kopf zu haben - Aber der 2100 hat auch keine
> eigenen SCSI Channels. Hmm - die webseite sagt anderes - Ok - hier eine maschine
> aus der Baureihe - Die hat definitiv keine eigenen SCSI Channels:
> 
> Loading Adaptec I2O RAID: Version 2.5.0
> Detecting Adaptec I2O RAID controllers...
> Adaptec I2O RAID controller 0 irq=24
>      BAR0 f882c000 - size= 100000
>      BAR1 f892d000 - size= 1000000
> dpti: If you have a lot of devices this could take a few minutes.
> dpti0: Reading the hardware resource table.
> TID 008  Vendor: ADAPTEC      Device: AIC-7902     Rev: 00000001
> TID 009  Vendor: ADAPTEC      Device: AIC-7902     Rev: 00000001
> TID 515  Vendor: SDR     G    Device: GEM318       Rev: 0   0
> TID 524  Vendor: ADAPTEC R    Device: RAID-1       Rev: FS13D
> TID 525  Vendor: ADAPTEC R    Device: RAID-1       Rev: FS13D
> scsi0 : Vendor: Adaptec  Model: 2010S            FW:FS13

Wir haben drei Maschinen von SuperMicro mit den
Controllern im Einsatz. Mit den raidutils von Adaptec
sieht der Output etwa so aus:

root at domina:~# /usr/dpt/raidutil -L all
RAIDUTIL  Version: 3.14  Date: 3/12/2001  LINUX CLI Configuration Utility
Adaptec ENGINE  Version: 3.14  Date: 3/12/2001  Adaptec LINUX SCSI Engine

#  b0 b1 b2  Controller     Cache  FW    NVRAM     Serial   Status
---------------------------------------------------------------------------
d0 -- --     ADAP2010S      32MB   3B05  CHNL 1.1  BB0D3130D32Optimal

Physical View
Address    Type              Manufacturer/Model    Capacity  Status
---------------------------------------------------------------------------
d0b0t0d0   Disk Drive (DASD) FUJITSU  MAP3367NC    35046MB   Optimal
d0b0t1d0   Disk Drive (DASD) FUJITSU  MAP3367NC    35046MB   Optimal
d0b0t6d0   SAF-TE            SUPER    GEM318       -----     Optimal

Logical View
Address       Type              Manufacturer/Model Capacity  Status
---------------------------------------------------------------------------
d0b0t0d0      RAID 1 (Mirrored) ADAPTEC  RAID-1    35046MB   Optimal
 d0b0t0d0     Disk Drive (DASD) FUJITSU  MAP3367NC 35046MB   Optimal
 d0b0t1d0     Disk Drive (DASD) FUJITSU  MAP3367NC 35046MB   Optimal


Address    Max Speed  Actual Rate / Width
---------------------------------------------------------------------------
d0b0t0d0   Ultra160   320 MB/sec    wide
d0b0t1d0   Ultra160   320 MB/sec    wide
d0b0t6d0   Ultra160   ?

Address    Manufacturer/Model        Write Cache Mode
---------------------------------------------------------------------------
d0b0t0d0   ADAPTEC  RAID-1           Write Back
 d0b0t0d0  FUJITSU  MAP3367NC        Write Back
 d0b0t1d0  FUJITSU  MAP3367NC        Write Back
  
#  Controller     Cache  FW    NVRAM     BIOS   SMOR   Serial
---------------------------------------------------------------------------
d0 ADAP2010S      32MB   3B05  CHNL 1.1  1.62   1.12/79I BB0D3130D32

#  Controller      Status     Voltage  Current  Full Cap  Rem Cap  Rem Time
---------------------------------------------------------------------------
d0 ADAP2010S       No battery

Address    Manufacturer/Model        FW          Serial  123456789012
---------------------------------------------------------------------------
d0b0t0d0   FUJITSU  MAP3367NC        0106 UPL0P3302B6G   -XXXX---XOX-
d0b0t1d0   FUJITSU  MAP3367NC        0106 UPL0P3302B5J   -XXXX---XOX-
d0b0t6d0   SUPER    GEM318           0    1              -------X-O-X

Capabilities Map:  Column 1 = Soft Reset
                   Column 2 = Cmd Queuing
                   Column 3 = Linked Cmds
                   Column 4 = Synchronous
                   Column 5 = Wide 16
		   Column 6 = Wide 32
                   Column 7 = Relative Addr
                   Column 8 = SCSI II
		   Column 9 = S.M.A.R.T.
                   Column 0 = SCAM
                   Column 1 = SCSI-3
		   Column 2 = SAF-TE
     X = Capability Exists, - = Capability does not exist, O = Not Supported



Wenn mir noch jemand sagt, wie man mit dem SNMP-Agent von
dem Dingen spricht, bin ich zufrieden :-)

Tschö
Töns
-- 
There is no safe distance.



More information about the Linux mailing list