Forum Discussion

yadda123's avatar
yadda123
Level 4
15 years ago

error 84 (Status = media write error.)

I just ran into an error 84 (Status = media write error). The job exited(shows up as queued in the activity monitor, but does not show up in a ps listing any longer), and the tape that error'd was fro...
7.1.x and Earlier
Backup and Recovery
NetBackup
  • Mouse's avatar
    Mouse
    15 years ago
    Here are descriptions of your errors:

    14h
    Clean now  The tape drive needs cleaning:
    1. If the operation has stopped, eject the tape and clean the drive.
    2. If the operation has not stopped, wait for it to finish and then clean the drive.
    Check the tape drive users manual for device specific cleaning instructions.
    The drive thinks it has a head clog or needs cleaning.

    27h
    Diagnostics required
    The tape drive may have a hardware fault. Run extended diagnostics to verify and diagnose the problem. Check the tape drive users manual for device specific instructions on running extended diagnostic tests.
    The drive may have a hardware fault that may be identified by extended diagnostics (i.e., SEND DIAGNOSTIC command).

    1Eh
    Hardware A
    The tape drive has a hardware fault:
    1. Eject the tape or magazine.
    2. Reset the drive.
    3. Restart the operation.
    The drive has a hardware fault that requires reset to recover.

    Based on the list of errors you provided I can make a conclusion that something is going wrong with your drive (s) in the tape library. Ask your library vendor to dump the error log from the library and follow their recommendations.

    Once you fix hardware fault, you can resume your job from the checkpoint (right click on the job in the Activity Monitor)

joel_blanks's avatar
joel_blanks
Level 3
15 years ago
Good Morning to all,

This is the error I am getting when I receive a status code 84.  Can I safely assume that I have a bad tape?

8/25/2009 8:38:24 AM - requesting resource stewdoimb2902-hcart3-robot-tld-0
8/25/2009 8:38:24 AM - requesting resource stewdoimb2901.NBU_CLIENT.MAXJOBS.stewdoimc202
8/25/2009 8:38:24 AM - requesting resource stewdoimb2901.NBU_POLICY.MAXJOBS.stewdoimc202
8/25/2009 8:38:24 AM - granted resource stewdoimb2901.NBU_CLIENT.MAXJOBS.stewdoimc202
8/25/2009 8:38:24 AM - granted resource stewdoimb2901.NBU_POLICY.MAXJOBS.stewdoimc202
8/25/2009 8:38:24 AM - granted resource 2773L3
8/25/2009 8:38:24 AM - granted resource IBM.ULTRIUM-TD3.001
8/25/2009 8:38:24 AM - granted resource stewdoimb2902-hcart3-robot-tld-0
8/25/2009 8:38:30 AM - started process bpbrm (4544)
8/25/2009 8:38:30 AM - connecting
8/25/2009 8:38:42 AM - connected; connect time: 00:00:12
8/25/2009 8:39:12 AM - current media 2773L3 complete, requesting next media Any
8/25/2009 8:40:10 AM - granted resource 2773L3
8/25/2009 8:40:10 AM - granted resource IBM.ULTRIUM-TD3.002
8/25/2009 8:40:10 AM - granted resource stewdoimb2902-hcart3-robot-tld-0
8/25/2009 8:40:12 AM - mounting 2773L3
8/25/2009 8:40:54 AM - mounted; mount time: 00:00:42
8/25/2009 8:40:54 AM - positioning 2773L3 to file 1112
8/25/2009 8:42:24 AM - positioned 2773L3; position time: 00:01:30
8/25/2009 8:42:24 AM - begin writing
8/25/2009 8:43:59 AM - Error bptm(pid=5820) write error on media id 2773L3, drive index 3, writing header block, 21
8/25/2009 8:44:01 AM - end writing; write time: 00:01:37
media write error(84)