>I modified the files in newtonl to reflect the change of path
>and also to effect the change from /dev/rmt/0cn to 1cn and
>the change of change from /dev/scsi/changer/c5t4d0 to c6t4d0.
>
>The newtonr configuration is working fine.
>
>The newtonl configuration is reporting that its unable to
>deftermine the current slot.
>...
>Oddly enough amanda seems to know that I have two drives and
>is creating two separate tape access logs in /tmp/amanda (I'm
>uncertain how it knows to do this). The files are called
>
>       changer.debug.drive0 and changer.debug.drive1.

The debug file name is built based on the drive name.  So .../0cn ends
up in *.drive0 and .../1cn ends up in *.drive1.

As it happens, I think this points to your problem ...

>11:25:01 Running: mtx status
>11:25:01 Exit code: 0
>         Stdout:
>  Storage Changer /dev/scsi/changer/c6t4d0:1 Drives, 9 Slots ( 0 Import/Export 
> )
>Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag = AF6385L1  
>...
>11:25:02 Config info:
>         firstslot = "1"
>         lastslot = "9"
>...
>         driveslot = "1"

Take a look at the *.drive0 debug file.  My guess is it will say that
driveslot is "0".

Note this installation step/comment in the script:

#   * Figure out the drive slot number.  By default, the script takes
#     any digits in the tape drive device name and assumes they match
#     the robot slot number for the drive.  In the example above, the
#     tape drive ("Data Transfer Element") is in slot 0.  If the tape
#     drive device name happens to be (e.g.) /dev/rmt/0mn, the numbers
#     match and you do not have to do anything else.  If they do not match
#     (e.g. the robot number was 128, or the drive was /dev/nst3) you
#     need to set the drive slot number with the "driveslot" variable.

Since your second drive is .../1cn the script decided the drive slot was
"1" (I'm guessing here a bit, but think this is correct).  But (I think)
that's wrong.  It should be "0".  So try putting:

  driveslot=0

in your changer config file and see if that helps.

>                                               Brian

John R. Jackson, Technical Software Specialist, ITaP/RCS, jrj AT purdue DOT edu