tape drives not recognised

Thread Tools Search this Thread
Operating Systems Solaris tape drives not recognised
# 1  
Old 08-27-2009
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.


# Copyright 2004 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#pragma ident "@(#)st.conf 1.34 04/06/24 SMI"
# The officially supported devices do not require a entry under
# tape-config-list as their configuration is built in to the driver.
# A non configured drive will say Unconfigured Drive: and have single quoted
# Vendor and Product strings displayed when it's status is checked with mt.
# mt -f /dev/rmt/# status
# Unconfigured Drive: Vendor 'VENDOR ' Product 'A Product ID '
# sense key(0x0)= No Additional Sense residual= 0 retries= 0
# file no= 0 block no= 0
# If your drive is displayed like this first check to see if a newer version
# of the st driver has added support for your drive.
# If your drive is not supported by Sun, check the drive manufacturer's
# documentation or web site for their recommended configuration strings.
# To configure a drive not supported by the driver, use the single quoted
# Vendor and Product strings to create a entry under tape-config-list.
# A starting point for your st.conf entry can be obtained by reading the
# current DEFAULT configuration from the driver using mt.
# mt -f /dev/rmt/# config
# "SONY SDX-700C", "SONY SDX-700C", "SONYSDX700C";
# SONYSDX700C = \
# 2,0x12,0,0x1865B,4,0x00,0x00,0x00,0x00,0,120,120,3600,3600,3600,3600,3600;
# Notes:
# Any spaces in the Vendor field must be kept so that it is 8
# characters long. Trailing spaces in the Product field can be removed.
# To add this configuration information, first uncomment the
# "tape-config-list=" line, and add the first configuration line
# immediately afterward. If there is more than one entry in the
# tape-config-list, all entries but the last must end with a comma.
# The last entry ends with a semicolon.
# See the driver.conf(4) man page for general information on the conf
# file format, and the st(7d) man page for information specific to st.conf
# Example:
# "VENDOR A Product ID", "A Prettier Name to Display", "A-Config-Name",
# "VENDORB Other Product ID", "An Other Pretty Name", "Other-Config-Name";
# Then for each config-Name there must be a setup string that looks like this.
# A-Config-Name = \
# 2,0x34,0,0x18659,4,0x47,0x47,0x47,0x47,1,120,120,3600,3600,3600,3600,3600;
# Other-Config-Name = 1,0x3B,0,0x18659,4,0x40,0x40,0x40,0x40,3;
# For specific details for of values to use see the st(7D) man pages and
# drive vendor manuals.

name="st" class="scsi" target=0 lun=0;
name="st" class="scsi" target=1 lun=0;
name="st" class="scsi" target=2 lun=0;
name="st" class="scsi" target=3 lun=0;
name="st" class="scsi" target=4 lun=0;
name="st" class="scsi" target=5 lun=0;
name="st" class="scsi" target=6 lun=0;
name="st" class="scsi" target=7 lun=0;
name="st" class="scsi" target=8 lun=0;
# In case there are wide tape drives, one can use these targets
#name="st" class="scsi" target=9 lun=0;
#name="st" class="scsi" target=10 lun=0;
#name="st" class="scsi" target=11 lun=0;
#name="st" class="scsi" target=12 lun=0;
#name="st" class="scsi" target=13 lun=0;
#name="st" class="scsi" target=14 lun=0;
#name="st" class="scsi" target=15 lun=0;
# This line adds support for Fibre Channel Tapes
name="st" parent="fp" target=0;


