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

                     Array1000U2 Family v4.20

                          Release Notes

                           Jan 25, 1999

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

This file contains the following:

  - WHAT IS IN Array1000U2 FAMILY V4.20

  - COMPATIBILITY NOTES FOR ADAPTEC Array1000U2 FAMILY PRODUCTS

  - HARDWARE INSTALLATION NOTES

  - SOFTWARE INSTALLATION NOTES

  - WINDOWS 2000 BETA NOTES

  - TIPS

  - KNOWN PROBLEMS

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

WHAT IS IN Array1000U2 FAMILY v4.20

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

PACKAGE CONTENTS
----------------
BIOS & Driver Selection Utility                - v4.20      
ARRAYCONFIG                                    - v4.20      
NT, Netware Driver Disk A                      - v4.20     
NT, Netware Driver Disk B                      - v4.20     
Unixware Driver Disk A                         - v4.20     
Unixware Driver Disk B                         - v4.20     
Windows 2000 Driver Disk A                     - v4.20     
Windows 2000 Driver Disk B                     - v4.20     
CI/O Managment Software 4.0                    - v4.00      

PRODUCT FEATURES
----------------
Array1000U2 is a release of Adaptec's low end RAID product family.
This product supports systems running Windows NT 4.0, NetWare 4.11,
5.0 and Unixware 7.0

The following features are included:
   RAID levels 0, 1, 5, and 0/1
   AAA-130U2 series array adapters
   ARO-1130U2 RAID Option Card supporting:
        AIC-7896, AIC-7890, AIC-7895B2, AIC-7895C or AIC-7880B 
        motherboard SCSI
   Selection Utility for automatic flashing of proper BIOS
        and selection of proper driver disk (A or B)   
   CI/O Management Software v4.0
        S.M.A.R.T. disk drive predictive failure notification
        SAF-TE enclosure management support
        SNMP
        DMI Version 2
   INT13 Extensions and VDS
   BIOS Boot Specification support

The Adaptec Array1000U2 Family of PCI RAID adapters currently consists of

   1 : ARO-1130U2 RAID on the motherboard
   2 : AAA-131U2 One channel RAID adapter
   3 : AAA-132U2 Two channel RAID adapter
   4 : AAA-133U2 Three channel RAID adapter

The diskettes include Adaptec Array1000U2 Family Manager Set drivers
for the following operating systems:

   Driver CDA1000.SYS for Windows NT Workstation and Server
   Driver CDA1000H.HAM for Netware 4.11 and Netware 5.0
   Driver CDA1000 for UnixWare 7.0

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

COMPATIBILITY NOTES FOR ADAPTEC Array1000U2 FAMILY PRODUCTS

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

NETWORK CARD CONFIGURATIONS
---------------------------
Some uncommon network card configurations may cause the array
configuration to hang. If the array configuration utility hangs,
check for conflicts with the network card configuration.

MEMORY ERRORS WITH AHA-2940
---------------------------
Memory errors or other problems may be experienced if both AHA-2940
and Array1000U2 Family product coexist. To solve this problem,
upgrade the AHA-2940 BIOS to the most recent version, v1.24 or later.
If both ARO-1130U2 and the AHA2940 are installed in the same system,
one of the cards may not be visible by the operating system. This
problem is caused by the system BIOS. Correct this problem by
enabling the shadow RAM for all the address ranges in the system
BIOS setup.

EZ-SCSI 4.0 & 5.0 SUPPORT
-------------------------
EZ-SCSI is not supported on Array1000U2 products, however,
ASPI8DOS.SYS is required for NetWare operations and is provided as
part of this product. If ASPI8DOS.SYS is already installed, it
should be upgraded to the version provided in the DOS directory of
the Array1000U2 FMS driver diskette.

ATI VIDEO CARDS
---------------
All ATI SVGA drivers may conflict with CDA1000 drivers under Windows
NT. Use only standard VGA drivers with an ATI video adapter card
under an NT environment.

