• Firmware Version: 310L
• I2OBIOS Version: 1.2Y
• SMOR Version: 1.11 Build 2A
• Storage Manager Version: 2.27
• DPTUTIL Version: 2.27

SmartRAID V

• User's Manual, DO-975-005
• Quick Install Guides, DO-998-001 & DO-999-001

SmartRAID VI

• Installation Guide, DO-1000-002
• Storage Management Software User's Manual, DO-1001-001

Information in these release notes applies equally to DPT SmartRAID V and SmartRAID VI products as of the date shown above. Please review this file for important information about compatibility issues and differences in operation that were discovered after our product documentation was printed.

NOTE: SmartRAID V and SmartRAID VI documentation (in Adobe Acrobat PDF format) are available for download at http://www.dpt.com.

In the case of conflict between various parts of the documentation set, this file (READ.ME) contains the most current information.

1. General Information (includes updates for controller configuration)
   • DPTUTIL
   • Storage Manager
   • Storage Manager on ROM (SMOR)
2. Operating Systems
   • Linux
   • Novell NetWare 4.11/4.2/5.x
   • SCO UNIX 3.2v4.2
   • SCO UnixWare 7.x
   • Windows 95/98
   • Windows NT 4.0 (with Service Pack 6 or higher)
   • Windows 2000
3. Peripheral Devices
4. Motherboards and Computer Systems
   Notes of motherboard- or system-specific compatibility issues.
5. System Compatibility
   • Incompatible host systems

DPT recommends that you install a minimum of 16MB of cache memory, especially when using RAID 5. (PM2865U3 controllers require a minimum of 32MB of cache.) Product testing also revealed that in a small number of systems, DPT controllers with 4MB of cache did not initialize correctly during the system boot process.

NOTE:   A PM2865U3 controller will use the first 16MB of cache as RAM for the i960 processor. Therefore, the reported cache will be 16MB less than the actual DIMM capacities.

Some motherboards are not able to initialize PCI to PCI Bridges and Multifunction Bridges if they are present in the same system. Therefore, these motherboards might not be able to configure both Millennium and Decade or Century controllers in the same system. See "Motherboards and Computer Systems" and "Hardware Compatibility" for additional information.

DPTUTIL, is now included with the DPT software distribution. This program is a command line storage management utility that allows you to create and manage your disk arrays from a command prompt on the following platforms:

