Forum Discussion

technimdaxviii's avatar
technimdaxviii
Level 5
8 years ago

The eject operation has completed with errors

Backup failed and got the log showing below:

02/13/2017 00:39:53 - mounting DAT003
02/13/2017 00:39:55 - Error bptm (pid=24921) error requesting media, TpErrno = Robot operation failed
02/13/2017 00:39:55 - Warning bptm (pid=24921) media id DAT003 load operation reported an error
02/13/2017 00:39:55 - current media DAT003 complete, requesting next media Any
02/13/2017 00:40:14 - Info bptm (pid=24921) EXITING with status 96 <----------
02/13/2017 00:40:14 - Error bpbrm (pid=24912) from client server1.domain.com: ERR - bpbkar exiting because backup is aborting
02/13/2017 00:40:15 - Info bpbkar (pid=24917) done. status: 96: unable to allocate new media for backup, storage unit has none available
02/13/2017 00:40:15 - end writing
unable to allocate new media for backup, storage unit has none available  (96)

 

Most all the tapes are full and waiting for the expiration to clean up, I assign one available tape in our oracle backup. Backup completed after adding.

What I've notice on the log, though it got completed, job still looking for DAT003 before proceeding to other tape.

02/13/2017 12:40:26 - mounting DAT003
02/13/2017 12:40:28 - Error bptm (pid=27518) error requesting media, TpErrno = Robot operation failed
02/13/2017 12:40:28 - Warning bptm (pid=27518) media id DAT003 load operation reported an error
02/13/2017 12:40:29 - current media DAT003 complete, requesting next media Any
02/13/2017 12:40:47 - Info bptm (pid=27518) Waiting for mount of media id 0007L6 (copy 1) on server server1.domain.com.
02/13/2017 12:40:47 - granted resource  0007L6

 

Question1:  DAT003 has no data, so we decided to remove the tape by ejecting from the console but it return an error(The eject operation has completed with errors). When we check the slot, tape was in the media. Why the tape was in the media even though its not being use?

 

 

 

 

 

 

7.6
Solaris
  • Marianne's avatar
    Marianne
    8 years ago

    Your robot seems to be faulty - no commands are going to work as the robot is not responding:

    mode_sense failed
sense key = 0x2, asc = 0x4, ascq = 0x81, UNIT IS OFF_LINE


    Try to reboot/powercycle the robot. If that does not fix it, call your hardware vendor.

6 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    8 years ago

    Sorry, I don't understand what this means:

    When we check the slot, tape was in the media.

    What is the media? Where is the tape? In the slot or the tape drive? 
    Maybe the tape is stuck in the drive and cannot be unloaded.

    Can you try to move the tape with robtest?

    Robtest usage: http://www.veritas.com/docs/000041570

    So, in robtest first use 's d' to see in which drive the tape is and which slot number the tape came from. First send 'scsi unload'. If successful, move tape back to slot:
    unload d#
    m d# s#

    If you get error messages and the tape seems to be stuck, call your hardware maintenance vendor.

    • mph999's avatar
      mph999
      Level 6
      8 years ago

      I would also add that even if the tape is in the slot, try and move it to the drive ...

      m sx dy (move from slot number x to drive number y)

      and then back again if successful

      m dy sx (be sure to move it back to the same slot number it came from)

      • technimdaxviii's avatar
        technimdaxviii
        Level 5
        8 years ago

        Hi mph999,

        Thank you for the input. I'll look into it once I have the details.

    • technimdaxviii's avatar
      technimdaxviii
      Level 5
      8 years ago

      Hi Marianne,

      Apologies for the confusion. I quite new using netbackup and not familiar with all the terminology.

      Trying to use robtest, it seems nothing happen using 's d' option.

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

Robot selected: TLD(0)   robotic path = /dev/sg/c0tw500104f000d23aa7l1

Invoking robotic test utility:
/usr/openv/volmgr/bin/tldtest -rn 0 -r /dev/sg/c0tw500104f000d23aa7l1 

Opening /dev/sg/c0tw500104f000d23aa7l1
mode_sense failed
sense key = 0x2, asc = 0x4, ascq = 0x81, UNIT IS OFF_LINE
Enter tld commands (? returns help information)
s d
read_element_status: Must execute a successful mode sense prior to executing this command.
 Perform a tldtest 'mode' command until it succeeds
      • Marianne's avatar
        Marianne
        Level 6
        8 years ago

        Your robot seems to be faulty - no commands are going to work as the robot is not responding:

        mode_sense failed
sense key = 0x2, asc = 0x4, ascq = 0x81, UNIT IS OFF_LINE


        Try to reboot/powercycle the robot. If that does not fix it, call your hardware vendor.