SHARING PCI INTERRUPTS
----------------------
Do not configure the system to share interrupts between the
Array1000U2 Family product and any network interface cards (NICs) in
the system. Refer to the system BIOS manual for information on how
to configure PCI interrupts, or change the PCI slot in which the NIC
is installed.

PROPER SCSI TERMINATION
-----------------------
It is important to properly terminate both ends of the SCSI bus for
the ARO-1130U2 card to function well. Improperly terminated SCSI
buses can still operate under lightly loaded situations (only a
couple of drives.)  SCSI bus scans will generally work, and find
all devices even if termination is incorrect. Under heavy workloads,
improper termination leads to SCSI bus errors and data corruption.
Refer to motherboard/system documentation for termination
instructions.

REMOVABLE DEVICES AS PART OF A RAID ARRAY
-----------------------------------------
Removable storage media devices cannot be part of a RAID array.

IOMEGA ZIP, JAZ DRIVES AND MO DRIVES
------------------------------------
In order for the drive connected to the ARO-1130U2 to be recognized 
as a disk device, media must be in the device at boot time.

HIGH PERFORMANCE CD-ROM DRIVES
------------------------------
Active termination may be required with CD-ROM Drives supporting the
FAST SYNCHRONOUS (10MB/sec) negotiation or higher.  In general,
failing to install proper termination or incorrectly setting
negotiation speeds within SCSI Select may affect CD-ROM function-
ality, resulting in installation and CD-ROM access errors. Consult
your CD-ROM drive vendor for proper termination information.

MS BACKOFFICE ON INTEL LANCEWOOD
--------------------------------
There is an incompatibility between MS Backoffice SBS and Lancewood 
that causes the system to hang during installation.

The problem appears to be related to the NIC chip on the mother
board. Using a PCI NIC card solves the problem (the on-board NIC 
can be ignored).

SCSI CD-ROM ON INTEL LANCEWOOD SYSTEMS
--------------------------------------
SCSI CD-ROM is not supported on Intel Lancewood Systems.

ARRAY1000U2 WITH 2940 ON NT
----------------------------
Specifying more than one 'additional' device during Windows NT 
installation may cause NT to prompt the user for driver disks in the 
improper order.  For example, if an Array1000U2 driver and a 2940U2 
driver are specified (in that order) as additional devices, when 
Windows NT later attempts to copy these drivers to the hard disk, it 
prompts the user to insert the floppy containing the 2940U2 driver.  
This occurs even though Windows NT is actually expecting the 
Array1000U2 driver.  As a work around, simply inserting the 
Array1000U2 driver disk solves the problem.  An alternative solution 
is to specify only one additional device, install the OS, then later 
use the Control Panel options to add other devices.

ARRAY1000U2 WITH 2940 ON NETWARE
---------------------------------
There is a conflict between AHA2940 and CDA1000H driver with AIC 7895B
on the mother board. Netware cannot load one of these drivers if one
is already in use. This problem occurs if both drivers are selected
during installation. This problem is scheduled to be fixed in the 
AHA2940.HAM driver.

BIOS, CONTROL PANEL, AND CI/O CONFIGURATION VIEWS
-------------------------------------------------
The BIOS, the Control Panel, and CI/O have different models of the
hardware configuration and may display slightly different views.
The BIOS is independent of the device driver and displays the
configuration at the SCSI device level. Once the system has booted
the Control Panel and CI/O use the Array1000U2 device driver to
get configuration information. The Array1000U2 device driver will
manage all the SCSI channels that are attached to the same PCI bus
as the ARO. The Control Panel will repetitively display the host 
adapter for each SCSI chip it controls even though there is a single 
adapter. CI/O understands the RAID model and displays the adapter only 
once.

For example, an ARO controlling a two channel SCSI chip where one
channel has two SCSI devices attached and the second channel has 
three SCSI disks attached as a RAID5 set would be displayed:

     By BIOS
          BIOS v4.20 with
          Chan A: 2 SCSI devices
          Chan B: 3 SCSI devices

     By the Control Panel
          Adaptec Array1000U2 Family Adaptec
               BUS #0: SCSI device 1
                       SCSI device 2
               BUS #1: Adaptec RAID5
          Adaptec Array1000U2 Family Adaptec
               No device
        
     By CI/O
          Adaptec ARO-1130U2
               Channel A - SCSI
                       SCSI device 1
                       SCSI device 2
               Channel B
                       Adaptec RAID5

