Technical article 100093

ARCserve/Open won't find my SCSI tape drive when my boot hard disk is on an IDE/EIDE controller.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4

Written · Last revised

Problem

There are no tape devices on the IDE controller (ARCserve/Open only
supports tape devices on a SCSI adapter) and the boot hard disk is
on the IDE/EIDE controller.  The tape drive is on a separate SCSI
adapter.  When a status 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.

Cause

By default, the ARCserve (chey) driver is configured to look for the first SCSI host adapter (usually with the boot Hard Drive). Since the wd device entry is seen as a SCSI adapter by ARCserve/Open, no tape drive will be found and ARCserve/Open will not search for another adapter.

Solution

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

For example, on a system using an IDE "wd" controller as the host adapter with the boot hard drive attached to it, and an Adaptec 2940 (alad driver) as a second host (but first SCSI) adapter with an external tape device, replace the following line in space.c:

extern int wd_entry();
with:
extern int alad_entry();
In this example, the wd controller has no attached tape device
(and ARCserve/Open does not support IDE tape devices).  The line
"extern int wd_entry();" is not necessary.

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

extern alad_entry();
In this example, since the tape device is on the first Adaptec 2940
(alad) controller 0, bus 0, scsi id 2, and lun 0, change "wd_entry"
to "alad_entry"  in the "/* Host adapter entry point */" field of
the "/* 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 alad_entry();  <---NOTE: This is where wd_entry() was replaced with
                                    alad_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 */
        alad_entry,             /* Host adapter entry point */  <---NOTE: Change
                                       all wd_entry lines to alad_entry
        (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 */
        alad_entry,             /* Host adapter entry point */  <--- NOTE: This
                                       is where the wd_entry for ID 2 is
                                       replaced with alad_entry.
        (paddr_t)0x0            /* Extensions to SCSI */
        },
/* SCSI ID 3 */
        {
        0x3,                    /* Device index */
          .....
etc...
          .....
        },
/* No more */
        { 0xFF }
};

After making the changes to the space.c file, the UNIX kernel must be relinked and the system rebooted for the changes to take effect.

NOTE:     These releases of ARCserve will support a total of 7 SCSI tape
          devices, each on separate and unique SCSI ids, up to a 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.

See also

TA100114 "ARCserve/Open can't contact the tape devices on the system."

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

From the Xinuos technical article database, record 100093. Reproduced with permission. The original is at www.sco.com/ta/100093, 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.