Windows NT
How do I get rid of all the drive letters after connecting a new jukebox
to the server?
When you connect a new jukebox or changer to the server, Windows NT maps each
drive (and each LUN) to a new drive letter. This is usually not desired.
iXOS-JUKEMAN can change this behavior:
The easy way is to configure the jukebox to be attached automatically as soon
as the server starts up. This is described in "Attach devices automatically" on
page 106. After the second reboot of the server or, alternatively after
a restart of the server after the device is set up and a single
reboot of the server, this problem is solved. A more sophisticated solution to
this problem and the background of this process is described in "Frequently
asked questions (FAQ)" on page 261.
Solaris
If you connect new devices to your Solaris host, either the SCSI driver must
be reinstalled with jmsetup or the operating system must be stopped
with /etc/halt and rebooted with boot -r. to prevent it from
controlling the drives in the jukeboxes. For more information see man
vold and man vold.conf or our FAQ (Frequently Asked
Questions).
IRIX
In IRIX, the available SCSI IDs are 1 to 7. ID 0 is occupied by the
controller. The removable media manager mediad may cause problems; see
man mediad.
AIX
AIX uses a multiplex driver: You can use the devices but not see them. If you issue the following command:
ls -l /dev/iXOS_SCSI?
the output should look like this:
lrwxrwxrwx 1 root system 13 Oct 22 14:22
/dev/iXOS_SCSI0-> genscsi/scsi0
lrwxrwxrwx 1 root system 13 Oct 22 14:22
/dev/iXOS_SCSI1 -> genscsi/scsi1
This shows that the files are in fact symbolic links to our generic SCSI
driver. You can use the csh expansion mechanism `{...}' to list the
device paths created by the driver. For example the following command:
ls /dev/iXOS_SCSI{0,1}/{0,1},{0,1}
gives the following output:
/dev/iXOS_SCSI0/0,0 not found (or does not exist)
/dev/iXOS_SCSI0/1,0 not found
/dev/iXOS_SCSI0/0,1
/dev/iXOS_SCSI0/1,1
/dev/iXOS_SCSI1/0,0
/dev/iXOS_SCSI1/0,1
/dmv/iXOS_SCSI1/1,0
/dev/iXOS_SCSI1/1,1
This shows that on the first SCSI bus (/dev/iXOS_SCSI0) on IDs 0 and 1
there are two hard disks or other SCSI devices which cannot be accessed by the
operating system. The access restriction is on LUN 0 only, whereas LUN 1
normally replies to the command. Our inquiry command prints the
following:
inquiry /dev/iXOS_SCSI0/0,{0,1}
/dev/iXOS_SCSI0/0,0: Bad file number
0000000 /dev/iXOS_SCSI0/0,1 is IBM's unknown "DORS-3"
The operating system is not that restrictive for CD drives and jukeboxes:
inquiry /dev/iXOS_SCSI0/6,0
0000000 /dev/iXOS_SCSI0/6,0 is IBM's CD-drive "CDRM00203"
With the following command you can find out which IDs and LUNs are occupied by
which devices:
inquiry /dev/iXOS_SCSI{0,1,2,3,4}/{0,1,2,3,4,5,6},0
IDs and LUNs that are not used return "SCSI-Error in 00 - TEST UNIT READY")