Technical article 110689

SCO UnixWare7/OpenServer6:Adding a DAT Tape Auto-Changer unit

OpenServer 6.0.0UnixWare 7.1.0UnixWare 7.1.1UnixWare 7.1.2UnixWare 7.1.3UnixWare 7.1.4

Written · Last revised

Problem

I need to install a DAT Autochanger unit to my SCO Unix system. What steps do I need to take?

NOTE:     If you do run into problems, you should confirm each point of the
          equipment is functioning correctly. Try another cable, try another
          SCSI card, and try another SCO Unix system, if possible, to verify
          each component.

Solution

As an example only, here are the steps performed to add and configure an HP Model 1557A 24x6E/6i DAT Autochanger unit to a SCO Unix system. The particular tape or autochanger and SCSI adapter card may differ from your own, but the overall steps involved should be the same.

In this case, the SCSI tape unit was connected to a SCO Unix system via a SCSI III to SCSI I cable to an Adaptec 2940U2W SCSI card in the PC chassis.

The Autochanger: ================ The Autochanger used was a Hewlett Packard Model 1557A 24x6E/I unit. This contained six DAT tapes (which includes one cleaning tape) in an autochanger cartridge. The cartridge is loaded and you must then select a particular tape from this, using the front panel switches or using the SCO Unix mccntl(1M) medium changer control command.

The unit contains two roller switches at the rear, both set, in this case (as shipped), to "Autochanger Options" at 7 and "SCSI Address" at 2. The unit details are listed as:

Model HPFH-010, Part number C1558-6001, Rev E Description: HP5, 25FH, 40W, CNT, 2RS

Note that model numbers quoted can vary according to where the unit was purchased, country, shipping agent, and so on.

The unit ALSO contains dip switches under the base. These number eight in all and are all set to ON, except switch 3, set at OFF. The settings for various operating systems are listed on pages 1-10 of the unit Installation Guide documentation.

HP set the LUN of the tape to be 0 and the changer itself to be 1.

Adaptec 2940 SCSI adapter: ========================== The Autochanger is attached as mentioned above via an Adaptec 2940U2W controller card in the PC chassis. Initially, the SCSI card was installed as shipped; no settings were altered. Subsequently, it was necessary to set the card as follows:

(On system reboot, press <Ctrl>A to access the card BIOS.)

Adaptec AHA-2940U2W SCSISelect Utility v2.01.0
SCSI Bus Interface Definitions:
Host Adapter SCSI ID            7
SCSI Parity Checking            Enabled
Host Adapter SCSI Termination
        Ultra2-LVD/SE Connector Automatic
        Fast/Ultra-SE Connector Automatic
Additional Options:
Boot Device Options
        Boot SCSI ID            0
        Boot LUN Number         0
SCSI Device Configuration       (For SCSI ID 2 !)
        Initiate Sync           Yes
        Max Sync Rate           80
        Enable Disconnection    Yes
        Initiate Wide Neg       Yes
        Send Start Unit Command Yes
        BIOS Multiple LUN       Yes
        Include in BIOS Scan    Yes
Advanced Configuration Options:
        Reset SCSI              Disabled
        Extend BIOS Translation Enabled
        Host Adapter BIOS       Enabled
        Support Removable Disks Boot Only
        Display                 Enabled
        Bootable CD-ROM         Enabled
        Int13 Extensions        Enabled
Interrupt IRQ Channel           09
I/O Port Address                1400h

There are several command utilities that can be used to indicate if everything is configured and working correctly:

sdiconfig(1M)
dcu(1M)
resmgr(1M)
sdiadd(1M)
mccntl(1M)

In this example, sdiconfig was run first to see if the Adaptec 2940 SCSI card was seen by the system. On boot-up, SCSI BIOS notices are seen on the console. However, sdiconfig does not list the card; neither does dcu or resmgr. The hardware on the system can be viewed via the SCOadmin Hardware DCU utility, or you can run dcu from the command line.

As the system in this example was an IDE system, no SCSI HBA drivers were loaded at install time. To check this, run:

# pkginfo

The HBA drivers are located on CD-ROM 2 of 3 of the SCO Unix Media Kit. This can be listed by inserting the CD-ROM media into the CD-ROM drive and (as the "root" user), running the command:

