I know the lus drivers are in a second package with SBU. SUNWsbus2 holds all
of them. Has anyone removed and reinstalled this package before? Any
particular steps to follow or just a plain "pkgrm SUNWsbus2"? Followed by a
pkgadd SUNWsbus2?
Ray
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]
On
Behalf Of Robert Maiello
Sent: Tuesday, September 07, 2004 12:14 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] jbconfig "read_elem_unload_fail"
Well it certainly looks as if the arm (/dev/lus) entry is different than
your inquire output. The jbconfig is finding your library though at 2.2.0?
As far as I know one can have the /dev/lus entry pointing to a jukebox and
doing a jbconfig for a second jukebox will not change the link. Still if
you have the one SCSI attached jukebox it's possible there is some
confusion taking place here. A boot -r may not step on an existing /dev/lus
entry. You could remove the /dev/lus entry/link and do a boot -r to see if
it gets remade. You may want to go through removing the entry with Sun
support; they may have a proper way to do it. Sun may , for example, have
you work with /etc/path_to_inst. Legato may be able to help also?
With no library defined then, the boot -r may or may not create the /dev/lus
entry..I forget. Either way jbconfig will find the library and hopefully
complete this time.
Robert Maiello
Pioneer Data Systems
On Tue, 7 Sep 2004 11:51:34 +0000, Ray Pengelly <ray AT BIOMED.QUEENSU DOT CA>
wrote:
>Here is the output as suggested:
>
> ls -l /dev/rmt/0cbn
>lrwxrwxrwx 1 root root 80 Jan 6 2004 /dev/rmt/0cbn ->
../../devices/pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci9005,ffff@2,1/st@3,0
:cbn
>dmstore/> ls -l /dev/lus
>lrwxrwxrwx 1 root other 47 Jan 29 2004 /dev/lus ->
../devices/pci@0,0/pci-ide@1f,1/ide@1/lus@0,0:0
>dmstore/> mt -t /dev/rmt/0cbn status
>Quantum Super DLT 320 tape drive:
> sense key(0x0)= No Additional Sense residual= 0 retries= 0
> file no= 0 block no= 0
>
>So I see the tape drive seems fine. Am I right in assuming the lus driver
isn't correct as it shows lus@0,:0 when the robot is on controller 2 target
2?
>
>If so how do I get the lus driver pointed to the right scsi target?
>
>Ray
>
>
>-----Original message-----
>From: Robert Maiello robert.maiello AT PFIZER DOT COM
>Date: Fri, 3 Sep 2004 15:47:34 -0400
>To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
>Subject: Re: [Networker] jbconfig "read_elem_unload_fail"
>
>> It certainly sounds like something is wrong with the library..ie its not
>> letting network read an element (broken bar code reader) or unload a
>> drive (problem talking to the drive)?
>>
>> You said the controller number of the libary arm moved when disk or
>> something was added to the system? I see it found a arm and the drive
>> on 2.2.0 and 2.3.0. ie ..SCSI IDs 2 and 3. Does the front panel of the
>> library report match these SCSI IDS. For Solaris anyway the device
>> path of the arm (/dev/lus) and tape drive /dev/rmt/0 should be
>> the same except of the last SCSI ID part; ie.
>> ls -l /dev/rmt/0cbn
>> ls -l /dev/lus
>>
>> I was thinking, perhaps that your tape drive is still on another device
>> path. Can you load a tape in the drive (manual or via the front panel)
>> and verify the OS (you didn't mention what OS) can see it with the mt
>> command:
>> mt -t /dev/rmt/0cbn status
>>
>>
>> Just guessing..you said the whole setup was working and some controller
>> numbers moved or something? Have Sun/Quantum come out to check out the
>> library?
>>
>> Robert Maiello
>> Pioneer Data Systems
>>
>> On Fri, 3 Sep 2004 11:40:31 +0000, Ray Pengelly <ray AT BIOMED.QUEENSU DOT
>> CA>
wrote:
>>
>> >I'm dropping my listing to show the inquire and sjirjc commands as well
as
>> my jbconfig. I made sure I deleted the driver device (/dev/rmt/0cbn) and
the
>> jukebox before I started. I am still getting the 'read_elem_unload_fail'
>> message.
>> >
>> >Any help anyone could give would be greatly appreciated.
>> >
>> >Ray
>> >
>> >dmstore/> cfgadm -la
>> >Ap_Id Type Receptacle Occupant
Condition
>> >c0 scsi-bus connected configured
unknown
>> >c0::dsk/c0t0d0 disk connected configured
unknown
>> >c0::dsk/c0t4d0 disk connected configured
unknown
>> >c0::lus2 disk connected configured
unknown
>> >c2 scsi-bus connected configured
unknown
>> >c2::lus3 tape connected configured
unknown
>> >c2::rmt/0 tape connected configured
unknown
>> >c3 scsi-bus connected configured
unknown
>> >c3::dsk/c3t0d0 disk connected configured
unknown
>> >c3::dsk/c3t0d1 disk connected configured
unknown
>> >c3::lus1 disk connected configured
unknown
>> >
>> >dmstore/etc/LGTOuscsi> ./inquire
>> >[email protected]:DS560 0001|Disk, /dev/rdsk/c3t0d0s2
>> >[email protected]:DS560 0001|Disk, /dev/rdsk/c3t0d1s2
>> >[email protected]:SEAGATE ST336607LW 0006|Disk, /dev/rdsk/c0t0d0s2
>> >[email protected]:SEAGATE ST336607LW 0006|Disk, /dev/rdsk/c0t4d0s2
>> >[email protected]:M4 DATA MagFile 3.07|Autochanger (Jukebox)
>> >[email protected]:QUANTUM SDLT320 2E2E|Tape, /dev/rmt/0cbn
>> >[email protected]:ASUS CD-S520/A 2. |CD-ROM, /dev/rdsk/c1t0d0s2
>> >[email protected]:ASUS CD-S520/A 2. |CD-ROM
>> >[email protected]:ASUS CD-S520/A 2. |CD-ROM
>> >[email protected]:ASUS CD-S520/A 2. |CD-ROM
>> >[email protected]:ASUS CD-S520/A 2. |CD-ROM
>> >[email protected]:ASUS CD-S520/A 2. |CD-ROM
>> >[email protected]:ASUS CD-S520/A 2. |CD-ROM
>> >[email protected]:ASUS CD-S520/A 2. |CD-ROM
>> >[email protected]:ASUS CD-S520/A 2. |CD-ROM
>> >dmstore/etc/LGTOuscsi> ./sjirjc 2.2.0
>> >
>> > Device: 2.2.0
>> >
>> > Number of Drives: 1
>> > Number Drive Pairs: 1
>> > Number of Import/Export Elements: 0
>> > Number of Import/Export Pairs: 1
>> > Number of Slots: 20
>> > Number of Slot Pairs: 1
>> > Number of Transport Elements: 1
>> > Number of Transport Pairs: 1
>> >
>> > Volume Tags Supported
>> >Initialize Element Status Supported
>> > Bar Codes Supported
>> >
>> >dmstore/etc/LGTOuscsi> jbconfig
>> > 1) Install an Autodetected SCSI Jukebox.
>> > 2) Install an Autodetected NDMP SCSI Jukebox.
>> > 3) Install an SJI Jukebox.
>> >
>> >What kind of Jukebox are you installing? [1] 1
>> >These are the SCSI Jukeboxes currently attached to your system:
>> > 1) [email protected]: Standard SCSI Jukebox, Vendor <M4 DATA>, Product
<MagFile>
>> >Which one do you want to install? 1
>> >Installing an 'Standard SCSI Jukebox' jukebox.
>> >Name you would like to assign to the jukebox device? L25
>> >A brief description of the jukebox device? [[email protected]: Standard SCSI
>> Jukebox] Sun L25
>> >Pathname of the control port for the jukebox device? [[email protected]]
>> [email protected]
>> >Do you want automated device cleaning support enabled? (yes/no) no
>> >
>> >Will media drive 1 be shared by multiple device paths? (yes/no) no
>> >
>> >Enter hostname that owns media drive 1: ? [dmstore.eyeml.queensu.ca]
>> >
>> >An example of a valid device name for this OS is '/dev/rmt/1cbn'
>> >Enter pathname of media drive 1: ? /dev/rmt/0cbn
>> >using '/dev/rmt/0cbn' as device name
>> >Should the drive be configured as a NDMP device? (yes/no) no
>> >This media device has not been configured yet. Please
>> >select a media device type for /dev/rmt/0cbn.
>> > 1) 3480 17) 9490 33) qic
>> > 2) 3570 18) 9840 34) SD3
>> > 3) 3590 19) 9940 35) sdlt
>> > 4) 4890 20) dlt 36) sdlt320
>> > 5) 4mm 21) dlt1 37) SLR
>> > 6) 4mm 12GB 22) dlt7000 38) tkz90
>> > 7) 4mm 20GB 23) dlt8000 39) travan10
>> > 8) 4mm 4GB 24) dst 40) tz85
>> > 9) 4mm 8GB 25) dst (NT) 41) tz86
>> > 10) 8mm 26) dtf 42) tz87
>> > 11) 8mm 20GB 27) dtf2 43) tz88
>> > 12) 8mm 5GB 28) file 44) tz89
>> > 13) 8mm AIT 29) himt 45) tz90
>> > 14) 8mm AIT-2 30) LTO Ultrium 46) tzs20
>> > 15) 8mm AIT-3 31) LTO Ultrium-2 47) VXA
>> > 16) 8mm Mammoth-2 32) optical
>> >Choice? 36
>> >Your jukebox has a bar code reader.
>> >Do you want bar code reader support enabled? (yes/no) yes
>> >Do you want volume labels to match bar code labels? (yes/no) yes
>> >
>> >'read_elem_unload_fail' invalid choice for 'jukebox features'
>> >Would you like to configure another jukebox? (yes/no) no
>> >
>> >--
>> >Note: To sign off this list, send a "signoff networker" command via
email
>> >to listserv AT listmail.temple DOT edu or visit the list's Web site at
>> >http://listmail.temple.edu/archives/networker.html where you can
>> >also view and post messages to the list.
>> >=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>>
>> --
>> Note: To sign off this list, send a "signoff networker" command via email
>> to listserv AT listmail.temple DOT edu or visit the list's Web site at
>> http://listmail.temple.edu/archives/networker.html where you can
>> also view and post messages to the list.
>> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>http://listmail.temple.edu/archives/networker.html where you can
>also view and post messages to the list.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
