Rolf,
 it could be any number of things, If you have Hp openview running it can
poll your drives, and even a stall of just half a seccond while it polls
can cause an 84. Do you see this happening in a pattern, where all your
drives have them at roughly thesame time?  I have been burried chest deep
in these . Lemme know, There is more to it that just "Bad Media"

    Jeremy

Thursday, November 17, 2005 10:37 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
cc:
From: "Rolf C" <rolfcolmer AT hotmail DOT com>
Subject: [Veritas-bu] status 84 - writing header block, 1117



Hi all,

Since some time all my backups fail with a status 84 and the following
error:

16:03:47.015 [4428.5964] <2> io_read_media_header: tapemark or blank tape
encountered reading media header, drive index 0
16:03:47.031 [4428.5964] <2> io_write_media_header: drive index 0, writing
media header
16:03:47.031 [4428.5964] <2> io_ioctl: command (5)MTREW 1 from
(bptm.c.8612)
on drive index 0
16:03:50.687 [4428.5964] <2> io_write_block: WriteFile() failed err = 1117
16:03:50.687 [4428.5964] <2> set_job_details: Done
16:03:50.703 [4428.5964] <16> io_write_block: write error on media id
A00005, drive index 0, writing header block, 1117
16:03:50.703 [4428.5964] <2> log_media_error: successfully wrote to error
file - 11/17/05 16:03:50 A00005 0 WRITE_ERROR
16:03:50.703 [4428.5964] <2> check_error_history: called from bptm line
19524, EXIT_Status = 84

I have checked the cables, drivers and used serveral tapes. Cleaned the
tapedrive with several cleaning cartridges and ran the Device Wizard
several
times.

Anyone any idea how to solve this?


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
 http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu