6. FAQ

6.1 I connected a new jukebox to my PC and a new drive letter appeared. Why did this happen?

At startup, NT inspects the hardware for devices that could represent file systems. The SCSI device type (according to the SCSI standard) is checked during this process. Unfortunately some devices don't respond properly to this request (for example, the Yamaha CDR 100 responds as a WORM drive). In the absence of iXOS-JUKEMAN, all devices capable of containing a file system would be displayed in the File Manager.

Since using a CD drive directly as well as through iXOS-JUKEMAN might yield unexpected results in some circumstances, and some customers want to connect a larger number of drives than can be covered by drive letters, iXOS-JUKEMAN can override the standard behavior described in the preceding paragraph two ways:1.

1. If you chose to attach the corresponding device automatically on server startup (in server.cfg either by direct editing or via the GUI), the Jukeman server changes NT to hide the drive letters during the next reboot. This takes effect only after a second reboot, since only then is this change visible to the operating system. If you change the startup mode again, or if the server isn't able to connect to the device (which might be switched off), the "claim" established by the automatic attach disappears after the second reboot.
2. If you want to remove direct access to drive letters permanently, you can use the regedt32 registry editor. In

   HKEY_LOCAL_MACHINE
   	|
   	--SYSTEM
   		|
   		CurrentControlSet
   			|
   			Services
   				genscsi
   					claims

   
   add entries for each drive you want to remove. For example, suppose that after rebooting with the connected devices, the scsidevs command returns a line similar to:
   0000008\\.\p2b0t2,0 is Toshiba's CD-drive "CD-ROM XM-3501TA"
   and you want to hide this drive.
   Choose Add value from the Edit menu and type the target ID as the value, where the first four characters are skipped (p2b0t2,0 in the example).
   The data type should be REG_DWORD and the corresponding value, which you are asked for after clicking OK, should be 2 (with hex radix, which is the default).
   You should see an entry like
   p2b0t2,0:REG_DWORD:0x2
   in the right part of the window.
   Note:If you follow this process, be sure to document your actions for your system administrator because another device cannot connected to the claimed address until the claim is removed.

6.2 Why can't my jukebox distinguish between bad CDs and empty slots? Why are empty recordable CDs labeled as bad CDs or not recognized?

Some jukeboxes and/or their drives cannot distinguish between empty slots and bad CDs. If this is the case with your jukebox, iXOS-JUKEMAN cannot make the distinction either.

Treatment of an empty recordable CD also depends on the type of CD drive or writer you are using. Some drives label them as bad CDs and some don't acknowledge that there is a CD.

6.3 What does the logfile message "CANNOT GET FH: 13 - Permission denied" mean?

This message occurs if the directory you create to mount on client computers is not exported. Refer to "Step 1: Setting Up File System Views" in Chapter 2 for information.

6.4 How can I restrict access of certain hosts to the Jukeman file system?

When you export the file system, you can use an option to restrict access. The option defines a list of hosts that can mount the exported file system. Make sure you include the local host in the list.

For example, in Solaris 2.4, the file /etc/dfs/dfstab can contain the following line:

share -F nfs -o rw=localhost:host2:host3:host4 /views/pc

6.5 What do I do if iXOS-JUKEMAN does not work properly?

• Check this manual and your jukebox manual to make sure your set up is correct.
• Reboot the host that runs iXOS-JUKEMAN with the jukeboxes you plan to use properly connected and turned on.
• Check the log file, logfile.txt, in the directory where the cdnfsd program resides. Refer to "Log Messages" in Chapter 5 for information about reading the log file.

1. The server does not start up correctly.
2. A device cannot be attached.
3. You can't access a CD.

   Startup Problems

   • Make sure you don't attach any devices automatically by editing server.cfg either directly or via the GUI.
   • Use the Control Panel to check that iXOS Admin Server, iXOS Jukebox Daemon, iXOS generic SCSI driver, and iXOS Jukebox File System are installed and started.
   • Check the event log, especially if you are experiencing hardware problems. If the scsidevs command does not show any SCSI devices, you are probably encountering hardware problems.
   • Use an appropriate ps (ps -aux or ps -efl) to check that no cdnfsd is already running. Note that cdnfsd must either be started by root or must be suid (see Chapter 2).

   Attaching Problems

   Attaching problems are almost always due to an incorrect device file.

   • Check that you chose the right device type. For each SCSI ID listed as a drive, use the inquiry command to verify that you can communicate with it. Typical output is:
     inquiry \\.\p2b0t2,0
0000002 \\.\p2b0t2,0 is Toshiba's
CD-drive "CD-ROM XM-3501TA"
0000003 ProRevL 1875, Firmware 07/06/95
   • If you encounter a "Can't open" error, use the scsidevs command to get a list of all known SCSI devices.
     inquiry /dev/iXOS_SCSI0/4,0
0000002 /dev/iXOS_SCSI0/4,0 is
Toshiba's CD-drive
"CD-ROM XM-3501TA"
0000003 ProRevL 1875, Firmware 07/06/95
   • If you encounter a "Bad file number" error, check for known devices by
     inquiry /dev/iXOS_SCSI?/*
   • Or try to attach a drive in a jukebox as a single device to check if the drive is all right.
   • Use the same procedure for SCSI changers/robots, except you can't use them as single drives.
   • If your jukebox has a changer that is addressed by a serial line, check for these types of log file errors:
     tty_open(xxx) - No such file
or directory
     or in the case of NSM jukeboxes
     nsm_recv(): got 0 bytes garbage:
     which are caused by an incorrect robot line in the device file.
   • For NSM jukeboxes, also make sure that the robid is correct. Check the jukebox manual for details.
   • Check your jukebox manual to make sure the order of drives in the device file corresponds exactly to the order that the changer expects.
   • If you cannot find the problem, stop the server, delete the save file of the corresponding jukebox, and start the server again so the jukebox rescans all slots.

   Problems with CDs

   • A CD is labeled as a bad CD even though other drives can read it.
     In most cases this is caused by exceeding the number of CDs specified in the license file. Excess CDs cannot be addressed by iXOS-JUKEMAN.
     Any CD that does not comply with the ISO 9660 standard is labeled as a bad CD.
     Some CDs may be tagged bad because the CD does not adhere to the convention of being inserted in the slot with the label up.
   • testcd takes a long time.
     This is a hardware problem. Some CD drives and recorders require a lot of time to read a CD or detect that it is empty. iXOS-JUKEMAN waits for the CD to be read rather than returning a bad CD tag immediately.

   6.6 How do I get iXOS-JUKEMAN support?

   If you are unable to find the problem, contact jukesupport@ixos.com, phone 415 294-5826.

   When you contact support, please be at your computer and have the following information available:

   • hardware platform
   • operating system and version
   • iXOS-JUKEMAN version (from the first line in the log file)
   • contents of logfile.txt and server.cfg
   • identity of all devices causing problems
   [Table of Contents] [Glossary]

   ---

   Send mail to webmaster@munich.ixos.de with questions or comments about this web site.
   Copyright © 1997 iXOS Software GmbH
   Last modified: