Sponsored Content
Top Forums UNIX for Advanced & Expert Users Scalar i500 can see tape drives but not autochanger Post 302181707 by tecky on Thursday 3rd of April 2008 07:00:16 PM
Old 04-03-2008
Scalar i500 can see tape drives but not autochanger

We have a new i500 and have 4 TLO4 drives which are connected directly to 2 FC cards on the host. The host can communicate with the autochanger through whichever drive that is set as control path.

When I run inquire, all 4 drives are listed but auto changer doesn't show up. Does anyone know how to configure lus.conf? I have tried the set it based on some of the sites I surfed on but still can't make it work. Any help is appreciated.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

DDS Tape Drives

How do I find if a server contains a DDS3 or a DDS2 drive remotely ? I checked in SMIT and I noticed the description field according to tape drives, but is there another more thorough way? Thanks, Luke (0 Replies)
Discussion started by: Skywlkr235
0 Replies

2. Solaris

identifying Tape drives on Sun Servers

Hi, Can you please help me to locate tape drives on Sun Server and the capacity of the tape drive. I am managing a Sun 4u server. Need this urgently. Regards, Vivek (2 Replies)
Discussion started by: vivek_scv
2 Replies

3. BSD

tape drives vs. tar with multiple directories

Hello, I have a little problem with backup & restoring files from tape drive. I am adding 3 directories to my tape, and it is OK: hades# tar -cvf /dev/nsa0 test test1 restore a test a test/level1 a test/myharddisk.img a test1 a test1/level1 a test1/myharddisk.img a test1/test.img a... (1 Reply)
Discussion started by: d3m00n
1 Replies

4. AIX