BIOS AND BACKPLANE CONFIGURATION
--------------------------------
On Backplanes that do not allow Wide negotiation and Sync negotiation
to be set before issuing a SCSI INQUIRY command the BIOS will not
display the Backplane configuration. The Backplane will be available
once the system has booted and will be visible through CI/O.
 
ENCLOSURES IN DUAL CHANNEL MODE
------------------------------- 
Models of nStor CR8e enclosures or other enclosures which include a 
dual SCSI bus architecture may exhibit system problems when used in 
dual channel mode. SAF-TE enclosure management may cause system abends in this
mode. These enclosure models will work in single channel mode.
  
**********************************************************************

HARDWARE INSTALLATION NOTES

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

HARDWARE INSTALLATION - ARO-1130U2 CARD CONFIGURATION INFORMATION
-----------------------------------------------------------------
When installing or re-installing the ARO-1130U2 hardware into the
system, SELECT OPTION "YES" for Reset System Configuration in the
system BIOS setup. This ensures all configuration/resources are
built properly for the current hardware in the system.

FLASHING: AAA-130U2 SERIES
--------------------------
Specific system configurations fail to allow the AAA-130U2 Series
BIOS to be flashed (with the Array10000 BIOS & Driver Selection
Utility.)  To remedy, follow the specified work around chart below.

                                              SYMPTOM/
 SYSTEM                 WITH HARDWARE         WORK AROUND DESCRIPTION
 ------                 --------------------   ----------------------
 Dual Pentium II        ANA-6944 + AAA-13xU2  Remove ANA-6944 prior
 IBM Netfinity 3500                           to running flash
 IBM IntelliStation                           utility
 Intel DK440LX

BOOT FAILURE: (PCI CARD SLOT ORDER) AAA-130U2 SERIES
----------------------------------------------------
Certain systems are sensitive to the order in which PCI cards are
scanned by PCI Memory during boot up. If PCI cards are installed in
the wrong order, some systems may not see the AAA-130U2 Series BIOS
and therefore fail to boot (hanging the system). To remedy, re-order
the PCI cards and re-boot.

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

SOFTWARE INSTALLATION NOTES

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

BIOS INSTALL
------------
The Array1000U2 BIOS will run its self-test diagnostic upon
power-on. However, it will not install unless at least one 
device is attached to the Array1000U2 family product. 

INSTALLING NETWARE 5.0
----------------------
There is a known limitation that if the SMP module is selected during 
installation, NetWare 5.0 will hang.  The reason is that NetWare 
fails to handle interrupts after driver initialization. To overcome 
this problem, do the following:
1. During installation NW 5.0 brings up a menu for selecting
    - Platform Support Module
    - HotPlug Support
    - Storage Adapters
2. Deselect any SMP module listed under the Platform Support Module.
3. Complete the installation.
4. Reboot the system and install the SMP module from the NWConfig 
   screen.

INSTALLING UNIXWARE 7.0 WITH IDE
--------------------------------
On some machines, installing Unixware 7.0 by using the IDE cdrom
causes a system panic while loading the ATAPI IDE cdrom driver.

You can workaround this problem by changing the settings of the 
system CMOS from AUTO to CDROM:
     Power on the system.
     Enter the System CMOS setup screen.
     Under the "Main" menu option, select "Secondary IDE Master".
     Hit <Enter>.
     Change the "Type" from 'Auto' to 'CD-ROM' by following the 
     on-screen instructions.
     Save the new settings and reboot the system.

UNIXWARE 7.0 INSTALLATION ID
----------------------------
Currently the UnixWare driver supports installation on ID7 only. All
channels on the system must be at ID7. 

HARDWARE REQUIREMENTS FOR UNIXWARE 7.0 INSTALLATION
---------------------------------------------------
Unixware 7.0 requires that the RAID host adapter be present, and that 
at least one drive be connected if the Array 1000U2 driver is 
installed. The installation will hang if these conditions are not met.

