Problem
The system was installed from an IDE CD-ROM device. There are no tape devices on the IDE controller (ARCserve/Open only supports devices on SCSI adapters) and the boot hard disk and tape device are on the same SCSI host adapter. When I try to access the tape device through ARCserve, I get "cannot access tape devices". The tape device can be accessed from the UNIX command line with no problems.
Cause
By default, the ARCserve/Open from Cheyenne driver is configured
to look on the SCSI host adapter with the boot hard disk when
searching for devices. The /etc/conf/pack.d/chey/space.c file
should reflect this. However, on some systems (usually COMPAQ)
with IDE CD-ROMs, ARCserve gets configured to search the IDE
controller. That is, the space.c file gets set up incorrectly
such that it tells ARCserve to search the IDE controller for
devices. ARCserve will not find any there, and will not search
the other host adapter(s). Solution
To change the host adapter(s) ARCserve scans for devices, the file /etc/conf/pack.d/chey/space.c must be modified. A detailed description of the modifications follow. However, a quick solution for systems with only one SCSI host adapter would be to modify space.c so that all occurrences of the string "wd_entry" (where wd is the IDE controller driver) are replaced with, for example, "cha_entry" if your system has a Compaq Fast SCSI "cha" controller. Or if your system has an Adaptec controller with alad driver, "wd_entry" would be globally replaced with "alad_entry". After making these changes, the kernel needs to be relinked, and the system rebooted (commands for relinking and rebooting are listed below). For a more detailed description of the modifications, read on.
In this case, where the system is using an IDE "wd" controller for the CD-ROM, and a Compaq Fast SCSI "cha" controller for the boot hard disk and tape device, replace this line in space.c:
extern int wd_entry();with:extern int cha_entry();In this case, the wd controller has no attached tape devices (and ARCserve/Open does not support IDE tape devices), so the "extern int wd_entry();" is not necessary.
NOTE: The space.c file text is incorrect. In this case, it says to add the line:
extern cha_entry();If you have multiple SCSI host adapters with different drivers, each driver must have an "extern int scsi_entry();" declaration in order to define a struct entry for a device off that controller. For example, if you had a second SCSI host adapter (Adaptec "alad" controller), you would add the line:
extern int alad_entry();The space.c file defines a seven-element structure describing the (up to) seven SCSI devices ARCserve can access (up to seven different SCSI host adapters). Each struct entry (numbered 0-6) corresponds to a device with a SCSI id that matches the struct entry number. Struct entry 1 describes a device with SCSI id 1, struct entry 2 describes a device with SCSI id 2, and so on. Therefore, each device ARCserve accesses must have a unique SCSI id even if it is on a separate host adapter. Part of each struct entry defines the host adapter number and host adapter entry point for the device.
Find the struct entry(s) that correspond to the SCSI device(s) you want ARCserve to access. For example, if the tape device you want ARCserve to access is on the first Compaq Fast SCSI "cha" controller at SCSI id 2, you will need to change "wd_entry" to "cha_entry" in the "/*Host adapter entry point*/" field of the "/*SCSI ID 2*/" struct entry. The updated entry would look like this:
/* SCSI ID 2 */{
0x2, /* Device index */
"chey", /* Driver name prefix */
(dev_t)142, /* Driver major number */
(unsigned char)0x0, /* Host Adapter number */
(unsigned char)0x0, /* SCSI Priority */
(unsigned char)0x0, /* LUN of the device */
(unsigned char)0x0, /* Used for MP purposes */
cha_entry, /* Host adapter entry point */
(paddr_t)0x0 /* Extensions to SCSI */
},If you also had a tape device on the second host adapter (an Adaptec "alad" controller), with SCSI id 6, you would need to change the "0x0" to "0x1" in the "/* Host adapter number */" field and "wd_entry" to "alad_entry" in the "/*Host adapter entry point*/" field of the "/*SCSI ID 6*/" struct entry. The updated entry would look like this:
/* SCSI ID 6 */
{
0x6, /* Device index */
"chey", /* Driver name prefix */
(dev_t)142, /* Driver major number */
(unsigned char)0x1, /* Host Adapter number */
(unsigned char)0x0, /* SCSI Priority */
(unsigned char)0x0, /* LUN of the device */
(unsigned char)0x0, /* Used for MP purposes */
alad_entry, /* Host adapter entry point */
(paddr_t)0x0 /* Extensions to SCSI */
},For each driver entry added to the space.c file, ensure the corresponding line in /etc/conf/cf.d/mdevice includes a capital 'B' in the third column.
For example,alad I iHh alad 0 0 1 2 -1
should become:alad I BiHh alad 0 0 1 2 -1
After making the changes to space.c and mdevice, save the file, relink the kernel, and reboot the system.
# cd /etc/conf/cf.d
# ./link_unix
# shutdown -g0 -yARCserve/Open should now be able to access your SCSI tape device.
NOTES: For multi-bus host adapters, ARCserve will only scan the first bus
(bus 0) of the host adapter. 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."