command to display my tape drives (rmt's)

Hi all, Looking for an ls** command to display my tape drives and their associated serial numbers. thx. (8 Replies)
Discussion started by: jwholey
8 Replies

5. Filesystems, Disks and Memory

Tape drives used for taking backups

Hi, I am a abit new in AIX system administration field. I want to gather knowledge about backup techniques. As per my knowledge we use Tape archives for taking backups. Can anyone pls explain me in detail abt tape archive? Whether these tape archives come along with the systems or we have to... (1 Reply)
Discussion started by: forumsrahul
1 Replies

6. Solaris

tape drives not recognised

I have a server/domain on a m5000 running Solaris 10. It is part of a cluster. The other cluster member sees tape drives, but this one does not. It is zoned correctly, and I can see the drives are binded in lputil. The st.conf, and devlink.tab are identical. ST.CONF: - # # Copyright... (1 Reply)
Discussion started by: pfwhufc
1 Replies

7. Solaris

Adding new tape drives

hi, i am using Solaris 8 on a sparc box and already have 4 tape drives in a backup libaray attached to my unix server. we have recently added 2 new tape drives to the libaray and now want to get unix to see them. have it working in windows. how do i scan for new hardware and add theses new... (5 Replies)
Discussion started by: dshakey
5 Replies

8. Solaris

MPXIO not working on a machine with both SAN and Tape drives.

Hi, I have a machine, and mpzio fails everytime i reboot the server. The machine has tape drives and SAN storage, I'm not sure if that is my issue or not. I was told to not enable mpxio globally as that would do something bad to the tape drives. So, I set it to only make the two SAN connected... (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

9. AIX

AIX 7.1 cannot discover drives from TS3310 tape library

Good day! Need help in checking my AIX 7.1 box. After we have finished zoning our TS3200 and TS3310 tape libraries, we installed the Atape driver, # lslpp -L |grep tape Atape.driver 11.7.7.0 C F IBM AIX Enhanced Tape and devices.fcp.tape.rte 7.1.3.15 C ... (0 Replies)
Discussion started by: alainken3
0 Replies
EJECT(1)							   User Commands							  EJECT(1)

NAME
eject - eject removable media SYNOPSIS
eject -h eject [-vnrsfqp] [<name>] eject [-vn] -d eject [-vn] -a on|off|1|0 [<name>] eject [-vn] -c slot [<name>] eject [-vn] -t [<name>] eject [-vn] -x <speed> [<name>] eject -V DESCRIPTION
Eject allows removable media (typically a CD-ROM, floppy disk, tape, or JAZ or ZIP disk) to be ejected under software control. The command can also control some multi-disc CD-ROM changers, the auto-eject feature supported by some devices, and close the disc tray of some CD-ROM drives. The device corresponding to <name> is ejected. The name can be a device file or mount point, either a full path or with the leading "/dev" or "/mnt" omitted. If no name is specified, the default name "cdrom" is used. There are four different methods of ejecting, depending on whether the device is a CD-ROM, SCSI device, removable floppy, or tape. By default eject tries all four methods in order until it succeeds. If the device is currently mounted, it is unmounted before ejecting. COMMAND-LINE OPTIONS -h This option causes eject to display a brief description of the command options. -v This makes eject run in verbose mode; more information is displayed about what the command is doing. -d If invoked with this option, eject lists the default device name. -a on|1|off|0 This option controls the auto-eject mode, supported by some devices. When enabled, the drive automatically ejects when the device is closed. -c <slot> With this option a CD slot can be selected from an ATAPI/IDE CD-ROM changer. Linux 2.0 or higher is required to use this feature. The CD-ROM drive can not be in use (mounted data CD or playing a music CD) for a change request to work. Please also note that the first slot of the changer is referred to as 0, not 1. -t With this option the drive is given a CD-ROM tray close command. Not all devices support this command. -x <speed> With this option the drive is given a CD-ROM select speed command. The speed argument is a number indicating the desired speed (e.g. 8 for 8X speed), or 0 for maximum data rate. Not all devices support this command and you can only specify speeds that the drive is capable of. Every time the media is changed this option is cleared. This option can be used alone, or with the -t and -c options. -n With this option the selected device is displayed but no action is performed. -r This option specifies that the drive should be ejected using a CDROM eject command. -s This option specifies that the drive should be ejected using SCSI commands. -f This option specifies that the drive should be ejected using a removable floppy disk eject command. -q This option specifies that the drive should be ejected using a tape drive offline command. -p This option allow you to use /proc/mounts instead /etc/mtab. It also passes the -n option to umount(1). -V This option causes eject to display the program version and exit. LONG OPTIONS
All options have corresponding long names, as listed below. The long names can be abbreviated as long as they are unique. -h --help -v --verbose -d --default -a --auto -c --changerslot -t --trayclose -x --cdspeed -n --noop -r --cdrom -s --scsi -f --floppy -q --tape -V --version -p --proc EXAMPLES
Eject the default device: eject Eject a device or mount point named cdrom: eject cdrom Eject using device name: eject /dev/cdrom Eject using mount point: eject /mnt/cdrom/ Eject 4th IDE device: eject hdd Eject first SCSI device: eject sda Eject using SCSI partition name (e.g. a ZIP drive): eject sda4 Select 5th disc on mult-disc changer: eject -v -c5 /dev/cdrom Turn on auto-eject on a SoundBlaster CD-ROM drive: eject -a on /dev/sbpcd EXIT STATUS
Returns 0 if operation was successful, 1 if operation failed or command syntax was not valid. NOTES
Eject only works with devices that support one or more of the four methods of ejecting. This includes most CD-ROM drives (IDE, SCSI, and proprietary), some SCSI tape drives, JAZ drives, ZIP drives (parallel port, SCSI, and IDE versions), and LS120 removable floppies. Users have also reported success with floppy drives on Sun SPARC and Apple Macintosh systems. If eject does not work, it is most likely a limita- tion of the kernel driver for the device and not the eject program itself. The -r, -s, -f, and -q options allow controlling which methods are used to eject. More than one method can be specified. If none of these options are specified, it tries all four (this works fine in most cases). Eject may not always be able to determine if the device is mounted (e.g. if it has several names). If the device name is a symbolic link, eject will follow the link and use the device that it points to. If eject determines that the device can have multiple partitions, it will attempt to unmount all mounted partitions of the device before ejecting. If an unmount fails, the program will not attempt to eject the media. You can eject an audio CD. Some CD-ROM drives will refuse to open the tray if the drive is empty. Some devices do not support the tray close command. If the auto-eject feature is enabled, then the drive will always be ejected after running this command. Not all Linux kernel CD-ROM drivers support the auto-eject mode. There is no way to find out the state of the auto-eject mode. You need appropriate privileges to access the device files. Running as root or setuid root is required to eject some devices (e.g. SCSI devices). The heuristic used to find a device, given a name, is as follows. If the name ends in a trailing slash, it is removed (this is to support filenames generated using shell file name completion). If the name starts with '.' or '/', it tries to open it as a device file or mount point. If that fails, it tries prepending '/dev/', '/mnt/', '/dev/cdroms', '/dev/rdsk/', '/dev/dsk/', and finally './' to the name, until a device file or mount point is found that can be opened. The program checks /etc/mtab for mounted devices. If that fails, it also checks /etc/fstab for mount points of currently unmounted devices. Creating symbolic links such as /dev/cdrom or /dev/zip is recommended so that eject can determine the appropriate devices using easily remembered names. To save typing you can create a shell alias for the eject options that work for your particular setup. AUTHOR
Eject was written by Jeff Tranter (tranter@pobox.com) and is released under the conditions of the GNU General Public License. See the file COPYING and notes in the source code for details. The -x option was added by Nobuyuki Tsuchimura (tutimura@nn.iij4u.or.jp), with thanks to Roland Krivanek (krivanek@fmph.uniba.sk) and his cdrom_speed command. SEE ALSO
mount(2), umount(2), mount(8), umount(8) /usr/src/linux/Documentation/cdrom/ Linux 18 May 2001 EJECT(1)
All times are GMT -4. The time now is 08:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy