Forum Discussion

George_Dicu's avatar
George_Dicu
Level 4
11 years ago

media position error(86)

Netbackup Env: Windows Server 2008 R2 + 4 media servers, IBM Robot, EMC Celera fillers, Master + Media NB version 7.5.0.7   I am trying to backup some emc filers through NDMP on tapes, IBM ro...
7.5
Backing Up
Backup and Recovery
Error messages
NetBackup
Windows Server (2003-2008)
  • Marianne's avatar
    Marianne
    11 years ago

    Just way too many hardware errors.

    At this point in time, I cannot see that ALL of those drives can be faulty.
    Probably a good idea to log a call with your hardware and server support team so that they can troubleshoot together.

    Check every piece in the data path - from server hba up to the library and tape drives (including drivers).

    What we can say with certainty is that NBU is merely reporting the errors, not causing it.

     

    Please check Event Viewer System log as well.

    **** EDIT ****

    How would you like to add event logs?

    Save them as text files and upload as attachments.

Marianne's avatar
Marianne
Level 6
11 years ago

Just WAY too many errors on different tape drives, different media....

13:28:41.887 [9328.12576] <2> io_read_block: read error on media id IBM046, drive index 8 reading header block, len = 0; No more data is on the tape. (1104)

13:28:41.887 [9328.12576] <16> io_position_for_write: cannot position media id IBM046 for write

13:28:41.887 [9328.12576] <2> send_MDS_msg: DEVICE_STATUS 1 118099786 x IBM046 4002703 IBM.ULT3580-TD5.Drive4 2000498 POSITION_ERROR 0 0


13:33:16.760 [12420.11092] <16> io_ioctl: io_ioctl_ndmp (MTFSF) failed on media id IBM037, drive index 7, return code 18 (NDMP_XDR_DECODE_ERR) (bptm.c.7061)

13:33:16.760 [12420.11092] <2> send_MDS_msg: DEVICE_STATUS 1 118108332 x IBM037 4002694 IBM.ULT3580-TD5.Drive5 2000497 POSITION_ERROR 0 0

13:33:16.775 [12420.11092] <2> log_media_error: successfully wrote to error file - 02/28/14 13:33:16 IBM037 7 POSITION_ERROR IBM.ULT3580-TD5.Drive5


13:43:59.262 [10776.12196] <2> io_read_block: read error on media id IBM069, drive index 7 reading header block, len = 0; No more data is on the tape. (1104)

13:43:59.262 [10776.12196] <16> io_position_for_write: cannot position media id IBM069 for write

13:43:59.262 [10776.12196] <2> send_MDS_msg: DEVICE_STATUS 1 118111934 x IBM069 4002726 IBM.ULT3580-TD5.Drive5 2000497 POSITION_ERROR 0 0



13:44:45.376 [8980.9836] <2> io_read_block: read error on media id XO0312, drive index 6 reading header block, len = 0; No more data is on the tape. (1104)

13:44:45.376 [8980.9836] <16> io_position_for_write: cannot position media id XO0312 for write

13:44:45.376 [8980.9836] <2> send_MDS_msg: DEVICE_STATUS 1 118099301 x XO0312 4002639 IBM.ULT3580-TD5.Drive3 2000496 POSITION_ERROR 0 0
13:51:10.822 [9340.4780] <2> send_MDS_msg: DEVICE_STATUS 1 118106543 x IBM022 4002679 IBM.ULT3580-TD5.Drive2 2000495 TAPE_ALERT 268435456 33554944

13:51:10.837 [9340.4780] <2> log_media_error: successfully wrote to error file - 02/28/14 13:51:10 IBM022 5 TAPE_ALERT IBM.ULT3580-TD5.Drive2 0x10000000 0x02000200

13:51:10.837 [9340.4780] <16> process_tapealert: TapeAlert Code: 0x04, Type: Critical, Flag: MEDIA, from drive IBM.ULT3580-TD5.Drive2 (index 5), Media Id IBM022

13:51:10.837 [9340.4780] <8> process_tapealert: TapeAlert Code: 0x27, Type: Warning, Flag: DIAGNOSTICS REQ., from drive IBM.ULT3580-TD5.Drive2 (index 5), Media Id IBM022

13:51:10.837 [9340.4780] <16> process_tapealert: TapeAlert Code: 0x37, Type: Critical, Flag: LOADING FAILURE, from drive IBM.ULT3580-TD5.Drive2 (index 5), Media Id IBM022
 
At this point curious to see ...db\media\error file on this media server as well as Event Viewer System log...
 
We need to see the source of the Events - hba or tape driver...