Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

media error

Created: 28 Nov 2012 • Updated: 01 Dec 2012 | 6 comments
This issue has been solved. See solution.

07/07/08 07:36:18 RUA253 1 TAPE_ALERT HP.ULTRIUM3-SCSI.001 0x00800000 0x00000000

07/09/08 20:01:13 NW0119 1 TAPE_ALERT HP.ULTRIUM3-SCSI.001 0x00000000 0x00002000 


Getting the above error in db/media /error file.

How to know what is error 0x00800000 0x00000000

0x00000000 0x00002000
I have followed above link.But not useful

It's just showing you the flags in hex from left to right.  4 flags in each hex digit.  Add four for each '0' to the left, then add 1 for an '8', 2 for a '4', 3 for a '2' and 4 for a '1'.

One of your examples was: 0x00800000 0x00000000

So two zeros on the left, add 4 for each => 2 * 4 => 8

Next digit is 8, so add 1.   8 + 1 => 9.  This is flag 9.

This works fine for determining the flag number of any single flag.  If you have multiple flags in different digits, just pretend the others aren't set.  So this one in my logs:   0x28000004 0x00000000

Would be flags 3, 5, and 30.

Little more complex if you have multiple flags in a digit. You have to break it into the components.

I have a lot of errors of flag 55 (which is just past the end of the flags that are discussed in the HP document).  I remember asking them about it, but we didn't come up with a specific reason for that flag to alert.  Caused a *lot* of problems.

Note that the BPTM log records the same data in two forms.  Once with the hex display and once with the decimal display.

02:48:09.651 [364] <2> send_MDS_msg: DEVICE_STATUS 1 52778 blah blah blah blah TAPE_ALERT 2048 0
02:48:09.651 [364] <2> JobInst::sendIrmMsg: starting
02:48:09.653 [364] <2> JobInst::sendIrmMsg: returning
02:48:09.679 [364] <2> log_media_error: successfully wrote to error file - 01/01/09 02:48:09 blah 30 TAPE_ALERT blah 0x00000800 0x00000000

0x000000800 and '2048' tell about the same flag.

Comments 6 CommentsJump to latest comment

Andy2345's picture

Hi,Can anybody please respond.

Mark_Solutions's picture

0x08 - netbackup freezes media as it is classed as not data grade

0x28 to 0x31 - undefined error - no action taken by NetBackup

55 converts to 0x37 in hex - loading error - will be frozen by NetBackup

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Marianne's picture

Please also read through 'TapeAlert logs and codes' in NBU Admin Guide II

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

Andy2345's picture

I just wanna know the process how this .

 0x28000004 0x00000000 is converted?

Marianne's picture

Already answered in Mark's post.

Also documented in Admin Guide II.

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

mph999's picture
  Add 0 if 4
  Add 1 if 8
  Add 2 if 4
  Add 3 if 2
  Add 4 if 1
  You break it down like this :
  Each digit is a separate flag, so there are 3 flags.
  Then you subsitite in the numbers from my table.(but ignore the 0's after a digit
  0x20000000 = 3    
  0x08000000 = 4 + 1
  0x00000004 = 4+4+4+4+4+4+4+2  (we substitute the 0's here as they are before the 4)
  So Add those up we have ...flags 3, 5 and 30
  Then you use Google to find out what tape alert flag 3 is, what tape alert flag 5 is , and the 30.
  Flag 3: Hard error. Severity: Warning
  Flag 5: Read failure. Severity: Critical
 Flag 30: Hardware A. Severity: Critical
 In summary, your drive is very broken.
Regards,  Martin
Setting Logs in NetBackup: