Asset ID: |
1-72-2000282.1 |
Update Date: | 2017-09-26 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2000282.1
:
L700 - MT Status Command Fails With the Message "No Such Device or Address"
Related Items |
- Sun StorageTek L700 Tape Library
|
Related Categories |
- PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: STK Legacy Drive and Library
|
In this Document
Created from <SR 3-10450477061>
Applies to:
Sun StorageTek L700 Tape Library - Version All Versions to All Versions [Release All Releases]
x86_64
STK L700 tape library has Dynamic WWN feature turned on. Tape drives are properly zoned in. The OS can detect the drives and creates all necessary driver files.
Symptoms
mt status check on any tape drive will give the message "no such device or address"
Tape Hardware functionality has been verified and found to be good.
Tape Devices detected correctly on the OS side.
cfgadm:
c3::500104f000003028 connected configured unknown STK T9940B
unavailable tape n /devices/pci@1c,600000/SUNW,emlxs@1/fp@0,0:fc::500104f000003028
c3::500104f0007d12bd connected configured unknown STK T9940B
unavailable tape n /devices/pci@1c,600000/SUNW,emlxs@1/fp@0,0:fc::500104f0007d12bd
c3::500104f000b57256 connected configured unknown STK T9940B
unavailable tape n /devices/pci@1c,600000/SUNW,emlxs@1/fp@0,0:fc::500104f000b57256
c10::500104f0007782ec connected configured unknown STK T9940B
unavailable tape n /devices/pci@1c,600000/SUNW,emlxs@1,1/fp@0,0:fc::500104f0007782ec
c10::500104f000bf979f connected configured unknown STK T9940B
unavailable tape n /devices/pci@1c,600000/SUNW,emlxs@1,1/fp@0,0:fc::500104f000bf979f
c10::500104f000c8ffb3 connected configured unknown STK T9940B
unavailable tape n /devices/pci@1c,600000/SUNW,emlxs@1,1/fp@0,0:fc::500104f000c8ffb3
========================
iostat:
rmt/10 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: STK Product: T9940B Revision: 1.42 Serial No: .407
rmt/8 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: STK Product: T9940B Revision: 1.36 Serial No: .404
rmt/9 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: STK Product: T9940B Revision: 1.44 Serial No: .410
rmt/5 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: STK Product: T9940B Revision: 1.36 Serial No: .404
rmt/6 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: STK Product: T9940B Revision: 1.44 Serial No: .410
rmt/7 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: STK Product: T9940B Revision: 1.44 Serial No: .410
==========================
luxadm:
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 710800 0 500104f000c8ffb3 500104f000c8ffb2 0x1 (Tape device)
1 710900 0 500104f000bf979f 500104f000bf979e 0x1 (Tape device)
2 710d00 0 500104f0007782ec 500104f0007782eb 0x1 (Tape device)
3 711600 0 10000000c9829331 20000000c9829331 0x1f (Unknown Type,Host Bus Adapter)
Pos Port_ID Hard_Addr Port WWN Node WWN Type
0 710b00 0 500104f000003028 500104f000003027 0x1 (Tape device)
1 710c00 0 500104f0007d12bd 500104f0007d12bc 0x1 (Tape device)
2 710e00 0 500104f000b57256 500104f000b57255 0x1 (Tape device)
3 711400 0 10000000c9829330 20000000c9829330 0x1f (Unknown Type,Host Bus Adapter)
=========================
Any I/O attempt leads to ambiguous error "No such device or address".
Changes
Added 3 new 9940B tape drives to the L700 tape Library.
Cause
Customer is running an old OS that the st driver does not handle instances > 2047 correctly.
Trying to open an st-device with an instance >2047 results in the error: " no such device or address".
e.g /dev/rmt/8 is
lrwxrwxrwx 1 root root 71 Apr 7 20:49 8 -> ../../devices/pci@1c,600000/SUNW,emlxs@1/fp@0,0/st@w500104f000003028,0:
$ grep 500104f000003028 path_to_inst
"/pci@1c,600000/SUNW,emlxs@1/fp@0,0/st@w500104f000003028,0" 3852 "st"
"/pci@1c,600000/SUNW,emlxs@1/fp@0,0/sg@w500104f000003028,0" 3853 "sg"
Solution
Step I:
st.conf entries which are currently set to 255 luns per target should be reduced down to the following:
name="st" class="scsi" target=0 lun=0;
name="st" class="scsi" target=0 lun=1;
name="st" class="scsi" target=1 lun=0;
name="st" class="scsi" target=1 lun=1;
name="st" class="scsi" target=2 lun=0;
name="st" class="scsi" target=2 lun=1;
name="st" class="scsi" target=3 lun=0;
name="st" class="scsi" target=3 lun=1;
name="st" class="scsi" target=4 lun=0;
name="st" class="scsi" target=4 lun=1;
name="st" class="scsi" target=5 lun=0;
name="st" class="scsi" target=5 lun=1;
name="st" class="scsi" target=6 lun=0;
name="st" class="scsi" target=6 lun=1;
name="st" class="scsi" target=8 lun=0;
name="st" class="scsi" target=8 lun=1;
name="st" class="scsi" target=9 lun=0;
name="st" class="scsi" target=9 lun=1;
name="st" class="scsi" target=10 lun=0;
name="st" class="scsi" target=10 lun=1;
name="st" class="scsi" target=11 lun=0;
name="st" class="scsi" target=11 lun=1;
name="st" class="scsi" target=12 lun=0;
name="st" class="scsi" target=12 lun=1;
name="st" class="scsi" target=13 lun=0;
name="st" class="scsi" target=13 lun=1;
name="st" class="scsi" target=14 lun=0;
name="st" class="scsi" target=14 lun=1;
name="st" class="scsi" target=15 lun=0;
name="st" class="scsi" target=15 lun=1;
Step II:
Remove all the st devices in /etc/path_to_inst
# cp /etc/path_to_inst /etc/path_to_inst.orig.st
# vi /etc/path_to_inst - and make the changes
Step III:
# rm /dev/rmt/*
# rm /dev/rst*
# rm /dev/nrst*
Step IV:
# devfsadm -Cv to rebuild the devices.
Step V:
Perform mt status check and confirm the communication with the tape drives.
Attachments
This solution has no attachment