Video Screencast Help
Search Video Help Close Back
to help

error requesting media (tpreq)(98)

Created: 18 Jul 2012 | Updated: 31 Jul 2012 | 15 comments
pkvyas1983's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

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..

Comments 15 CommentsJump to latest comment

mph999's picture

Does robtest work ?

If so, try loading the cleaning tape into the drive from robtest.

eg

m sX dY

(Move slot x to Drive y)

 

m dY sX  (move Drive Y to slot X to unload)

Martin

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
0
Login to vote
  • Actions
pkvyas1983's picture

Thanks for reply Martin,

Yes robotic is working & backup alos working fine on first drive, sencond drive giving the message cleaning required & backups are getting failed on this drive after writing some data.

I tried robtest command  to move the cleaning media into drive but is giving error

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

System Event logs- ID 7

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

Thanks

Pradeep

0
Login to vote
  • Actions
Andy Welburn's picture

Seems it doe not like your cleaning tape.

Is it compatible with LTO4 drives?

Have you used this cleaning tape before in these drives? (Successfully?)

0
Login to vote
  • Actions
pkvyas1983's picture

Hi Andy, Thanks for reply. Actually we are sitting on remote location & dont able to view the actual cleaning tape. As per site support its a cleaning tape HP Ultrium universal cleaning media. And we performed last cleaning before 6 month ago. Dont why this time we are getting this error. We are going to connect with site tech & ask him to send a snap of cleaning media & let you update.

Thanks u all for your suggesion & help.

0
Login to vote
  • Actions
wr's picture

Stuck tape?  Can you move it via robtest? 

 

* oh, Martin beat me to it *

will restore -- where there is a Will there is a way

0
Login to vote
  • Actions
pkvyas1983's picture

Hi Martin, Thanks

But no media stucked in drive, Please check the details below

Robot Selection
---------------
  1)  TLD 0
  2)  none/quit
Enter choice: 1
1

Robot selected: TLD(0)   robotic path = {2,0,1,0}

Invoking robotic test utility:
E:\Program Files\Veritas\Volmgr\bin\tldtest.exe -rn 0 -

Opening {2,0,1,0}
MODE_SENSE complete
Enter tld commands (? returns help information)
s d
drive 1 (addr 500) access = 1 Contains Cartridge = no
drive 2 (addr 501) access = 1 Contains Cartridge = no
READ_ELEMENT_STATUS complete
quit

Please suggest.

0
Login to vote
  • Actions
revaroo's picture

 

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

System Event logs- ID 7

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

 

This error is coming from outside of NetBackup. Incompatible Medium Installed. Have you checked that the cleaning tape and the drive are actually compatible?

 

0
Login to vote
  • Actions
pkvyas1983's picture

Hi Revaroo,

We are going to check & let you update. Thanks for reply.

0
Login to vote
  • Actions
Marianne van den Berg's picture

Eject the cleaning tape from the library and check the actual barcode. There is something else besides CLNU01 on the label that says to the robot that the tape is not compatible with the drive.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

0
Login to vote
  • Actions
pkvyas1983's picture

Thanks Marianne,

I will check & update you.

0
Login to vote
  • Actions
pkvyas1983's picture

Hi Marianne,

We checked with site tech & got the snap of cleaning tapes. These are cleaning medias only and below is the update-

Cleaning cartridge for use with all Ultrium 1,2,3,4, & 5 Drives (written on cleaning media)
Label on Tape:CLNU01L4 & CLNU02L4 (Actual barcode)

Please suggest.

 

0
Login to vote
  • Actions
mph999's picture

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

 

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
SOLUTION
0
Login to vote
  • Actions
Marianne van den Berg's picture

It all seems right, but this is the robot that does not believe that drive and media is compatible. The robot is producing the error.

If you try to mount the tape through the robot front panel or the Web GUI, you will see the same error.
Your hardware vendor needs to sort this out. Possibly robot firmware issue?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

0
Login to vote
  • Actions
pkvyas1983's picture

Hi Martin/Marianne,

Thanks for help/suggestion, I will contact to harware vendor to sort it out this issue & update you once problem resolved. Thanks you all for yr time & valuable suggestion.

Regards

Pradeep

0
Login to vote
  • Actions
pkvyas1983's picture

Hi All,

Drive cleaning issue now has been fixed, the problem due to drive old firmware. We have upgraded the drive firmware & drive cleaning done without any issue by using same media.

Thanks you all for your support & suggestion.

0
Login to vote
  • Actions