previous - next - up - title - contents - index

3.5.4 Device description files


A device description file contains lines in the format <key>=<value>. Some keys must be specified for all devices, others must be specified only for certain types.

Device type set-up

The most important parameter is the device type: device=<type>.
The supported jukeboxes and their types are listed in the following table.

Table 3 - Device types for all supported jukeboxes

Type

Jukeboxes

cdr100

Kodak ADL 100/150, NSM CDR100XA and CDR100Rec

cygnet

Cygnet Infinidisc

cygnet_id100

Cygnet ID100

denon200

Denon DRD-1408

disc

DISC D???

disc_da

DISC DA*.*

disc_dj

DISC CD-CHG DJ-200/600

dsm

DSM Terastore

elms

ELMS DVL

grundig35

Grundig GMS 1035

grundig105

Grundig GMS 2105

grundig200

Grundig GMS 3200

grundig280

Grundig GMS 3280

hyundai

Hyundai HAS-550

image

Hard disk image of a disk or of an ISO 9660 file

jvc

JVC MC-* CDROM Library

kodak_cdl

Kodak CDL 54, CDL 144

kubik

Kubik CDR240M

mercury

Kodak ADL 150, NSM Mercury 20, 31 and 40

nakamichi

Nakamichi MCD-1020, MJ-4.8s, MJ-5.16si
Smart and Friendly CDJ 7004 and CDJ 4008

pioneer6

Pioneer DRM-6??x

pioneer18

Pioneer DRM-1804x

pioneer100

Pioneer DRM-1004x

pioneer500

Pioneer DRM-5004x

plasmond

Plasmon D-Series

plextor200

Plextor MegaPlex (also known as PX-J2200)

ps_lf_j

Panasonic LF-J-50/100/200

satellite

NSM Satellite

scsi2

Standard SCSI-2 jukeboxes

single

SCSI single drives

sony1100

Sony CDL-1100-20 Desktop Library

sony_cdl

Sony CDL-2?00-??

sony_cdz

Sony CDZ-R360

standard

NSM Mercury 20s, 31s and 40s, Plasmon CD150J, ASM Jukeboxen, Grundig M35

tower

Cope Tower

worm

WORM and MO jukeboxes

Drive set-up

Each device description file must also contain a line such as drive=<path> for each existing drive, where the specified <path> is the name of the drive. The way the drive names are represented is described in "SCSI devices and device names" on page 52.
Please note:
The order in which the drives are listed is important and should reflect the view of the jukebox. Check your jukebox manual to determine which SCSI ID belongs to which drive.
You have four choices for the drive= lines. They differ in what character, if any, is to be added after the `=':

1. If the drive is either not available or defective, declare this using the syntax drive=!. This inhibits all interaction of iXOS-JUKEMAN with the respective drive.
2. If you want to dedicate a recorder drive for writing disks, use the syntax drive=-. This specification allows the administrator to move disks into or from the drive, but file system requests will not use this drive. When the server is running, a drive can be locked and unlocked dynamically with cdadm detach <device> [-d <drive> ] and cdadm attach <device> [-d <drive> ], respectively.
3. For a recorder drive you want to use for incremental writing from the file system, choose the syntax drive=* (see also "Burning disks incrementally" on page 154).
4. In all other cases, use the syntax drive=... .


For example, if you want the server to control a single drive that the generic SCSI driver presents as

\\.\p0b0t4 or /dev/iXOS_SCSI0/4

the device description file should look like this:
Windows NT UNIX
device=single device=single
drive=\\.\p0b0t4 drive=/dev/iXOS_SCSI0/4
Similarly, a device description file for a pioneer6 changer would look like this:
device=pioneer6 device=pioneer6
drive=\\.\p0b0t4 drive=/dev/iXOS_SCSI0/4

Note: The drives in the device description file must be in the same order as the drive numbers in the jukebox and not in the order of the SCSI IDs. This applies to all jukeboxes with several SCSI IDs for the drives. See the documentation that came with the jukebox for more information on the drive order. The first physical drive of the jukebox must be the first drive in the device description file.


If the device type is a hard disk image, the drive parameter must be specified as one or more file names with an ISO image. (see "Disk images on hard disk" on page 220).

Slot set-up

Using the parameter disks=<slots> you specify the slots to be used by the server. Sometimes it can be useful to use only some of the slots, for instance during set-up or when writable disks are stored in unused slots (reading empty disks can take some time depending on the drive). If the server is to use no slot at all, you can specify "disks=-". In this case each disk will have to be tested individually to be made known to the server, and the server will forget about the disks when it is shut down.
If not otherwise specified in the device description file, all slots will be used. You can specify a few disks by adding a line such as disks=1-3 or disks=1,2,4-6.
The slots can be specified using the following syntax:
- no slot
7 slot 7
3,6,40 slots 3, 6 and 40
3-7 slots 3 through 7
2,20-45 slot 2, and slots 20 through 45

Save file set-up

When the server attaches a device, it inspects only the specified disks. This is useful during installation when you start and stop the server often. If you do not want the server to inspect the disks upon each start-up, use the parameter save=<savefile> to specify a save file in which the server stores information about which disk resides in which slot of the jukebox. The server uses the file if present or creates it if it is not present.
device=pioneer6 device=pioneer6
drive=\\.\p0b0t4 drive=/dev/iXOS_SCSI0/4
save=p6.sav save=p6.sav
We recommend that you use the following naming scheme: Use the name of the device description file with the suffix .sav instead of the suffix .dev. This is also the default setting if the save file is specified as save=*.sav. If the name of your device description file is p6.dev, the save file should be p6.sav.
Please note that if you change disks manually the state of the save file will be corrupted. Therefore, manual disk changes should only be done if you are aware of how to regain a consistent state (see "cdadm testcd <device> <list>" on page 242).

Robot set-up

For the device types "nakamichi", "tower", "image" and "pioneer6" as well as "single" a robot need not be specified.
For all other device types, you must specify a robot: robot=<rob>. For most devices this is another SCSI ID. For "sony_cdz" and "pioneer18", this is a LUN of the drive target. A device description file for a "pioneer18" using slots 1-9 would look like this:
device=pioneer18 device=pioneer18
drive=\\.\p0b0t3 drive=/dev/iXOS_SCSI0/3
robot=\\.\p0b0t3,1 robot=/dev/iXOS_SCSI0/3,1
disks=1-9 disks=1-9
For the "kubik", the robot uses a serial interface. The device description file looks like this:
device=kubik device=kubik
drive=\\.\p0b0t1 drive=/dev/iXOS_SCSI0/1
drive=\\.\p0b0t2 drive=/dev/iXOS_SCSI0/2
drive=\\.\p0b0t3 drive=/dev/iXOS_SCSI0/3
drive=\\.\p0b0t4 drive=/dev/iXOS_SCSI0/4
robot=com2: robot=/dev/ttya
For NSM jukeboxes "cdr100", "mercury", and "satellite", a single serial line controls up to 16 jukeboxes. An additional line robid=<id>, specifies the ID of the robot on the serial line. Each NSM jukebox has an ID from 0 to 15, which can be checked and set by the Mercury's or Satellite's menu, or directly in the CDR 100 (see NSM manual). A device description file for a Mercury 20 with Robot ID 7 should look something like:
device=mercury device=mercury
drive=\\.\p1b0t0 drive=/dev/iXOS_SCSI1/0
drive=\\.\p1b0t1 drive=/dev/iXOS_SCSI1/1
robot=com2: robot=/dev/ttya
robid=7 robid=7
Alternatively, the following syntax can be used to define the serial interface and robot ID in one line:

robot=com2:,7 robot=/dev/ttya,7


previous - next - up - title - contents - index