BSDi 4.0 (go to http://www.dpt.com for availability)
FreeBSD 2.2.8 (go to http://www.dpt.com for availability)
Linux
MS-DOS 6.22 or higher
SCO OpenServer 5
SCO UnixWare 7.10
Novell NetWare 4.11, 4.2 and 5.x
Windows NT 4.0

DPTUTIL for Linux requires specific kernel versions. Refer to the Linux section under Operating Systems for a list of kernel versions supported by this release.

BSDi, FreeBSD, Linux and MS-DOS versions are available only as downloads from the DPT web site. UNIX/Linux versions include a man page for the command line parameters.

For BSDi and FreeBSD, go to http://www.dpt.com to check for availability.

SCO UNIX 3.2v4.2 and OpenServer 5

Running DPTUTIL with the -e soft parameter generates an error and non-fatal core dump.

Running DPTUTIL with the -A parameter returns data headings but does not display any data values.

You cannot use Storage Manager Remote Communication to monitor a controller on another operating system platform from a SuSE Linux 6.4 client system.

Do not attempt to perform Dynamic Array Expansion from a remote client running Storage Manager. This operation should be performed only through Storage Manager on the host system to which the array is connected.

Changes to the Background Task Priority setting are not saved for multilevel (0+1 and 0+5) arrays. The setting is saved correctly for individual RAID 0, 1 or 5 arrays. For multilevel arrays, the background task priority will always be the default value.

Storage Manager running on a UNIX client may become unresponsive during an attempt to make a remote connection. If this occurs, turn off the Num Lock key and enter the IP address information using the number keys on the top row of the keyboard. In some cases, enabling the Num Lock key and entering the IP address from the numeric keypad causes Storage Manager to stop responding.

Storage Manager may not prompt you to reboot your system after you flash a firmware image to the controller. Always shutdown your operating system and restart your computer after you download flash image files through Storage Manager to ensure the new code is effective.

The Array Group Information dialog and Logical Configuration window are not updated correctly after stopping a Verify operation. For the Array Group information window, click OK to close the window and then open it again. This new window will display the correct status. For the Logical Configuration window, select File--Read System Configuration to update the device status.

DPT Storage Manager is now available for Linux 6.x systems with the appropriate kernel version. You can download Storage Manager for Linux from the DPT web site. See the "Linux" section under "Operating Systems" for additional information.

DPT Storage Manager is not available for BSDi or FreeBSD systems. However, you can use the SMOR utility or the DPTUTIL command line utility to configure disk drives and RAID subsystems for computers that use these operating systems. See the SmartRAID V User's Manual or SmartRAID VI Storage Management Software manual for additional information about using SMOR.

The current version of the DPT Communications Engine (DPTSCOM.EXE) can support only one remote connection to a server. If you attempt to establish multiple remote connections to the same server, the DPT Communications Engine will fail with an Invalid Page Fault error. This will be fixed in a subsequent release.

When using Storage Manager under SCO UNIX or UnixWare you might experience a problem using the Help-Glossary hyperlinks. If this occurs, place the pointer slightly below and to the right of the highlighted link. Clicking to select in this location should cause the link to be activated.

A bootable version of SMOR that runs from a floppy disk is available on the DPT Technical Support web site. This version provides the same function as the controller-based utility.

When creating a RAID-1 array, SMOR will allow mirroring to a disk that is smaller than the source data disk. This can result in loss of data. Ensure that both disks have equal capacity when creating a RAID-1 array.

You cannot upgrade a controller's flash ROM from a floppy diskette on some Compaq host systems. Copy the ROM image files to a SCSI disk drive and use the files on the SCSI disk when performing an upgrade.

When using an ATI 3D RAGE video card, exiting SMOR may cause video display to become garbled. This is a problem with the video card and can be fixed by switching power to the computer off and then on.

If you get a read error message while updating the DPT controller ROM BIOS using an image file stored on an IDE or SCSI disk drive, copy the image file to a floppy disk and try the operation again.

If you are using I2ODDL.SYS with the ASPICD.SYS driver, only those CD-ROM drives attached to the first channel (channel 0) of the SmartRAID V controller are detected.

DPT-qualified I2O Drivers for the following operating systems are provided on diskette in this release:

• Novell NetWare 4.2 and 5.x
• SCO UNIX 3.2v4.2
• SCO UNIX OpenServer 5.x
• Windows NT 4.0
• Windows 95/98

I2O Drivers for the following operating systems are available from the DPT web site (http://www.dpt.com):

• BSDi 4.x (go to http://www.dpt.com for availability)
• FreeBSD 2.2.8 (go to http://www.dpt.com for availability)
• Linux (see Linux section for specific kernel versions)
• Novell NetWare 4.11
• Windows 2000

Although not released by the operating system vendors at the time of this document release, generic I2O drivers (Operating system Services Modules [OSM]) compatible with SmartRAID V or VI may be obtained from:

SCO for UnixWare 7.10
IBM for OS/2 Warp e-business.

Please contact your operating system vendor for availability of generic I2O OSMs for platforms that are not listed.

This release of DPT software is supports the following Linux kernels:

		2.2.5         2.2.13          2.2.5-22smp     2.2.14-5.0smp
		2.2.5-15      2.2.13-12       2.2.12-20smp
		2.2.5-22      2.2.14          2.2.13-smp
		2.2.10        2.2.14-50       2.2.13-12smp
		2.2.12-20     2.2.5-15smp     2.2.14-smp
		

There is an error in the Linux kernel for Red Hat 6.2 on Intel processors that can result in data corruption. Please refer to the RH62FIX.TXT file for information on obtaining and using a kernel patch from Red Hat that corrects this problem. This file is part of the Linux driver download package.

The DPT I2O driver is not copied correctly when you install an upgrade from Red Hat Linux 6.0 to 6.1. This results in a kernel panic when you restart the system. Use the following procedure to avoid this problem.

Before installing the upgrade:

1. Mount the DPT Red Hat 6.1 driver disk.

   mount -t msdos /dev/fd0/mnt/floppy

2. Extract the driver using the following commands:

   cd/lib/modules
   	      mkdir -p 2.2.12-20/scsi
   	      gzip -cd /mnt/floppy/modules.cgz | cpio -i 2.2.12/dpti2o.o
   	      mv 2.2.12-20/dpti2o.o 2.2.12-20/scsi

   For systems that use symmetric multiprocessing (SMP):

    cd/lib/modules
   	      mkdir -p 2.2.12-20smp/scsi
   	      gzip -cd /mnt/floppy/modules.cgz | cpio -i 2.2.12smp/dpti2o.o
   	      mv 2.2.12-20smp/dpti2o.o 2.2.12-20smp/scsi
   		  

3. Modify or verify that your scsi_hostadapter entries in your local /etc/conf.modules file are numbered starting with 1:

   For example:

   alias scsi_hostadapter1 eata.dma
   	     alias scsi_hostadapter2 dpt_i2o

4. Reboot and install the Red Hat 6.1 upgrade as described in the DPT redhat61.txt HowTo file.

Storage Manager for Linux 6.x requires kernel version 2.2.5 or later. See the Linux section under Operating Systems (above) for specific kernel versions that are supported.

Storage Manager for Linux with the GNOME desktop environment does not automatically update the Percent Complete status of Build, Rebuild or Verify operations when the Storage Manager window does not have the focus. When the window receives the focus it will begin updating the completion status.

You can change the default behavior of the desktop to give new windows immediate focus by changing the setting in the Window Manager configuration options for the Enlightenment window manager.

If you are using Red Hat Linux 6.0 issuing a halt command can cause the system to fail during the shutdown process. This problem occurs on various motherboards and DPT controller combinations.

DPT has determined that this problem does not occur if you disable Advanced Power Management (APM) services. If you encounter this problem, recompile the Linux kernel with the APM option disabled.

Create and build multilevel (0+1 and 0+5) arrays using SMOR. Creating multilevel arrays with DPTUTIL or Storage Manager does not initiate a build process.

If event broadcast to a Windows NT user/client is enabled under NetWare 5.x, the DPT NetWare Broadcaster will generate multiple event messages on the Windows NT client for a single event condition. DPT recommends using the Storage Manager Event Log viewer to view event messages for a NetWare server in place of broadcast messages. This problem will be fixed in a future release of the DPT Event Broadcast module for NetWare.

I2O drivers for NetWare 4.11 are not supplied on the software diskettes. You can download the driver package from the DPT web site (http://www.dpt.com).

Using a DPT SmartRAID IV or SmartCache IV controller and SmartRAID V or SmartRAID VI controller in the same system will result in the following problems if the SmartRAID/SmartCache IV controller does not have a hard disk attached:

DPTUTIL -L will not list any devices attached to the SmartRAID/SmartCache IV controller. The command will scroll blank lines and then SmartRAID V or VI devices will be listed.

A Storage Manager session from a remote client will not display any devices attached to the controllers and the remote session will freeze after the hardware scan. You will have to terminate the storage manager remote session to recover from this condition.

DPT has identified some limitations with NetWare support for I2O that requires a modified installation procedure. This modified procedure will allow the SmartRAID V or VI controller to function as a boot device and correctly support certain software utilities and disk array configurations under NetWare. DPT is currently working with Novell to resolve these issues.

The DPT NetWare diskette includes a README.TXT file (from Novell) that has instructions for installing the Novell I2O drivers.

To use a SmartRAID V or VI controller as a boot device under NetWare 4.11, you will need to use a special DOS batch file (DPT411.BAT) when installing the I2O drivers for NetWare. This batch file is available from the DPT Technical Support web site.

Go to http://www.dpt.com and access our technical support web site to download the batch file and view the latest information about installing the Novell NetWare I2O drivers for SmartRAID V or VI controllers.

The Novell SCSIOSM driver for I2O cards does not support tape or CD-ROM devices on SmartRAID V or VI controllers. The standard Novell block storage OS Services Module (OSM) will work for hard disk drives. Contact DPT Technical Support for availability of an updated NetWare OSM.

You cannot install the operating system onto an array if any non-RAID drives are present. The following workaround for this problem will allow you to install UnixWare 7.10 on an array and also have non-RAID drives after the installation.

1. Remove any non-RAID drives from the system. Leave the RAID drives installed.
2. Install the operating system on the disk array.
3. Reinstall the non-RAID drives.

During the next system boot UnixWare will assign the array a "ghost" address of 0.0.0 and disable whatever drive was previously assigned to 0.0.0. You will see a message about this change during the boot process.

To ensure correct operation with tape devices, update your UnixWare installation to version 7.10. Versions prior to 7.10 may experience problems communicating with tape devices attached to SmartRAID V controllers.

The statement in the SmartRAID V User's Manual that SCO does not support booting from a DPT controller is not correct. An I2O driver patch is available from SCO that allows you to to boot from a DPT controller.

To correct this problem, apply the I2O Mass Storage HBA Supplement (PTF7067E) for UnixWare 7. This patch is only for UnixWare 7.0.1 and 7.1.0. The patch is available from:

http://www.sco.com/support/ftplists/uw7list.html

If you you replace your existing, configured SmartRAID V or VI controller with a different SmartRAID V or VI model, when you restart your system Windows 95/98 will detect the controller as a new device. You will be prompted to choose a driver. Select the DPT miniport driver and click OK to complete the device installation.

The DPT miniport driver that you select can be a new one you downloaded from the DPT web site, the original one that came on diskette with your SmartRAID V or VI controller, or the existing one already installed on your system in C:\WINDOWS\SYSTEM\IOSUBSYS.

If you attempt to correct a DPT controller entry under Other Devices in the Device Manager using the Update Driver function your system may hang during the restart sequence. If this occurs the device update is not completed and the device will still be identified incorrectly. You may need to manually copy the DPT miniport driver (DPTI20.MPD) to the Windows \SYSTEM\IOSUBSYS directory.

DPT has determined that this indicates a problem with Windows 95/98 and the motherboard chipset (Intel FX and BX types) when attempting to identify the DPT controller. Contact your motherboard manufacturer for a chipset driver patch.

NOTE:  The controller will function normally even if there is no patch available.

For Windows 98 only
Do not delete the DPT I20 Memory Controller entry under "System devices" in Windows 98 Device Manager. Deleting this entry will cause the Windows operating system to stop responding to user input.

The I2ODDL.SYS driver may fail to load when there are no hard disk drives attached to a SmartRAID V or VI controller or if the DPT I2O BIOS is disabled. This driver is required for CD-ROM support under MS-DOS.

When a PM1564+RA4060, PM1554+RA4050, PM2554+RA4050, PM2654+RA4050 or PM3754U2 controller is installed, Windows 95 will display the controller information with conflicts in the Device Manager. However, the controller will operate normally. This problem also occurs in the Windows 98 Upgrade product, but not in the standard Windows 98 release.

When using a PM3754U2, PM1564+RA4060, PM1554+RA4050, PM2554+RA4050 or PM2654+RA4050 controller you will see two entries under Other Devices in the Device Manager: PCI Card and PCI Memory Controller. To install the DPT miniport driver:

1. Select Update Driver for the PCI Card entry.
2. Choose the DPT driver.
3. Reboot the computer.

The DPTSERV and DPTCOM modules must run as services under a user ID with Administrator privileges.

If during the installation of Windows NT 4.0, the operating system fails with a blue screen which references a "display" type error or you cannot boot the system in using a video resolution higher than 640x480, ensure that the EBDA Relocation option in SMOR is enabled.

Ensure you have installed the latest Service Pack from Microsoft for Windows NT 4 before you install a SmartRAID V or VI controller and DPT drivers.

Video corruption can occur when using a Millennium controller or a controller with an RA4050 module in a host system with a Cirrus Logic PCI video adapter. This problem occurs in any video mode other than 640x480-16 color.

The DPTSERV and DPTCOM modules must run as services under a user ID with Administrator privileges.

If during the installation of Windows 2000, the operating system fails with a blue screen which references a "display" type error or you cannot boot the system in using a video resolution higher than 640x480, ensure that the EBDA Relocation option in SMOR is enabled.

If you are upgrading to Windows 2000 from Windows NT 4 and a DPT SmartRAID controller is part of your configuration, run the W2KPREP.EXE utility before you start the upgrade. If necessary this utility makes a single modification to the Windows NT registry to ensure a successful upgrade with a DPT controller. W2KPREP.EXE is on the DPT Windows 2000 diskette.

You will be prompted to modify Administrator privileges during by the DPT setup utility. You can ignore this message. The modification is not necessary under Windows 2000 and applies only to Windows NT 4.

You cannot successfully complete installation of Windows 2000 using the floppy-based install procedure on AOpen AX5T motherboards. You must boot from the Windows 2000 CD-ROM (connected to the IDE controller or a non-SmartRAID V or VI SCSI controller) to successfully complete the install process.

Seagate hard drive models ST39204LC, ST39204LW, ST318404LC, and ST318404LW with microcode revision 002 or earlier may not be detected by DPT or another vendor's controller. Contact Seagate and obtain microcode revision 004 or higher to correct this problem.

Seagate ST136475FC disk drives with microcode version 003 can cause erratic system operation when under I/O load. This can result in the operating system failing to respond to user input.

DPT has tested microcode version 0415 which resolves this problem. This microcode is not yet released by Seagate.

nStor CR8F enclosures using Seagate ST39173FC disk drives may experience a condition that prevents some or all of the drives from being recognized by a DPT controller. If this condition occurs, use SMOR to change the SmartROM Configuration "Scan Delay" parameter from Default to 10. This will cause the controller to wait 10 seconds before scanning the bus for devices.

Ricoh Model 6200S CD-R drives may not operate correctly with SmartRAID V or VI controllers.

When you initiate a recording test using Adaptec EZ CD Creator (version 3.5), the test will fail and abort the recording session. You should be able to record data to a CD successfully if the Create function is used instead of the combined Test/Create operation.

Quantum Atlas III and IV Ultra2 SCSI disk drives are not compatible with the DPT PM3755U2B controller. If you attach these drives to this controller, a condition will occur that prevents the drive from being identified by the controller firmware, and consequently by SMOR and Storage Manager. This problem is specific to the PM3755U2B controller.

A Dell PowerEdge 1300 system will hang during Windows NT boot if a SmartRAID VI Decade controller is installed in PCI slots 4 - 6. To avoid this problem, install the SmartRAID VI controller in slots 1 - 3 only.

A Supermicro S2DGU motherboard, Pentium III 550 MHz, AMI BIOS R1.5 with a SmartRAID VI Decade controller will stop responding if you attempt to enter SMOR using Ctrl+D during the system boot.

Use Alt+D during system boot to start SMOR on this system.

A Soyo SY-6BE motherboard with a SmartRAID VI controller that has 4MB of cache can experience erratic operation and possible data loss. This problem does not occur if the controller has 16MB or more of cache memory.

Iwill BD100 motherboards using Award BIOS 4.51PG (Iwill release 31310A) are not compatible with DPT controllers that have more than 64MB of cache memory.

A computer system or motherboard does not need to be I2O compliant to support SmartRAID V or VI controllers. However, a machine that is not I2O compliant may display "Unknown PCI Device in Slot x" during it's system power-on self test (POST). Even if your system displays "Unknown PCI Device in Slot x" or something similar, your system or motherboard may still be compatible with SmartRAID V or VI controllers.

Abit BH6 and BX6 Motherboards

• This motherboard is not compatible with the PM3755U2B controller when a BB4050 module is attached. All other SmartRAID V or VI controller configurations are compatible with this system.
• PM3754U2 and PM3755F controllers will not initialize when the system is started by cycling the power off and on. Press the manual reset button on the system to correct this condition. This problem occurs only during a power-on sequence; resets or warm-boots do not cause the controllers to fail initialization.

Acer and AOpen

• AOpen MX3W motherboards (Intel Celeron and Award 6.00PG BIOS) does not reboot successfully when Windows NT 4 Service Pack 5 or 6a are installed. The system will operate normally when no service pack has been applied.
• AOpen AX59Pro motherboards using the Via MVP3 chipset will not complete power-on self test (POST) when using a PM1554 or PM2554 controller with the RA4050 module.
• Acer 930, 9100 & 21000 systems will report an IRQ Setting Error during the power-on self test (POST) when an RA4050 module or Millennium controller is present. The controller will operate normally and this error message can be ignored. To bypass this error during POST enable the system CMOS setting "No Halt on Error".
• AOpen AX5T motherboards do not complete the power-on self test when a DPT Millennium controller with more than 128MB of cache is installed. If the cache is less than 128MB, this problem does not occur.

Compaq

• Deskpro EN series systems (Compaq BIOS 686T3) will report a "101-Option ROM Checksum error" during startup if a SmartRAID VI Decade is installed in a higher PCI slot than an Adaptec AS-29160 SCSI adapter. To avoid this problem install the SmartRAID VI in a lower slot number than the Adaptec controller.
• Proliant systems do not complete initialization of SmartRAID V controllers that have less than 16MB or more than 128MB of cache installed on one controller or a total of 128MB of cache installed across multiple controllers. This problem may be corrected by a newer BIOS version, contact Compaq for information about obtaining a BIOS upgrade.
• The MWI Write option in SMOR must be disabled for Proliant systems. This can be done by unchecking the MWI Write checkbox in the SMOR HBA configuration tab. MWI Write is enabled by default.

Intel

• Systems using an Intel CC820 motherboard are unable to boot from CD-ROM when the CD-ROM drive is attached to a SmartRAID controller.
• Systems using an Intel CC820 motherboard and SmartRAID controller may not be able to access SMOR during system boot. If this occurs, reboot the system and when the second "Hit Ctrl-D" message appears, use the Alt+D key combination to start SMOR. If you are still unable to start SMOR, contact DPT Technical Support.
• Systems using an Intel SC450NX motherboard and PM1554U2, PM2564U2, PM2865U3 or PM1564U3 controller will take an extended period of time (approximately 2 minutes) to initialize. After the controller initializes, the system will continue to boot normally.
• Systems using an Intel SC450NX motherboard and multiple SmartRAID controllers will display the following message during system boot:

  PCI Expansion ROM Error Device xx Bus xx Channel xx

  for each controller except the first one. The system will continue to boot and operate normally.

• Systems using Intel SC450NX, MB440LX, N440BX, NL440BX and AK450NX motherboards will not boot successfully if:

  There are two or more SmartRAID V or VI controllers and the total cache across all controllers is greater than 320MB.

  One controller with more than 128MB of cache is installed.

  This cache limitation is caused by the Intel system BIOS; ensure that you are using the most recent BIOS version.

On some Asus motherboards if a SmartRAID V or VI controller is found first, any subsequent SmartRAID IV controllers are ignored by SMOR when a RAID accelerator is attached. This problem does not occur when a SmartRAID IV controller is the first one found or when using a PM3754U2 controller.

SmartRAID V or VI adapters are PCI Bridge devices, and if properly recognized by the motherboard or system BIOS, will be identified as a "PCI Bridge Adapter" (or something similar) during your system power on self-test.

DPT SmartRAID V and SmartRAID VI controllers are tested on a wide variety of systems which represent common motherboard, BIOS, and CPU combinations. In almost all cases the controller will initialize and operate correctly without any special intervention. Exceptions are noted in the "Motherboards and Computer Systems" section above.

The following systems have been tested by DPT and are not compatible with SmartRAID V or VI controllers:

		System                CPU/Speed (# CPUs)  BIOS and Version
		-----------------     -----------------   -----------------------------
		Acer M5               P5/150Mhz           BIOS 2.0 (ACR89E00-960308)
		Acer M15              PII/300Mhz (2)      Acer 3.0 (local R01-A0 Test 37)
		Acer Altos 9000       P5/66Mhz            Acer 2.0
		Antec MB6881          K6-2/400Mhz         Award 4.51PG
		Apricot FT4200        P6/200Mhz (2)       SurePath BIOS Version 2
		AST Manhattan         P5/90Mhz (2)        AST 1.10
		AST Premmia           P5/75Mhz            AST 2.02
		Asus P55TP4N          P5/166Mhz           Award 4.51PG-106
		Dell Omniplex         P5/90Mhz            Phoenix BIOS 1.00 A05
		HP WSB160             RISC/160Mhz         HP 999.9
		Micronics Spitfire    PII/300Mhz (2)      Phoenix 4.0 Release 6
		NetFrame NF9008       P6/200Mhz (2)       Phoenix 24.MF
		SNI Primergy 500      P5/133Mhz           Phoenix BIOS 4.04 Revision 103.A.873