# pkginfo -d /dev/cdrom/cdrom1
...
system adsa           Adaptec AIC-7770 EISA SCSI IHV HBA
system adsb           Adaptec 7800 Family PCI Ultra2 SCSI HBA
system adsc           Adaptec SCSI IHV HBA
system adse           Adaptec EISA SCSI IHV HBA
system adsl           Adaptec 7800 Family PCI SCSI IHV HBA
system adss           Adaptec AIC-6x60 SCSI IHV HBA
...
Load the Adaptec drivers using pkgadd(1M):
# pkgadd -d /dev/cdrom/cdrom1
or specify the specific one, using:
# pkgadd -d /dev/cdrom/cdrom1 adsb

The system was rebooted but the Adpatec card was not listed by sdiconfig; in this case, the adapter was not supported by the SCO Unix driver.

# sdiconfig -l
0:0,7,0: HBA     : (ide,1) Generic ESDI/IDE/ATA
  0,0,0: DISK    : Generic IDE/ESDI        1.00
1:0,7,0: HBA     : (ide,2) Generic ESDI/IDE/ATA
  0,0,0: CDROM   : SAMSUNG CD-ROM SCR-3231 S104

A 7800UNIX.EXE driver had to be obtained from the Adaptec website at:

http://www.adaptec.com/support/overview/aha2940u2w.html

These are installed on the system via floppy disk with:

# pkgadd -d /dev/dsk/f0t
The required driver in this case is the "adsb" one, but choose to
load them all. The system is usually rebuilt using idbuild(1M) for
the SCO Unix media, but for external HBA drivers this may not be
automatic. Flag that the system needs to be rebuilt on the next
reboot by typing:
# idbuild

or use "# idbuild -B" to rebuild it immediately.

The system was rebooted. Now sdiconfig shows the card:

# /sbin/sdiconfig -l
...
1:0,7,0: HBA     : (adsb,1) Adaptec PCI SCSI
...

If a controller card is installed in the system and a driver correctly supports that controller, the driver will be automatically enabled. As well as using sdiconfig, a controller can be checked using the dcu(1M) and resmgr(1M) utilities.

The driver status can be checked as follows:

# modadmin -Q adsb
Module ID: 5,           Module: /etc/conf/mod.d/adsb
Size: 192512,           Base Address: 0xc26c0000
Hold Count: 1,  Dependent Count: 0
Unload Delay: 60 seconds
Adaptec 7800 Family PCI SCSI Ultra2 HBA driver
Type:   Miscellaneous
and using:
# resmgr |pg

... 24 adsb 1 5 4 9 1400 14ff c9000 c97ff - - 4 0x90050010 0x0001 4 - 0

The SCO Unix system should now detect the SCSI card and attached
Autochanger unit. These are listed on the SCO Unix console upon
reboot and also via:
# sdiconfig -l
0:0,7,0: HBA     : (ide,1) Generic ESDI/IDE/ATA
  0,0,0: DISK    : Generic IDE/ESDI        1.00
1:0,7,0: HBA     : (adsb,1) Adaptec PCI SCSI
  0,2,0: TAPE    : HP      C1557A          U709
  0,2,1: CHANGER : HP      C1557A          U709
2:0,7,0: HBA     : (ide,2) Generic ESDI/IDE/ATA
  0,0,0: CDROM   : SAMSUNG CD-ROM SCR-3231 S10

The sdiconfig command lists the Storage devices IDs in this format:

A,B,C,D
where:

A: is the controller (host) number B: is the channel number of a multichannel device C: is the SCSI ID D: is the LUN

So, for the above, our tape is sitting on the "adsb" controller at SCSI ID 2 matching the back panel setting of the HP unit.

Accessing the Tape: =================== The tape devices are held in the "/dev/rmt" directory on SCO Unix. In this case, a typical command to copy a file to the tape failed:

# tar tv8
UX:tar: ERROR: Cannot open /dev/rmt/c0s0: I/O error

The tape unit can be queried using the mccntl(1M) command:

