Forum Discussion

pkvyas1983's avatar
pkvyas1983
Level 4
13 years ago

error requesting media (tpreq)(98)

Hi All,

I am getting the error 98 while cleaning the tape drive. Please check the below logs & provide the solution .

Job Logs:-

7/17/2012 8:21:54 PM - granted resource CLNU01
7/17/2012 8:21:54 PM - granted resource HP.ULTRIUM4-SCSI.001
7/17/2012 8:21:56 PMCleaning drive HP.ULTRIUM4-SCSI.001 from server ia04bck001 with media CLNU01.
7/17/2012 8:21:59 PM - Error bptm(pid=8264) error requesting media, TpErrno = Robot operation failed    
7/17/2012 8:22:00 PM - current media CLNU01 complete, requesting next resource HP.ULTRIUM4-SCSI.001:None:CLNU01
7/17/2012 8:22:00 PM - Error nbjm(pid=3568) NBU status: 98, EMM status: The media server reported a system error
error requesting media (tpreq)(98)

 

Library make/model : Sun SL500, two HP ULTRIUM4 drive, firmware version 1300(6.39.00), Auto cleaning enabled.
OS: Microsoft Window 2003 SP2, Netbackup Version 6.5.5

vmquery output:-->

E:\Program Files\Veritas\Volmgr\bin>vmquery -m CLNU01
================================================================================
media ID:              CLNU01
media type:            1/2" cleaning tape (13)
barcode:               CLNU01
media description:     cleaning tape
volume pool:           None (0)
robot type:            TLD - Tape Library DLT (8)
robot number:          0
robot slot:            28
robot control host:    ia04bck001
volume group:          001_00000_TLD
vault name:            ---
vault sent date:       ---
vault return date:     ---
vault slot:            ---
vault session id:      ---
vault container id:    -
created:               7/17/2012 11:12:31 AM
assigned:              ---
last mounted:          ---
first mount:           ---
expiration date:       ---
cleanings left:        25
================================================================================


tpconfig output:-->

E:\Program Files\Veritas\Volmgr\bin>tpconfig -l
Device Robot Drive       Robot                    Drive                 Device
Type     Num Index  Type DrNum Status  Comment    Name                  Path
robot      0    -    TLD    -       -  -          -                     {2,0,1,0}
  drive    -    1  hcart    1      UP  -          HP.ULTRIUM4-SCSI.001  {2,0,0,0}
  drive    -    1  hcart    1      UP  -          HP.ULTRIUM4-SCSI.001  c64t0l0
  drive    -    2  hcart    2      UP  -          HP.ULTRIUM4-SCSI.002  {4,0,0,0}
  drive    -    2  hcart    2      UP  -          HP.ULTRIUM4-SCSI.002  c48t0l0
======================================================================================

vmoprcmd output:-->

E:\Program Files\Veritas\Volmgr\bin>vmoprcmd -d

                                PENDING REQUESTS

                                     <NONE>

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  1 hcart    TLD                -                     No       -         0
  1 hcart    TLD                -                     No       -         0
  2 hcart    TLD                -                     No       -         0
  2 hcart    TLD                -                     No       -         0

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment
  1 HP.ULTRIUM4-SCSI.001  No       -
  1 HP.ULTRIUM4-SCSI.001  No       -
  2 HP.ULTRIUM4-SCSI.002  No       -
  2 HP.ULTRIUM4-SCSI.002  No       -

Thanks in advance..

  • Barcode looks good - looks like standard clening tape barcode.

    This is the same as putting the tape in the drive by hand

    m s28 d2

    Initiating MOVE_MEDIUM from address 1027 to 501
    move_medium failed
    sense key = 0x5, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED

    This is hardware error

    TLD(0) key = 0x5, asc = 0x30, ascq = 0x0, INCOMPATIBLE MEDIUM INSTALLED

    For some reason, the drive does not like the tape.

    Could be a firmware issue, or drive issue, or tape issue.

    It was working before you say, so very odd, but it is not working now, and that error cannot be caused by netbackup.

    I recommend you speak with the hardware vendor for advice.

    Martin

15 Replies