INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

E-mail*
Handle

Password
Verify P'word
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Member Feedback

"...Congratulations on a brilliant idea and a great site..."

Geography

Where in the world do Tek-Tips members come from?
brackovic (IS/IT--Management)
19 Jul 05 16:25
After changing some parts of SAN environment, NW failed in reading tapes in drives.
The error messages were as follows:

(warning) /dev/rmt/1cbn reading: read open error: drive status is There is not a tape in the drive

(warning) /dev/rmt/0cbn opening: DRIVE_STATUS_NEED_INIT

(warning) /dev/rmt/0cbn reading: read open error: drive status is The drive is not ready - it requires an initialization

(warning) /dev/rmt/1cbn reading: read open error: drive status is There is not a tape in the drive

(warning) /dev/rmt/1cbn reading: read open error: drive status is There is not a tape in the drive

(warning) Device /dev/rmt/1cbn is automatically disabled


Here are mixed messages from /dev/rmt/0cbn and /dev/rmt/1cbn, but both (in fact all 3 drives) have same behavior.

jbverify –v –v –v –v –v gives output as follow:
about to get JB info from NSR server...
 successfully retrieved JB info from NSR server.

 Processing jukebox devices...

 Processing jukebox IBM3584:

  checking if any of the drives are pre-loaded...
  checking device /dev/rmt/0cbn...
  checking device /dev/rmt/1cbn...
  checking device /dev/rmt/2cbn...

 Testing drive 1 (/dev/rmt/0cbn) of JB IBM3584
  no slot was specified. Searching for slot...
  found slot 1
  about to load from slot 1 to drive 1
  successfully loaded from slot 1 to drive 1
  found load sleep to be 5 secs for this JB

  about to test device /dev/rmt/0cbn
 open(/dev/rmt/0cbn): I/O error
  device not ready yet. Retrying (trial no. 1)...
 open(/dev/rmt/0cbn): I/O error
  device not ready yet. Retrying (trial no. 2)...
 open(/dev/rmt/0cbn): I/O error
  device not ready yet. Retrying (trial no. 3)...
 open(/dev/rmt/0cbn): I/O error
  device not ready yet. Retrying (trial no. 4)...
 open(/dev/rmt/0cbn): I/O error
  device not ready yet. Retrying (trial no. 5)...
 open(/dev/rmt/0cbn): I/O error
  device not ready yet. Retrying (trial no. 6)...
 open(/dev/rmt/0cbn): I/O error
  device not ready yet. Retrying (trial no. 7)...
 open(/dev/rmt/0cbn): I/O error
  device not ready yet. Retrying (trial no. 8)...
 open(/dev/rmt/0cbn): I/O error
  device not ready yet. Retrying (trial no. 9)...
 open(/dev/rmt/0cbn): I/O error
  device not ready yet. Retrying (trial no. 10)...

  failed to detect loaded volume on drive /dev/rmt/0cbn
 even after   10 tries. Giving up...
 Ejecting tape...
jbverify: NetWorker error: read open error: drive status is There is not a tape in the drive


What could be possible problem and how to solve it?
S
MostlyNuts (TechnicalUser)
19 Jul 05 16:44
You made changes to the SAN and the drive handles all changed. You should reconfig your drives and turn persistent binding on the SAN
brackovic (IS/IT--Management)
20 Jul 05 2:30
Do you mean reconfigure on the system level or on the NetWorker level.
If system does recognize all drives correctly, would be helful to reinstall al devices, including jukebox on the Networker Server??
605 (Instructor)
20 Jul 05 14:44
We are talking about NetWorker. You obviously load the wrong device.
dominionvp (TechnicalUser)
28 Jul 05 13:48
First you need to determine if the OS can even see the drives.
brackovic (IS/IT--Management)
28 Jul 05 17:14
I found the problem.
Customer has redundant fibre connections to drives and when they changed FC cables, they missed something, so NW worked with wrong devices scidev@4.0.0 instead scidev@2.0.0. Correct cabling solved the problem!!

Thanks to all for useful tips.
S

Start A New Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Promoting, selling, recruiting and student posting
are not allowed in the forums.
Posting Policies

LINK TO THIS FORUM!
(Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum)
TITLE: Legato back-up solutions Forum at Tek-Tips
URL: http://www.tek-tips.com/threadminder.cfm?pid=480
DESCRIPTION: Legato back-up solutions technical support forum and mutual help system for computer professionals. Selling and recruiting forbidden.