# mccntl -s
Drive 1 Status: MEDIA LOADED
Magazine Status: LOADED
Magazine Size: 6
Slot    Status
1       Empty
2       FULL
3       FULL
4       FULL
5       FULL
6       FULL
Load a tape first:
# mccntl -l 1
# mccntl -s
Drive 1 Status: MEDIA LOADED
Magazine Status: LOADED
Magazine Size: 6
Slot    Status
1       Loaded In Drive
2       FULL
3       FULL
4       FULL
5       FULL
6       FULL
# tar cv8 /etc/passwd
a /etc/passwd 2 tape blocks
# tar tv8
-r--r--r--  0/3      667 Nov 15 12:06 1999 /etc/passwd

The "8" corresponds to entry 8 in "/etc/default/tar" which maps to the device "/dev/rmt/c0s0".

If ARCserveIT 6.6 is installed on the SCO Unix system, remember to stop it using "# astop" before trying to use the unit, as it may be under exclusive control of ARCServeIT.

Adding the unit to a running system: =================================== The tape unit may be added to an already running SCO Unix system using the "sdiadd(1M)" utility. For example, in this case the UnixWare system was running and the tape unit was powered off but physically connected to the SCSI bus. The operating system shows:

		# sdiconfig -l
		0:0,7,0: HBA     : (ide,1) Generic ESDI/IDE/ATA
		  0,0,0: DISK    : Generic IDE/ESDI        1.00
		1:0,7,0: HBA     : (adsb,1) Adaptec PCI SCSI
		2:0,7,0: HBA     : (ide,2) Generic ESDI/IDE/ATA
		  0,0,0: CDROM   : SAMSUNG CD-ROM SCR-3231 S104

Power on the tape unit and load the cartridge of tapes. Login as "root" on the system console (press Control+SysReq+P), NOTE: it must be the console, and run the sdiadd command without any arguments:

		# sdiadd
		INFO Successfully stopped SCSI Bus
		INFO: Hit return when device changes have been made
INFO: Device added
INFO:   1:0,2,1:VOID         :HP      C1557A          U709

=> it then should list the tape changer device

The system should now see the tape:

		# sdiconfig -l
		0:0,7,0: HBA     : (ide,1) Generic ESDI/IDE/ATA
		  0,0,0: DISK    : Generic IDE/ESDI        1.00
		1:0,7,0: HBA     : (adsb,1) Adaptec PCI SCSI
		  0,2,0: TAPE    : HP      C1557A          U709
		  0,2,1: CHANGER : HP      C1557A          U709
		2:0,7,0: HBA     : (ide,2) Generic ESDI/IDE/ATA
		  0,0,0: CDROM   : SAMSUNG CD-ROM SCR-3231 S104
	  Test with "# mccntl -l 1"

If, however, I see the following WARNINGS:

Oct 15 16:00:48 WARNING:  dstat=20 on ha=2 has DS_BF, dsp=A7E8EC
dcmd_dbc=1000004 dsa=A7E8A0 dsps=37119DC0 !!!
or:

UX:sdimkdev: WARNING: Unable to clear device table /etc/device.tab, devattr failure. UX:sdimkdev: ERROR: system call error is: No such file or directory

then check:
# grep ctape1 /etc/device.tab
ctape1:/dev/rmt/c2b0t6l0:::: type="qtape" scsi="true" volume="cartridge" removable="true" pdimkdtab="true" bklib="SCSI" bufsize="65536" copy="/bin/dd if=CDEVICE1 of=CDEVICE2 bs=10240" desc="Tape Drive 1" norewind="/dev/rmt/c2b0t6l0n" erasecmd="/usr/lib/tape/tapecntl -e /dev/rmt/c2b0t6l0n" rewind="/usr/lib/tape/tapecntl -w /dev/rmt/c2b0t6l0n" rewindcmd="/usr/lib/tape/tapecntl -w /dev/rmt/c2b0t6l0n" retension="/usr/lib/tape/tapecntl -t /dev/rmt/c2b0t6l0n" display="true" inquiry="HP      C1533A          A812"

If there is no entry again then this may indicate a hardware fault and then repeat once checked.

NOTE: Troubleshooting:
Getting: mccntl: ERROR: cannot allocate buffer

This is a failure of 'mccntl' to allocate memory due a communication failure with the, typically, firmware of the tape device so it is recommended to ensure that the tape drive is running with the latest firmware.

See also

ta110287, "The UnixWare 7 adsl driver won't recognize my Adaptec 2940UW Pro host adapter."

From the Xinuos technical article database, record 110689. Reproduced with permission. The original is at www.sco.com/ta/110689, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.