Technical article 100077

I cannot access the tape device on a second Host adapter; tapesvr not starting.

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

The system has no tape device on the SCSI host adapter for the boot
Hard Drive, and the tape device(s) are on a SCSI host adapter other
than the host adapter used for the boot drive; ARCserve will not
start.  When astatus is run it returns:
tapesvr
dbserver 513 515
asod 521
aprocess

NOTE: This indicates that tapesvr and aprocess have not started since no process id is returned for either.

-OR-

The system has multiple SCSI host adapters with tape devices on any of these SCSI adapters, and the only tape device(s) shown as Destination device(s) for ARCserve are on the SCSI host adapter with the boot Hard Drive.

Cause

Normally when ARCserve starts, it will only scan the SCSI bus
of the host adapter that the boot hard drive is on for tape
devices.   If ARCserve cannot find any tape devices "tapesvr"
will not start.

By default, the ARCserve driver is configured to only look on the SCSI host adapter with the boot Hard Drive.

Solution

To change the host adapters and devices that ARCserve scans for on start-up, the file /etc/conf/pack.d/chey/space.c must be modified, and the kernel re-linked.

For example, on a system using a Compaq "cha" controller as the SCSI host adapter for the boot hard drive with no tape devices attached to it, and an Adaptec 2740 (arad driver) as a second host adapter with an external tape device, replace the following line in space.c:

extern int cha_entry();
with:
extern int arad_entry();

In this example, the cha controller has no tape device attached to it. The line "extern int cha_entry();" is not necessary.

NOTE: The space.c file text is incorrect. It says to add:

extern arad_entry();
In this example, since the tape device is on the first Adaptec 2740
(arad) controller 0, bus 0, scsi id 2, and lun 0, change "cha_entry"
to "arad_entry"  in the "/* Host adapter entry point */" field of
"/* SCSI ID 2 */" struct entry.

After making the above changes, the chey/space.c file should look similar to:

#include "sys/param.h"
#include "sys/types.h"
#include "sys/scsi.h"
#include "config.h"
extern int arad_entry();
struct scsi_dev_cfg cheycfg[] = {
/* SCSI ID 0 */
        {
        0x0,                    /* Device index */
        "chey",                 /* Device driver name prefix */
        (dev_t)106,             /* Device driver major number */
        (unsigned char)0x0,     /* Host Adapter number */
        (unsigned char)0x0,     /* SCSI Priority */
        (unsigned char)0x0,     /* Logical Unint number of the device */
        (unsigned char)0x0,     /* Used for multiprocessing purposes */
        cha_entry,              /* Host adapter entry point */
        (paddr_t)0x0            /* Extensions to SCSI */
        },
/* SCSI ID 1 */
        {
        0x1,                    /* Device index */
           .....
etc...
           .....
        },
/* SCSI ID 2 */
        {
        0x2,                    /* Device index */
        "chey",                 /* Device driver name prefix */
        (dev_t)106,             /* Device driver major number */
        (unsigned char)0x0,     /* Host Adapter number */
        (unsigned char)0x0,     /* SCSI Priority */
        (unsigned char)0x0,     /* Logical Unint number of the device */
        (unsigned char)0x0,     /* Used for multiprocessing purposes */
        arad_entry,             /* Host adapter entry point */
        (paddr_t)0x0            /* Extensions to SCSI */
        },
/* SCSI ID 3 */
        {
        0x3,                    /* Device index */
          .....
etc...
          .....
        },
/* No more */
        { 0xFF }
};

NOTE: Substitute "cha" and "arad" for device drivers specific to your system.

	  If the two controllers on your system are the same type, and your
	  tape drive is attached to the 2nd adapter (ha 1) then the change
	  in the space.c file will be to the Host Adapter Number field of the
	  struct for the SCSI ID of your tape drive.  For example, if your tape
	  drive is set to ID 2 on the second Adaptec 2940 controller, you will
	  want the /* SCSI ID 2 */ struct to look like this:
/* SCSI ID 2 */
        {
        0x2,                    /* Device index */
        "chey",                 /* Device driver name prefix */
        (dev_t)106,             /* Device driver major number */
        (unsigned char)0x1,     /* Host Adapter number */
        (unsigned char)0x0,     /* SCSI Priority */
        (unsigned char)0x0,     /* Logical Unint number of the device */
        (unsigned char)0x0,     /* Used for multiprocessing purposes */
        alad_entry,             /* Host adapter entry point */
        (paddr_t)0x0            /* Extensions to SCSI */
        },
	  Notice that the forth line of the struct has been changed from 0x0 to 		  0x1.  This will cause the chey driver to search the second Adaptec
	  2940 controller for a tape device with scsi id 2.

After making these changes, you will need to relink the kernel and reboot the system:

	  # cd /etc/conf/cf.d
	  # ./link_unix -y
	  # init 6
NOTE:     These releases of ARCserve will support a total of 7 SCSI tape
          devices, each on separate and unique SCSI ids, up to total of
          7 different SCSI host adapters. Each driver must have an
          "extern int scsi_entry" and the appropriate "/* Host adapter entry
          point */" entry for the "/* Device index */.  This means that
          ARCserve will only see one SCSI ID of devices to scan for; it will
          only scan for one SCSI id 0, one SCSI id 1, and so on. If the SCSI
          host adapter is a multi-bus adapter, the tape device must be on
          the first bus of that adapter, as ARCserve cannot scan a tape
          device on any bus except the first.

From the Xinuos technical article database, record 100077. Reproduced with permission. The original is at www.sco.com/ta/100077, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

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.