#ident "@(#)devlink.tab.sh 1.72 00/07/17 SMI"
# Copyright (c) 1998 by Sun Microsystems, Inc.
# This is the table used by devlinks
# Each entry should have 2 fields; but may have 3. Fields are separated
# by single tab ('\t') characters.
# The fields are:
# devfs-spec: a keyword-value set of devfs specifications, describing the set
# of devfs node entries to be linked.
# The keywords are:
# type - The devinfo node type (see <sys/sunddi.h> for possible values)
# name - the devinfo node name (the part of a /devices entry that appears
# before the '@' or ':').
# addr - the devinfo node address part (the portion of the name between
# the '@' and the ':').
# minor - the minor-attributes (the portion of a /devices name after the
# ':').
# The keywords are separated from their valuse by an equals ('=') sign;
# keyword-value pairs are separated from each other by semicolons (';').
# dev name - the /dev name corresponding to the devfs node described by
# the devfs-spec field. This specification is assume to start rooted at
# The name can contain a number of escape-sequences to include parts of
# the devfs-name in the /dev/-name. These escape-sequences all start with
# a backslash ('\') character. The current sequences are:
# \D - the devfs 'name' field
# \An - the 'n'th component of the address field (n=0 means the whole
# address field)
# \Mn - the 'n'th component of the minor field (n=0 means the entire
# minor field).
# \Nn - a sequential counter, starting at n (a *single* digit, giving
# a starting range of 0 through 9).
# extra dev link - a few devices need a second link; that is, a second link
# pointing to the first link. This optional field specifies the /dev
# format of this second link. This entry can also use the above-described
# escape-sequences.
# Fields can be blank; seperated by single tab characters,
# Spaces are significant, and are considered part of a field. IN GENERAL THIS
# All fields must be present (even if blank)
# devfs-spec Dev-Namespec Extra-Link
type=pcmcia:event;name=pem pem
type=ddi_pseudo;name=SUNW,rtvc;minor=ctl rtvc\M0
type=ddi_pseudo;name=SUNW,rtvc \M0
type=ddi_pseudo;name=vxspec;minor=0,raw vx/config
type=ddi_pseudo;name=vxspec;minor=1,raw vx/trace
type=ddi_pseudo;name=vxspec;minor=2,raw vx/iod
type=ddi_pseudo;name=vxspec;minor=3,raw vx/info
type=ddi_pseudo;name=vxspec;minor=4,raw vx/task
type=ddi_pseudo;name=vxspec;minor=5,raw vx/taskmon
type=ddi_pseudo;name=vxspec;minor=6,raw vx/clust
type=ddi_pseudo;name=vxspec;minor=7,raw vx/netiod
type=ddi_pseudo;name=vxspec;minor=8,raw vx/vcevent
type=ddi_pseudo;name=vxdmp;minor=0,raw vx/dmpconfig
type=ddi_pseudo;name=fdd \D
type=ddi_pseudo;name=vxportal \D
type=ddi_pseudo;name=gab \M0
type=ddi_pseudo;name=vxfen \M0
type=ddi_pseudo;name=vxfen \M1

# lputil listhbas

20:00:00:00:c9:82:14:d3 10:00:00:00:c9:82:14:d3 0
20:00:00:00:c9:82:14:b3 10:00:00:00:c9:82:14:b3 1

# lputil shownodes 0
Visible Nodes:
Node Target WWPN WWNN
---- ------ --------- --------
In Transition 0 2e-1e-00-05-1e-36-30-d4 10-00-00-05-1e-36-30-d4
In Transition 0 21-fc-00-05-1e-36-30-d4 10-00-00-05-1e-36-30-d4
In Transition 0 21-fa-00-05-1e-36-30-d4 10-00-00-05-1e-36-30-d4
Automapped FCP Node 0 50-05-07-63-0f-5a-c3-0c 50-05-07-63-0f-1a-c3-0c
Automapped FCP Node 1 50-05-07-63-0f-5a-c3-63 50-05-07-63-0f-1a-c3-63
Automapped FCP Node 2 50-05-07-63-0f-5a-bd-0c 50-05-07-63-0f-1a-bd-0c
Automapped FCP Node 3 50-05-07-63-0f-5a-bd-63 50-05-07-63-0f-1a-bd-63

# lputil shownodes 1
Visible Nodes:
Node Target WWPN WWNN
---- ------ --------- --------
In Transition 0 2e-5e-00-05-1e-36-30-d4 10-00-00-05-1e-36-30-d4
In Transition 0 21-fc-00-05-1e-36-30-d4 10-00-00-05-1e-36-30-d4
In Transition 0 21-fa-00-05-1e-36-30-d4 10-00-00-05-1e-36-30-d4
Automapped FCP Node 0 50-05-07-63-0f-5a-c3-0c 50-05-07-63-0f-1a-c3-0c
Automapped FCP Node 1 50-05-07-63-0f-5a-c3-63 50-05-07-63-0f-1a-c3-63
Automapped FCP Node 2 50-05-07-63-0f-5a-bd-0c 50-05-07-63-0f-1a-bd-0c
Automapped FCP Node 3 50-05-07-63-0f-5a-bd-63 50-05-07-63-0f-1a-bd-63

# lputil version

One sees the drives, the other does not.

Any ideas would be welcomed.

Many Thanks.
# 2  
Old 08-31-2009
Bumping up posts or double posting is not permitted in these forums.

Please read the rules, which you agreed to when you registered, if you have not already done so.

You may receive an infraction for this. If so, don't worry, just try to follow the rules more carefully. The infraction will expire in the near future

Thank You.

The UNIX and Linux Forums.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. 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 C F IBM AIX Enhanced Tape and devices.fcp.tape.rte C ... (0 Replies)
Discussion started by: alainken3
0 Replies

2. 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

3. 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

4. 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

5. UNIX for Advanced & Expert Users

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... (1 Reply)
Discussion started by: tecky
1 Replies

6. 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

7. 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

8. 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

9. 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
Login or Register to Ask a Question