Veritas-bu

[Veritas-bu] Netbackup 4.5 on Solaris box; stk silo; 9840 tape drive problem with unmount

2003-03-07 06:22:42
Subject: [Veritas-bu] Netbackup 4.5 on Solaris box; stk silo; 9840 tape drive problem with unmount
From: mhickey AT glasshousetech DOT com (Mark Hickey)
Date: Fri, 7 Mar 2003 06:22:42 -0500
David,
    
If the drive was operating okay, and has recently developed this
problem, then:
    + what has changed in the environment?
    + Check the drive status from the web interface or the front panel
      to make sure that the library is talking to the drive.
    + check the FCS log from the web interface.
    + open the door of the library and make sure that the drive hasn't 
      got any error lights on the front.  Opening the door will force a 
      re-init cycle for the library that sometimes clears things up
    + power cycle the drive
    + put a tape in the drive (by hand if necessary), and verify that
NBU
      shows it in the drive you expected and that mt -f commands against
      the device file for the drive return the expected status.
    + start unit testing cables,etc.

 If the drive never worked right, try looking at:
    + your kernel configuration, specifically,
         - do you have enough targets defined in the st.conf for the 
           controller that the drives are on?
         - do you have equivalent sg.conf entries for the drives?
         - does /etc/devlink.tab have the right entries?
    + verify the SCSI id of the drive
    + verify the robot drive numbering scheme versus what you 
      told netbackup.


Just some things that have worked in the past.

  Mark Hickey
  Senior Technology Consultant
  Glasshouse Technologies
  www.glasshouse.com
       

-----Original Message-----
From: Letnes, David G. [mailto:david.letnes AT unisys DOT com] 
Sent: Thursday, March 06, 2003 6:11 PM
To: 'Michael Graff Andersen'; Letnes, David G.;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Netbackup 4.5 on Solaris box; stk silo; 9840
tape drive problem with unmount

The robtest command unload doesn't work for this drive.  The other drive
I
can move a tape in, unload and move it back out fine.
  What else can I do if the drive doesn't respond to robtest.

David

-----Original Message-----
From: Michael Graff Andersen [mailto:nbuscripts AT post.cybercity DOT dk]
Sent: Thursday, March 06, 2003 5:13 PM
To: Letnes, David G.; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Sv: [Veritas-bu] Netbackup 4.5 on Solaris box; stk silo; 9840
tape drive problem with unmount


Hi David

One thing worth trying is scsi unload from the robtest utility, this
will
show if the drive react/responds correctly to scsi commands. Try also to
move a tape from around in the robot.

Regards
Michael

-----Oprindelig meddelelse-----
Fra: Letnes, David G. <david.letnes AT unisys DOT com>
Til: 'veritas-bu AT mailman.eng.auburn DOT edu'
<veritas-bu AT mailman.eng.auburn DOT edu>
Dato: 6. marts 2003 19:54
Emne: [Veritas-bu] Netbackup 4.5 on Solaris box; stk silo; 9840 tape
drive
problem with unmount


>
>I have some trouble with my tape drives.  A backup will occur and
finish
>fine, but when the tape unmounts something happens and it can't unmount
and
>remove the tape.  Has anyone else seen these errors where the drive
writes
>and reads fine, but during the unmount process an error occurs and
Netbackup
>marks the drive as down?  Our Storage Tek Rep says Netbackup has a
problem
>when it unmounts tapes that it wants to unmount and eject the tape
before
it
>gets down rewinding the tape.
>
>Thank You
>David
>
>
>Here is the error messages that show up.
>
> Feb 24 16:32:335 exu303 tldcd[16608]: [ID 178687
>daemon.notice] Processing UNMOUNT, TLD(0) drive 1, slot 69, barcode
EP0068
> , vsn EP0068 
> Feb 24 16:32:35 exu303 tldcd[20705]: [ID 363900
>daemon.notice] TLD(0) opening robotic path /dev/sg/c4t0l0 
> Feb 24 16:32:35 exu303 tldcd[20705]: [ID 143434
>daemon.notice] inquiry() function processing library STK L700 0301: 
> Feb 24 16:32:35 exu303 tldcd[20705]: [ID 802088
>daemon.notice] isSTK = TRUE 
> Feb 24 16:32:35 exu303 tldcd[20705]: [ID 141381
>daemon.notice] TLD(0) initiating MOVE_MEDIUM from addr 500 to addr 1068

> Feb 24 16:32:36 exu303 tldcd[20705]: [ID 183166
>daemon.error] TLD(0) key = 0x5, asc = 0x3a, ascq = 0x0, MEDIUM NOT
> PRESENT 
> Feb 24 16:32:36 exu303 tldcd[20705]: [ID 841094
>daemon.error] TLD(0) Move_medium error: CHECK CONDITION 
> Feb 24 16:32:36 exu303 tldcd[20705]: [ID 559680
>daemon.notice] TLD(0) closing/unlocking robotic path 
> Feb 24 16:32:36 exu303 tldd[16594]: [ID 348449
>daemon.notice] DecodeMount(): TLD(0) drive 1, Actual status: Unable to
open
> drive 
> Feb 24 16:32:36  exu303 tldd[16594]: [ID 487151
>daemon.notice] Adding media ID EP0068 to unmountable media list 
> Feb 24 16:32:36 exu303 tldd[16594]: [ID 138408 daemon.error]
>TLD(0) drive 1 (device 1) is being DOWNED, status: Unable to open
> drive 
> Feb 24 16:32:36 exu303 tldd[16594]: [ID 229259 daemon.error]
>Check integrity of the drive, drive path, and media 
> Feb 24 16:32:36 exu303 ltid[16545]: [ID 774530
>daemon.notice] LTID - received ROBOT MESSAGE, Type=57, LongParam=0,
> Param1=0, Param2=0 
> Feb 24 16:32:36 exu303 tldd[16594]: [ID 114742
>daemon.notice] Removing media ID EP0068 from unmountable media list 
>
>
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


<Prev in Thread] Current Thread [Next in Thread>