UNIXWARE INSTALLATION WITH RAID BOOT ARRAY SPANNING MORE THAN ONE BUS
---------------------------------------------------------------------
The system must be installed with all of the members of the RAID array 
on the primary bus.  After the installation media is installed, the 
operating system will reboot and rebuild a kernel.  The system will 
then reboot automatically, and at this point the members of the array 
may be moved to another channel.  NOTE: the primary member of the 
array must remain on the primary bus, and the ID must not change.  If
the ID of the primary member changes, the machine will not boot until 
that member is restored to its original ID.

UNIXWARE INSTALLATION WITH MPIO DRIVER
--------------------------------------
The mpio driver (Multi-Path I/O) is not needed for normal operation of 
the cda1000, and should be disabled.  The driver can be turned off by 
the following operations:

# cd /etc/conf/sdevice.d
edit mpio and change the Y in the second column to an N
# cd /etc/conf/bin
# ./idbuild
reboot the machine

The mpio driver is designed to interface to multi port devices.  The 
driver attempts to determine whether the drive is a dual ported device 
by checking a magic, "unique", value that is stored on the drive near 
the super block. Drives that match this magic value, are seen as dual 
ported drives. If the user has more than one drive with the same magic 
value, these drives will be seen as the same drive, even though they 
are not physically identical.

Please consult the SCO documentation before enabling this feature.

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

WINDOWS 2000 BETA NOTES

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

Windows 2000 drivers are included for those doing early development on 
the Windows 2000 beta software.  These drivers are specifically for 
Windows 2000. Because of changes in the Windows NT driver data 
structures, the drivers are not compatible with Windows NT 4.0. 
Conversely, the Windows NT 4.0 drivers will not work on Windows 2000.

The driver installation and driver execution have been tested under
several versions of the Windows 2000 release. The following instructions 
work best under Windows 2000 Build 1877. The instructions are for a non 
bootable array. Windows 2000 has changed the installation procedures for 
bootable devices from NT 4.0 so that bootable drivers that are not on the
Windows 2000 CD will not install.

Installation Notes
------------------
To install the ARO RAID adapter, the RAID driver, and create a non 
bootable array, do the following:

  1. Insert a Adaptec 2940 SCSI host adapter or other SCSI adapter
     in the system. The host adapter must have a corresponding device
     driver on the Windows 2000 CD.
     Do not install the ARO RAID adapter.

  2. Install Windows 2000 Workstation using the Adaptec 2940 adapter 
     or other SCSI adapter. 

  3. Add the RAID driver using the Hardware Wizard under Windows 2000 
     using the appropriate driver diskette:
          Driver disk A for motherboards with 
               AIC-7896, AIC-7890, AIC-7895C, or AIC-7880B
          Driver disk B for motherboards with 
               AIC-7895B2

  4. Modify the C:\boot.ini file to include the /PCILOCK switch. To do
     this:
          1. Make the boot.ini file writable. At the DOS prompt type
             attrib -r -s -h boot.ini
          2. Edit the boot.ini file to include the line
             multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows NT 
             Workstation Version 5.0" /PCILOCK 

  5. Shutdown the machine.

  6. Insert the ARO card and attach to the ARO adapter the SCSI boot 
     drives and other drives that were present on the SCSI adapter. 

  7. Remove the Adaptec 2940 or SCSI adapter card.
 
  8. Place the Array1000BIOS & Driver Selection Utility diskette in
     the drive and reboot the system.

  9. Flash the BIOS onto the ARO RAID adapter using the flash utility. 

 10. Remove the Array1000BIOS & Driver Selection Utility diskette from
     the drive and reboot the machine. The system is now under control
     of the Windows 2000 OS using the ARO adapter driver to control the
     disks as non RAID disks.

 11. Bring up the management software tool, CI/O, to configure an
     array. Do not configure the system disk containing the Windows
     2000 software as part of the array.

Earlier Builds of Windows 2000 
------------------------------
Builds 1940 and 1942 of Windows 2000 changed the behavior of one of the
OS calls used during initialization that prevents installation of bootable
drivers that are not part of the Windows 2000 CD.

Technically, the problem is that the driver is given the same I/O base 
address for both the SCSI and XOR chips by the O.S. Curing initialization,
The driver makes a ScsiPortGetBusData/ScsiPostGetDeviceBase call and
gets the same base  address for both chips even though the chips are not 
on the primary PCI bus, but are behind a PCI bridge. As a result, the
installation hangs.

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

TIPS

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

INITIALIZING THE ARRAY
----------------------
If the user has created the array without initializing it, and reboots
the system, the state of the array will be reported as:
        "New array needs init, needs system reboot"
A reboot at this point is not required.  One can initialize the array,
and the array will become fault tolerant.

NT SYSTEM PARTITION LIMITATIONS
-------------------------------
The following information was obtained from Micrsoft's Support WEB
site. For further information see:

     http://support.microsoft.com/support/kb/articles/q137/4/74.asp 

The information in this article applies to:	
     Microsoft Windows NT Workstation versions 3.5 and 3.51	
     Microsoft Windows NT Server versions 3.5 and 3.51	
     Microsoft Windows NT Workstation versions 4.0	
     Microsoft Windows NT Server versions 4.0

When you attempt to install Windows NT on a computer with some 
SCSI controllers, using two or more drives containing free space, 
Windows NT does not allow creation of partition sizes larger than 
1 gigabyte (GB).The text mode setup restricts Partition 0 on the 
first disk to 1024 cylinders - if there are no partitions, 
partition 0 is the free space on the drive, so the drive appears 
in the listing limited to 1024 cylinders non-translated. If you 
create a partition during setup, reboot and delete it, the 
same check is not performed again, so the size of the partition 
(Partition 0) is added onto the free disk space and you can make 
a partition that spans the whole drive up to 4GB or 1024 cylinders 
worth of data which ever is less.

-OR-

Using MS-DOS, create a partition using FDISK.  During NT Setup, 
delete the partition created with MS-DOS.  This will allow Windows 
NT Setup to create a system partition larger than 1 GB, but limited 
to 4 GB or 1024 cylinders worth of data, whichever is less.

RISKS & BENEFITS OF DRIVE WRITE-BACK CACHING
--------------------------------------------
Most disk drives allow write-back caching which greatly speeds up
writes to disks.  This feature enables an application program to
continue executing once write data is successfully sent to a
drive.   In very rare cases a deferred write error can occur
(for example, because of a parity error within the drive cache
memory).  A deferred write error means data has been incorrectly
written and is no longer available to the I/O system.  The error
is unrecoverable. The consequence of turning off the write cache
on the drive is slower write performance, but deferred write errors
are prevented.

OFF LINE ARRAY CACHE SETTINGS
-----------------------------
If an array with enabled cache goes off-line, that cache is not
returned to the "available" memory pool.  This causes a bad value
to be displayed for "Internally used" cache.  To correct this
situation, simply delete or reactivate the off-line array.

FLUSHING THE CACHE
------------------
The driver can flush the cache and clear the 'dirty' bit on the
reserved sectors only when it receives a shutdown notification
from the OS. It has been observed that certain versions of Windows NT,
such as the Enterprise Edition Server, do not issue a shutdown to an
array when it has no partitions.  (Partitions are created through the 
Disk Administrator).  The driver needs only one shutdown event, 
however, to shutdown ALL the arrays in the system.  Hence if even one 
array on the AAA/ARO has a partition, it will be sufficient to clear 
the dirty flag.  In the absence of a shutdown, or in the event of an 
abnormal reboot, the system verifies all the redundant arrays after 
first displaying the message "Unsafe shutdown detected on array xxx".

HOT SWAPPING DEVICES ON ARRAY CONTROLLERS
-----------------------------------------
Hot swapping a device with another device of a different type, but 
with the same assigned SCSI ID (for example, replacing a CD-ROM with 
a disk or vice versa) is not supported.

REINSERTION OF DEDICATED SPARES
-------------------------------
If a dedicated spare is removed by mistake, upon reinsertion and bus
rescan, it may become a single.  If this occurs, simply re-create
a dedicated spare upon that same device.

DEVICES INACCESSIBLE AFTER POWER OFF / POWER ON
-----------------------------------------------
By design, newly detected arrays, single drives, or devices will 
remain offline until the next reboot.  The device information 
structures are deleted when a device disappears, and are built
from scratch when a new one is detected.  It might appear as if 
the user is switching off and on the same drive, but to the driver 
it is a new device. 


UNIXWARE: CHANGING DEVICE ID AFTER INSTALLATION
-----------------------------------------------
To change the SCSI controller ID after installation :

# cd /etc/conf/pack.d/cda1000

edit space.c and change the CDA1000_SCSI_ID to the new SCSI ID.

# cd /etc/conf/bin
# ./idbuild -B
# ./idcpunix

reboot machine and use F6 to change the SCSI ID on the controllers.  
NOTE:  SCSI IDs for buses on the same controller must match.

UNIXWARE: DEVICE ID REASSIGNMENT
--------------------------------
Each array in the system is reported to the OS as a single large 
drive with the aggregate capacity of the member drives.  That logical 
drive representing the array is assigned a channel number and SCSI ID.
Unixware does not expect the channel number and SCSI ID of a device
to change between successive reboots. 

After a drive in an array is replaced with a spare, however, the 
driver may modify the channel and ID seen by the operating system.  
If this array contains the boot volume, the system may fail to boot. 
If it is not the boot volume, then that volume may not be mounted 
after the system boots. 

If you encounter this problem, shutdown the system and move the spare 
device to the slot/ID originally occupied by the damaged drive and 
reboot.

UNIXWARE 7.0 CONFIGURATION CHANGES
----------------------------------
UnixWare will accept changes in the configuration only after a 
reboot.  Hence, when multiple arrays are created, the system may 
require multiple reboots to insure that all new arrays are 
registered by the system and accessible to the user.  Similarly, 
if an array goes offline due to multiple drive failures, then 
following reactivation, the system must be rebooted to bring the 
array back on-line. 
 
SLOW REBOOT DURING BACKGROUND RAID MANAGEMENT OPERATIONS
--------------------------------------------------------
During the boot up process, RAID management operations may sometimes 
execute.  These background RAID operations are initiated following 
certain system events.  For example, a Verify operation will 
automatically run after an unsafe shutdown. These operations, may 
causes the operating system to take a long time to boot.  

Due to a SCSI technology limitation, SCSI commands sent to devices 
that are part of the Verify operation are given a higher priority 
than the boot device(s).  The result is that delivery of I/O commands 
may be constrained to lower-priority device ID's on the bus.

Connecting the array and the boot device(s) on separate channels, may
resolve this problem. An alternative is to boot from a higher-priority 
device ID(s).  

After resolving channel priority conflicts boot performance can be
effected by the number of boot devices and their respective priorities
with respect to the array being Verified.

Once the operating system is up, remember to:
  1) Click on the Services icon in the Control Panel.
  2) Manually start the "CIOArray Manager RPC Command" service.
  3) Manually start the "CIOArray Manager RPC Event" service.
  4) Now launch the CI/O Management Software user interface from the
     Programs group.

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

KNOWN PROBLEMS

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

ARRAY NAME CHANGE
-----------------
If array name is changed using CI/O Management Software, the change 
won't be reflected on the server until the next system reboot.  This 
occurs because NetWare refuses any change in Inquiry Data passed to 
it during Scans. 

NETWARE 5.0 LIST DEVICES
------------------------
A "list devices" command will not complete if you remove a drive 
from an existing configuration or bring down an array.

Netware 5.0 doesn't handle failure of singles or Arrays properly. 
A fix for this problem has been identified that involves the 
SCSIHD.CDM, NWPA.NLM and MM.NLM modules.  A permanent fix is planned
for Netware 5.0 Support Pack 2, scheduled for release in March '99.  
A temporary fix is available from the net at:

	http://developer.novell.com/devres/sas


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

                                  END

                        Array1000U2 Family v4.20

                              Release Notes

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